Forum / NoMachine for Linux / Cannot get output for command: evalsha after resending
- This topic has 5 replies, 3 voices, and was last updated 3 years, 9 months ago by Carin.
-
AuthorPosts
-
January 12, 2021 at 10:22 #31213manjarouser1Participant
I have NoMachine 7.0 running on Manjaro with KDE and when I try to connect to it from a Windows 10 machine I get
Error: Cannot create a new display.
Looking at server side logs I see this in nxserver.log
59227 59227 2021-01-11 17:12:25 569.592 NXSERVER User 'admin' logged in from '10.4.255.131' using authentication method NX-password.
59263 59263 2021-01-11 17:12:57 580.337 NXSERVER WARNING! NXRedis: timeout for command evalsha which is 10 has been reached.
59263 59263 2021-01-11 17:13:07 590.370 NXSERVER Previous message repeated 1 time
59263 59263 2021-01-11 17:13:07 590.493 NXSERVER WARNING! NXRedis: failed twice connection to db.
59263 59263 2021-01-11 17:13:07 590.578 NXSERVER ERROR! NXRedis: Cannot get output for command: evalsha after resending.
59227 59227 2021-01-11 17:13:07 606.340 NXSERVER ERROR! Received error from nxserver --daemon nxFrameBuffer error while starting
59227 59227 2021-01-11 17:13:07 676.738 NXSERVER User 'admin' from '10.4.255.131' logged out.
59304 59304 2021-01-11 17:18:10 005.620 NXSERVER User 'admin' logged in from '10.4.255.131' using authentication method NX-password.
59338 59338 2021-01-11 17:18:14 109.924 NXSERVER ERROR! Limit of 1 virtual sessions has been reached.
59338 59338 2021-01-11 17:18:14 112.233 NXSERVER ERROR! Cannot specify is local node base on ':' (NXNodeExec, /usr/NX/lib/perl/nxserver/NXNodeExec.pm, 2592, NXNodes::isRemoteNode).
59304 59304 2021-01-11 17:18:14 113.442 NXSERVER ERROR! Received error from nxserver --daemon NX> 599 ERROR: Reached the maximum number of concurrent virtual sessions on this server.
59304 59304 2021-01-11 17:18:14 200.388 NXSERVER User 'admin' from '10.4.255.131' logged out.
59413 59413 2021-01-11 17:22:44 381.501 NXSERVER User 'admin' logged in from '10.4.255.131' using authentication method NX-password.
59413 59413 2021-01-11 17:22:59 738.784 NXSERVER User 'admin' from '10.4.255.131' logged out.
59445 59445 2021-01-11 17:23:02 413.832 NXSERVER User 'admin' logged in from '10.4.255.131' using authentication method NX-password.
59479 59479 2021-01-11 17:23:16 149.689 NXSERVER WARNING! NXRedis: timeout for command evalsha which is 10 has been reached.
59479 59479 2021-01-11 17:23:26 161.145 NXSERVER Previous message repeated 1 time
59479 59479 2021-01-11 17:23:26 161.387 NXSERVER WARNING! NXRedis: failed twice connection to db.
59479 59479 2021-01-11 17:23:26 161.562 NXSERVER ERROR! NXRedis: Cannot get output for command: evalsha after resending.
59445 59445 2021-01-11 17:23:26 183.119 NXSERVER ERROR! Received error from nxserver --daemon nxFrameBuffer error while starting
59445 59445 2021-01-11 17:23:26 256.752 NXSERVER User 'admin' from '10.4.255.131' logged out.January 12, 2021 at 17:25 #31226og00rContributorDid you try already solutions from other manjaro topic?
https://forums.nomachine.com/topic/connecting-to-manjaro-gnomeI mean:
1. Create a backup of nx PAM configuration (sudo cp -a /etc/pam.d/nx /etc/pam.d/nx.original). Then change /etc/pam.d/nx in this way:auth include system-login
account include system-login
password include system-login
session include system-login2. Change DefaultDesktopCommand in /usr/NX/etc/node.cfg
DefaultDesktopCommand “env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus /usr/bin/startplasma-x11”
3. Restart NoMachine:
sudo /usr/NX/bin/nxserver –restart
Point 2 is different than in mentioned topic, specially for KDE version
If for some reason problem persist please enable debug logs, restart NoMachine (command from above point 3) and try to connect again with enabled logs. Gather logs and send them please. Article about enabling logs:
https://www.nomachine.com/DT10O00162#1
(Please restart NoMachine before point 2 in that article)January 13, 2021 at 08:50 #31243manjarouser1ParticipantThanks for the steps. I already followed that before except point #2. Now after, making all the changes just like you suggested.. i see this in nxserver.log
137457 137457 2021-01-12 09:39:47 728.216 NXSERVER User 'admin' logged in from '10.4.255.160' using authentication method NX-password.
137491 137491 2021-01-12 09:40:05 753.051 NXSERVER WARNING! NXRedis: timeout for command evalsha which is 10 has been reached.
137491 137491 2021-01-12 09:40:15 764.639 NXSERVER Previous message repeated 1 time
137491 137491 2021-01-12 09:40:15 764.862 NXSERVER WARNING! NXRedis: failed twice connection to db.
137491 137491 2021-01-12 09:40:15 765.062 NXSERVER ERROR! NXRedis: Cannot get output for command: evalsha after resending.
137386 137386 2021-01-12 09:40:15 785.233 NXSERVER ERROR! NXFrameBuffer failed to start.
137457 137457 2021-01-12 09:40:15 786.384 NXSERVER ERROR! Received error from nxserver --daemon nxFrameBuffer error while starting
137457 137457 2021-01-12 09:40:15 860.964 NXSERVER User 'admin' from '10.4.255.160' logged out.Debug log attached
Attachments:
January 14, 2021 at 15:37 #31267og00rContributorDid you update from version 7.0.x to newest 7.0.x? Looks like some problem with update could you try make fresh install?
1) Uninstall current NoMachine.
2) Remove directories /usr/NX and /etc/NX
3) Install newest NoMachine packages.Second point is really important.
If for some reason reinstallation is not possible and if there exist file /usr/NX/etc/nodes.db then running commandsudo /etc/NX/nxserver –updatedb
could help. If there is /usr/NX/etc/nodes.db.backup instead, you could try to move file manually
sudo mv /usr/NX/etc/nodes.db.backup /usr/NX/etc/nodes.db
and then run
sudo /etc/NX/nxserver –updatedb
restart nomachine after that.
sudo /etc/NX/nxserver –restart
January 15, 2021 at 10:02 #31279manjarouser1ParticipantThanks, that did it!
Where can I find keyboard shortcuts?
January 20, 2021 at 14:18 #31388CarinParticipantHi manjarouser1,
We are glad it worked!
For the keyboard shortcuts, you can find the instructions in this article: https://www.nomachine.com/DT11R00177 (see Fig. 2 and 3).
-
AuthorPosts
This topic was marked as solved, you can't post.