Hello!

I recently had the fun of finding out that the hard drive on one of my customer's servers that have GoGlobal installed had completely filled up. I traced the problem to the $HOME/.graphon/log/ where there were several session logs that were HUGE. After removing these, the system is back to normal.

What I would like to know is, what are the parameters for the $GOGLOBAL_ROOT/etc/sessionlog.conf file and how are they used? I am hoping that somewhere in this configuration file I can limit the amount of disk space consumed by these session logs.

I would appreciate any help that is available. Thank you.

We endeavor to avoid this situation, but in the case of session logs it can be hard to determine. One problem is that ideally each session log should contain all of the logging for a given session (so "rotation" of log files based on size is hard to do). Ideally you should be able to use the "MAXLOGAGE" setting in the sessionlog.conf file to avoid having too many of these logs on the system.

Also, if the session logs continue to grow at too great a rate, you can send a sample one to our support team (at support@graphon.com) and ask them what other settings in the sessionlog.conf can be adjusted to make the log less verbose. It's difficult to say what adjustments you should make without seeing the types of logging that is going on.

Hope this helps,
Troy

Thanks for the quick reply.

Since there is no sessionlog.conf file in existence, I would assume that the session is logging at whatever your development team have decided is the "default" settings. I have heard from one of our users that sessions can become suspended when we lose our VPN connection in the middle of a session. If this is so, and the user decides that they do not want to restart the connections, then the session will run until the next time the session is connected.

Maybe you can advise me on how to setup a session timeout for sessions that have seen no user interaction for a specified period of time. Maybe in this way I can eliminate the "run on" session situation.

Thanks again for your help.