Hi,

Yesterday I noticed my main AstLinux box /var was filed at 10 GB.  The culprit 
was "/var/log/openvpn.log" .

After some investigating this was caused by the OpenVPN Connect (1.0.1 build 
88) app on my iOS device (I assume Android would be the same). AFAIK, the 
OpenVPN Connect 1.0.0 version did not behave the same way.

Quick answer, the solution is to set OpenVPN Server -> Log Verbosity: [ None ], 
whereby only significant errors will be logged on the production server.

The details...

I use the default general setting of "Reconnect on wakeup" ON, so even when the 
iOS device is off, every 5 minutes it authenticates itself and keeps the 
OpenVPN session active while sleeping.  This simple process can generate a fair 
amount of logging.  To add to the errors after using the iOS device externally 
and then moving the iOS device to the local WiFi network there were a lot of 
replay errors since the raw command "multihome" was not set so the return path 
would not be correct.  By setting the raw command "multihome" the OpenVPN 
session will re-connect locally without errors (assuming you are using UDP).  
Regardless, there is still a lot of logs generated over time.

If I set the default general setting of "Reconnect on wakeup" OFF, the logging 
problem goes away, but clearly this is very cool feature of the OpenVPN Connect 
app, so I want it ON.

Of course if you can always remember to turn off the OpenVPN connection when 
you are finished that would be the best, but who does that ? :-)

Possibly a better solution down the road would be to add some general log 
rotating utility in AstLinux.

Lonnie


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to