Forum / NoMachine Terminal Server Products / Failed to connect to socket /tmp/dbus – Connection refused
- This topic has 8 replies, 3 voices, and was last updated 6 years, 3 months ago by Mth.
-
AuthorPosts
-
June 15, 2018 at 09:29 #18717DennisGParticipant
We are using nxserver 6.0.66:
[djg3@rgs03 bin]$ ./nxserver –version
NoMachine Small Business Server Subscription – Version 6.0.66on several ProLiant WS460c G6 servers running RHEL 6.7.
With a hundred or so users. Fairly uneventful, problem free setup.
But, there is one account that keeps getting the following after attempting to start a new desktop after the initial connection:
“When I connect it accepts my password, I select Create a
New Virtual Desktop (as I have before), and get the following error: “Could
not connect to session bus: Failed to connect to socket /tmp/dbus-GdQdHrEZ8Y:
Connection refused” followed by “Could not acquire a name on session bus” ”The “GdQdHrEZ8Y” string changes with successive attempts.
The user is running NM v5.3.25 on a MAC, but has tried connection using colleague’s system with the same result.
I have attached the session, connection, options, and settings logs from the users MAC.
Thanks,
Dennis
[email removed]
June 15, 2018 at 10:06 #18722BritgirlKeymasterIt would be a good idea to submit the server-side logs as well. Instructions on how to enable debug are here:https://www.nomachine.com/DT10O00163.
Please send them and the other attachments which didn’t attach above to forum[at]nomachine[dot]com.
June 22, 2018 at 10:57 #18814DennisGParticipantI will set up the log level and have the user reproduce the problem. Thanks. Sorry for the delay, I didn’t realize my topic went to Terminal Server Products and kind of lost track….. I’ll get this info to you in a few days or so.
Thanks very much.
Dennis
June 25, 2018 at 08:28 #18817DennisGParticipantI just emailed the logs per your suggestion. For this test the line produced was
Failed to connect to socket /tmp/dbus-ZnYUk9b20V:
Connection refusedinstead of
Failed to connect to socket /tmp/dbus-GdQdHrEZ8Y:
Connection refusedThere are lines in the nodes /var/log/messages file I can send also if needed.
Thanks for your help
Dennis
June 26, 2018 at 07:44 #18821MthContributorHello.
I do not know what happened, but the nxserver.log file inside the archive you sent us
is completely empty. Can you check what happened there and send us the logs again
with reproduced problem?Please also send us the configuration files server.cfg and node.cfg from the server machine
to help investigating. Also if this user that is experiencing problems have his own
node configuration file (<username>.node.cfg), please send it too.And question: is this user having any other processes running on this server that
can interfere with starting desktop environment? Like another desktop environment inside
a virtual frame buffer? If yes please tell us which ones./Mth
June 28, 2018 at 18:25 #18835DennisGParticipantResending the logs. Error was reproduced about 8:15 this morning (Jun 28). I noticed that the nxserver.log is still emptyL As Mth suggested, I have also attached the server.cfg and node.cfg files with my edits to the SessionLogLimit and Clean values.
Using ps -ef and lsof I don’t see the account name (vr044) having anything running/open on the node. (Maybe there’s another way to check??).
Thanks for your help,
Dennis
July 4, 2018 at 09:17 #18864MthContributorHello.
So the nxserver.log is empty because of the configuration key EnableSyslogSupport
is set to 1 in both configuration files.
If this is the case, please provide us with the logs from the system log file accessible
via the standard syslog interface (e.g. in /var/log/syslog, can depend on configuration).This logs can be identified by nxnode and nxserver nametags.
/Mth
July 11, 2018 at 09:10 #18980DennisGParticipantI just emailed /var/log/messages and /var/log/secure files from one of the nodes where the problem has occurred. Thanks,
Dennis
July 13, 2018 at 08:26 #18998MthContributorSo from the messages file there is this from NX:
Jun 27 06:18:43 rgs05 nxnode[40980]: WARNING! Process ‘/bin/bash -c exec -a – /bin/bash -c ‘/etc/gdm/Xsession gnome-session” with pid ‘41015/41015’ finished with exit code 1 after 12,906 seconds.
Jun 27 06:18:43 rgs05 nxnode[40980]: ERROR! Session application terminated abnormallySo we can rule out NX processes generating problem on their own.
There can be two things to cause problems here:
1. The session wrapper ‘/etc/gdm/Xsession’. Please check if there was any modifications done to this file that could point to any problems.
2. User ‘vr044’ configuration. Could You check any unorthodox changes in this user configuration files? Especially if they are connected with gnome-session, so around in .config/gnome* or /.gnome* in this user home directory.
/Mth
-
AuthorPosts
This topic was marked as solved, you can't post.