We have one service, connecting stunnel to another application. Relevant configuration:

 

[vpn]

client = no

accept = 172.17.102.122:443

exec = /usr/sbin/ppp

execargs = ppp -direct vpn

pty = yes

 

Brian

 

 

 

Just a silly idea, but is it possible you have a re-entrant configuration for one service, one that connect back to itself creating a loop?

 

 

 

 

 

We are running stunnel 5.49 on FreeBSD 11.2 and we’re running into a problem once in a while.

 

CPU pegs at 100% when we get an stunnel connection from one of our external devices.

This affects 100% of all cores and we can’t even log in to console.

 

To mitigate this temporarily, we have a script running in the background to watch when stunnel begins to spike and restarts the daemon.

 

It doesn’t happen 100% of the time, and so far I have been unable to distinguish what makes the connection do this to the CPU.

 

Have any of you run in to this issue?

 

 

Sincerely,

 

 

Brian Murrey
System Engineer II, IT Infrastructure

 

NOTICE: This message may contain privileged and confidential information and/or protected health information intended solely for the use of the named recipient and may be privileged or otherwise protected by law. If you are not the intended recipient of this message, you should immediately notify the sender and delete this message. Do not disseminate, reproduce, or review this message or attachments if you are not the intended recipient. The sender or others may have legal rights restricting the dissemination of the information contained in this message and, as a result, remedies against you in the event of the improper dissemination of confidential information, trade secrets, personal information or privileged communications. This message is the work of the sender and does not necessarily reflect the position, views, or policies of TriMedx LLC or its affiliates.

WARNING: The integrity and security of this message cannot be guaranteed and may contain or transmit a virus or other illicit code. Neither TriMedx LLC or its affiliates accept liability for any damage attributable to viruses or illicit code transmitted through this message or an attachment.

CAUTION: This email originated from outside of the organization. Do not open links or attachments you were not expecting, even from known senders, and use caution when responding. Please contact the Service Desk if in doubt regarding the legitimacy of this email.