Forum Replies Created
January 26, 2021 at 17:57 in reply to: Session negotiation failed: Cannot connect to the requested session #31594
It’s actually working now. Apparently X was down and that solved the issue.January 26, 2021 at 10:16 in reply to: Session negotiation failed: Cannot connect to the requested session #31567
I edited the sysctl.conf but it did not generate a core file. I also searched the syslog file and did not find any instances of nx. Instead, I ran the recommended command to extract system files:
journalctl -b -0 | grep -i "nxserver\|nxnode\|nxwebplayer" > journalctl.extract
I have sent that file. Hopefully it contains more relevant information.January 22, 2021 at 19:45 in reply to: Session negotiation failed: Cannot connect to the requested session #31500
It was easier for me to cd to the log directory and tar the entire log directory. I have sent the file, hopefully it contains the server log.January 22, 2021 at 19:20 in reply to: Session negotiation failed: Cannot connect to the requested session #31499
The instructions provided are not very helpful. I am confused as to what path I should be using when creating the tar file. What directory should I be in when running the command? I only have an .nx directory under my local /home directory. I keep getting an error saying “gzip: nxdir.tar.gz: No such file”.
I am curious though as to why this works. Can you explain exactly what unsetting LD_PRELOAD does? Thanks again!
Yes, the client is being started in a remote desktop. I can confirm that adding the above line works! The player now launches!
File has been sent.
For other users who may come across this, note that I had to run the following command to resolve an error with gdb (unefined symbol pyunicodeucs34_fromencodedobject), which occurs if the you have a different default path for Python:
Sent. But note that I had to kill the process because it was hanging. Hopefully it captured relevant information.