Dear all,

we are driving O-VPN 2.3.2 on Fedora20.
Since we have quit many permanently connected O-VPN clients, we have 
started three O-VPN processes, listening on three different ports and 
setting up three different tap interfaces:

Today, all three O-VPN processes crashed suddenly, whereas we found 
following error:

 ip-172-16-128-101 openvpn[654]: <CN>/172.16.253.10:44214 Could not create 
temporary file '/var/tmp/openvpn_cc_1bd37815cbacd70936015e40e25198aa.tmp': 
Too many open files

We did not find any helpful information, neither in the the mail-archives, 
nor in other forums/panels, beside something related to user/password 
authentication (openvpn-auth-pam), which we are not using (using 
TLS-server) and also lsof did not provide any helpful information to 
correlate this error to a (file-) resource problem

https://forums.openvpn.net/topic13474.html 
https://community.openvpn.net/openvpn/ticket/201 


After this happened, we found:

- in /tmp:      -rw-r--r--.  1 root    0 Jul 18 10:51 vpn3_sema_15198 
#sema files laying around

- in /var/tmp   -rw-------.  1 root        0 Jul 18 10:51 
openvpn_cc_0e211df697b9f5620da89bd05f44ef48.tmp


Deleting of the sema-files and restarting O-VPN brought back everything to 
life.

Has anybody ever experienced something similar, can this be a bug and what 
could be the corrective action to overcome, this to repeat again?

Thank you for any help in this

Ar



******************************************************
Notice: The information contained in this message is intended only for use of 
the individual(s) named above and may contain confidential, proprietary or 
legally privileged information. No confidentiality or privilege is waived or 
lost by any mistransmission. If you are not the intended recipient of this 
message you are hereby notified that you must not use, disseminate , copy it in 
any form or take any action in reliance of it. If you have received this 
message in error please delete it and any copies of it and notify the sender 
immediately.
*******************************************************

Reply via email to