chipconnection
Hello all,
I just deployed an AS server at a clients. Works great. Had a strange issue the other day though. One user couldn't connect and got an error that the autoconnect log in C:\program files (x86)\OpenVPN Technologies\OpenVPN Client\etc\logs could not be read to the end. Or something like that.
So I went in to the logs folder and that log file was just under 5GB! This has only been deployed for about 2 weeks.
Any ideas on what could make that so big?
Note: I haven't seen the contents of the file. It's on a laptop that I haven't been able to get to to get the file off of yet.
Thanks,
-John
maikcat
without being AS expert try to avoid log-append and verb level above 3..
Michael.
The Johan
This is a known problem that was addressed in the Connect Client that comes with Access Server 2.0.11. It affects only a handful of systems. We recommend updating your Access Server installation and downloading and installing the new Connect Client that comes bundled in that version, it should resolve the issue for you.
chipconnection
Hello all,
I got a new version of the client from support. It's the version that's included with the update to AS. NovaFlash is right. Either update your AS server or get the updated client from support.
NOTE: I was seeing log files in c:\program files (x86)\OpenVPN Technologies\OpenVPN Client\etc\logs of anywhere from 5 to 19 GB when the program stopped connecting. I had huge log files with 6 of the 15 or so machines I installed it on, the others haven't been checked yet. Seems like the problem is pretty consistent. It was the size of the log file when the Client stopped connecting that was the variable.
-John
