Forum Replies Created
January 7, 2014 at 21:43 in reply to: Error: Session agent timeout: ‘Initial’ since too much time #1604
Can you attach or send us the following logs after enabling debug? To enable debug and collect the most amount of information you can use the instructions here:
You can attach the logs to this topic or alternatively email them to forum[at]nomachine[dot]com with the subject “Error: Session agent timeout: ‘Initial’ since too much time”
We would like to ask for the following logs, at your convenience, to better diagnose what is happening:
For the failing connection to Ubuntu installation:
1. All logs located in /usr/NX/var/log/nxnode from the Ubuntu laptop NoMachine Server installation:
Create a compressed archive (tar.gz) from command line. Run a terminal and move to /usr/NX/var :
$ cd /usr/NX/var/log/nxnode/
$ sudo tar cvfz NoMachine-log.tar.gz log
2. All logs located in the $HOME/.nx directory from the Ubuntu laptop NoMachine Server installation:
When a session is unexpectedly disconnected, the client issues a dialog asking for saving logs. Accept to save these logs.
If the dialog asking for saving log is not available, please refer to the following article, section “How to gather client side logs”:
For the Windows to Windows issue:
The NoMachine \var\log folder on Windows is:
%PROGRAMDATA%\NoMachine\var\log on Windows Vista, 7 and 8
\Documents and Settings\All Users\NoMachine\var\log on Windows XP
To compress it, right-click the file or folder, point to Send To, and then click Compressed (zipped) Folder.
You can email all of these logs to forum[at]nomachine[dot]com. Please be sure to reference the following “First Results” so that we can match up the logs to the appropriate topic from the forums.
If the files are too big for to send via email please let us know and we will find an alternative method for you to upload them via FTP or you can try to attach them to a reply to this topic.
NoMachine has an open Trouble Report about that directory growing very large. You can read more about it here: https://www.nomachine.com/TR11K04084 . There is also a workaround to help with this issue while NoMachine works on a fix.
The failed session ID’s can help in the case of a failed session to understand what went wrong.
To uninstall on Mac you can follow the instructions here:
http://www.nomachine.com/DT09K00056#3.3. It’s basically just choosing Move to Trash to uninstall on Mac.
Sorry I meant what specific version of Centos are you running?
Automatic updates are not available as of yet. This feature will be coming soon I think. For today you can download the newest packages from the website and update manually as outlined here:
Instructions will vary a bit depending on whether your installation Red Hat, Debian, etc.
What version did you download for testing? The base NoMachine product or one of the Enterprise or Terminal Server eval products?
You are using the base NoMachine for Linux free product? What Linux distribution are you using to host the NoMachine install? e.g. Red Hat, etc.
Can you still make a connection to your NoMachine installation even with this error message?