Re: [Openvpn-devel] Openvpn 2.3.2: "Could not create temporary file" ....Too many open files
Hi, On Tue, Jul 22, 2014 at 12:37:19PM -0500, Eric Crist wrote: > This isn't an OpenVPN problem, directly. It appears you have a client > connect script, or are storing connection information in temp files. You can > increase the maximum allowed open files in Fedora (you'll have to research > that yourself). Alternatively, stop storing connection data in a temp file > for new connections. OpenVPN, by itself, does not create these temporary > files. Uh, this is not fully correct. If you use --client-connect (or any of the other up scripts that enable passing of config values back), OpenVPN will create the temp file to be used for that, to avoid race conditions. I'm not sure when this was added, but "recentish" (2.2.x) Now the sema-files do not ring a bell, but we need to check whether we properly clean up the other files - but that should be visible in "lsof" while OpenVPN is running and after a few connections have completed. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpAH7R1Bc6x0.pgp Description: PGP signature
Re: [Openvpn-devel] Openvpn 2.3.2: "Could not create temporary file" ....Too many open files
This isn't an OpenVPN problem, directly. It appears you have a client connect script, or are storing connection information in temp files. You can increase the maximum allowed open files in Fedora (you'll have to research that yourself). Alternatively, stop storing connection data in a temp file for new connections. OpenVPN, by itself, does not create these temporary files. - Eric F Crist On Jul 22, 2014, at 11:24:54, arno.oderm...@ch.schindler.com wrote: > 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]: /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 root0 Jul 18 10:51 vpn3_sema_15198 > #sema files laying around > > - in /var/tmp-rw---. 1 root0 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. > *** > -- > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds___ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel signature.asc Description: Message signed with OpenPGP using GPGMail
[Openvpn-devel] Openvpn 2.3.2: "Could not create temporary file" ....Too many open files
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]: /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 root0 Jul 18 10:51 vpn3_sema_15198 #sema files laying around - in /var/tmp -rw---. 1 root0 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. ***
