[X2Go-User] session.log file fills disk

[David Schumm]

From my experience it doesn’t always seem to free up the disk space.  We’ve already downgraded the packages to the previous version and it appears to be working fine.  Thanks for your responses.
Dave

> On Dec 30, 2020, at 6:49 AM, Ulrich Sibiller <uli42 at gmx.de> wrote:
> 
> Yes, this is a bug in 3.5.99.25  that has already been fixed in commit
> https://github.com/ArcticaProject/nx-libs/commit/ad275d50720fbbaf65bc0668eed0297df5d27cad
> 
> Unfortunately there has not been a release with this fix. If you are
> able to compile your own version you can get rid of the bug.
> 
> You should be able to delete the session.log even with the session
> running. I need to test if this really frees the disk space. If not,
> an additional suspend/reconnect might help.
> 
> If both approaches are not feasible I suggest downgrading to nxagent 3.5.99.24.
> 
> Uli
> 
> 
>> On Wed, Dec 30, 2020 at 2:36 PM David Schumm <david.schumm at seakr.com> wrote:
>> We are seeing this on multiple machines where the session.log file is massive.  I’ve seen them as large as 82gb.
>> When you attempt to open it it says it’s a binary file
>> Server is Centos 7 running  x2go server 4.1.0.3-9
>> ________________________________
>> This e-mail may contain SEAKR Engineering (SEAKR) Confidential and Proprietary Information. If this message is not intended for you, you are strictly prohibited from using this message, its contents or attachments in any way. If you have received this message in error, please delete the message from your mailbox. This e-mail may contain export-controlled material and should be handled accordingly.  ­­
>> _______________________________________________
>> x2go-user mailing list
>> x2go-user at lists.x2go.org
>> https://lists.x2go.org/listinfo/x2go-user

==
This e-mail may contain SEAKR Engineering (SEAKR) Confidential and Proprietary Information. If this message is not intended for you, you are strictly prohibited from using this message, its contents or attachments in any way. If you have received this message in error, please delete the message from your mailbox. This e-mail may contain export-controlled material and should be handled accordingly.