Forum Replies Created
-
AuthorPosts
-
marty39Participant
NoMachine doesn’t list Mint as a supported distro, so I did a sideways upgrade to Ubuntu 18.04.1 “Bionic Beaver” and immediately installed NoMachine. No problems, works both directions. Ubuntu does everything I need.
marty39ParticipantIt’s in trouble again, and I tried to collect the logs, but nxserver.log on the Linux server is 3.4 GB. When I run the tar command it pauses for maybe a minute at nxserver.log and then says the file shrank by about 3GB and it’s padding with zeros, and the compressed file is nearly 90MB. I tried with the server stopped and the file shrank by about 2GB, again padding with zeros, and the compressed file is “only” about 5MB. What should I do?
marty39ParticipantHello, got your email. I backed up the original and I’m going to make the patch, but at this time the connection is proceeding normally. If the problem recurs I will have the logs ready to send as instructed above.
marty39ParticipantStill hoping for a solution. Compressed logs are attached.
marty39ParticipantSessionLogClean 0 was set, but I had restarted the NoMachine server on the Linux system, not the whole Linux system. I thought I had set “don’t delete log files on exit on the client side (Mac) but apparently I had not.
I restarted the Linux system before trying again. Ignore messages in the client log saying the host is down; it was down because attempting to restart remotely failed. The relevant session begins at 12:50:23 after the Linux system was restarted.
There was no client log folder beginning with R-, but there was a relevant log folder beginning T-R- so that’s what I’m sending, along with the latest server side logs.
-
AuthorPosts