NoMachine stopped working after upgrade to 13.1

Forum / NoMachine for Linux / NoMachine stopped working after upgrade to 13.1

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #49387
    smat70xc
    Participant

    Hi,

    I am on Manjaro Linux machine.  NoMachine was working wonderful over months until upgrade to version 13.1. Since this no connection is possible or more exactly it will be established and very very soon closed again.

    I tried to reinstall version 12.12  – it worked previously perfectly but now it’s same as in a new version 13.1

    I tried to set

    (base) [me@me-qm2 ~]$ sudo cat .nx/config/player.cfg | grep -ni hardware
    50:  <option key=”Enable hardware accelerated decoding” value=”disabled” />

    as I read in another topics here, but with no success.

    In the log file (in very first effort something more, afterwards only few lines repeated over and over as can be seen at the bottom of the  file – starting with the key 2598) I see:

    (base) [me@me-qm2 log]$ sudo cat nxserver.log
    21327 21327 10:47:44 154.342 Redis: Server started, Redis version 3.0.7.
    21327 21327 2024-08-27 10:47:44 183.133 ServerRedisServer: Finishing handler.
    21327:signal-handler (1724748464) Received SIGTERM scheduling shutdown…
    21327 21327 2024-08-27 10:47:44 183.170 ServerRedisServer: Waiting handler to terminate.
    21327 21327 10:47:44 254.255 Redis: User requested shutdown….
    21327 21327 10:47:44 254.291 Redis: Saving the final RDB snapshot before exiting..
    21327 21327 10:47:44 260.713 Redis: Redis is now ready to exit, bye bye….
    21327 21327 2024-08-27 10:47:44 260.905 ServerRedisServer: Cleaning up handler information.
    21625 21625 2024-08-27 10:47:46 355.405 NXSERVER Connected from remote machine ‘127.0.0.1’ using protocol ‘SSH’.
    21625 21625 2024-08-27 10:47:46 383.029 NXSERVER Remote machine ‘127.0.0.1’ disconnected.
    21713 21713 10:47:47 400.064 Redis: Server started, Redis version 3.0.7.
    21713 21713 10:47:47 400.277 Redis: DB loaded from disk: 0.000 seconds.
    21713 21713 2024-08-27 10:47:47 439.759 NXSERVER Starting LS 8.12.12 and services.
    21713 21713 2024-08-27 10:47:47 439.805 NXSERVER System information: Manjaro Linux, standalone.
    22072 22072 2024-08-27 10:48:33 927.360 NXSERVER Shutting down NoMachine server and services.
    21713 21713 2024-08-27 10:48:34 005.393 ServerRedisServer: Finishing handler.
    21713:signal-handler (1724748514) Received SIGTERM scheduling shutdown…
    21713 21713 2024-08-27 10:48:34 005.438 ServerRedisServer: Waiting handler to terminate.
    21713 21713 10:48:34 019.488 Redis: User requested shutdown….
    21713 21713 10:48:34 019.532 Redis: Saving the final RDB snapshot before exiting..
    21713 21713 10:48:34 026.267 Redis: Redis is now ready to exit, bye bye….
    21713 21713 2024-08-27 10:48:34 026.477 ServerRedisServer: Cleaning up handler information.
    22072 22072 2024-08-27 10:48:34 196.245 NXSERVER WARNING! NXRedis: Cannot get output for command ‘get’. Resending commands failed.
    22072 22072 2024-08-27 10:48:34 196.337 NXSERVER WARNING! NXRedisScript: wrong sha: ” for script ‘getAllCMWithTheirPids’. Trying get one more time.
    22072 22072 10:48:34 199.832 Redis: Server started, Redis version 3.0.7.
    22072 22072 10:48:34 200.044 Redis: DB loaded from disk: 0.000 seconds.
    22072 22072 2024-08-27 10:48:34 243.261 ServerRedisServer: Finishing handler.
    22072:signal-handler (1724748514) Received SIGTERM scheduling shutdown…
    22072 22072 2024-08-27 10:48:34 243.313 ServerRedisServer: Waiting handler to terminate.
    22072 22072 10:48:34 300.478 Redis: User requested shutdown….
    22072 22072 10:48:34 300.526 Redis: Saving the final RDB snapshot before exiting..
    22072 22072 10:48:34 307.719 Redis: Redis is now ready to exit, bye bye….
    22072 22072 2024-08-27 10:48:34 307.916 ServerRedisServer: Cleaning up handler information.
    22141 22141 10:48:34 670.735 Redis: Server started, Redis version 3.0.7.
    22141 22141 10:48:34 670.951 Redis: DB loaded from disk: 0.000 seconds.
    22141 22141 2024-08-27 10:48:34 710.358 NXSERVER Starting LS 8.12.12 and services.
    22141 22141 2024-08-27 10:48:34 710.406 NXSERVER System information: Manjaro Linux, standalone.
    22380 22380 2024-08-27 10:48:56 791.106 NXSERVER Connected from remote machine ‘192.168.1.72’ using protocol ‘NX’.
    Info: Handler started with pid 22380 on Tue Aug 27 10:48:56 2024.
    Info: Handling connection from 192.168.1.72 port 49388 on Tue Aug 27 10:48:56 2024.
    22380 22380 2024-08-27 10:49:09 732.417 NXSERVER User ‘me’ logged in from ‘192.168.1.72’ using authentication method NX-password.
    Info: Connection from 192.168.1.72 port 49388 closed on Tue Aug 27 10:49:10 2024.
    Info: Handler with pid 22380 terminated on Tue Aug 27 10:49:10 2024.
    22380 22380 2024-08-27 10:49:11 888.228 NXSERVER User ‘me’ from ‘192.168.1.72’ logged out.
    22380 22380 2024-08-27 10:49:11 888.529 NXSERVER Remote machine ‘192.168.1.72’ disconnected.
    22141 22141 2024-08-27 10:51:41 902.480 NXSERVER Shutting down NoMachine server and services.
    22141 22141 2024-08-27 10:51:51 320.284 NXSERVER WARNING! Timeout of 10 seconds reached for terminating of node process with pid 22206.
    22141 22141 2024-08-27 10:51:51 320.396 NXSERVER WARNING! Killing node process with pid 22206.
    22141 22141 2024-08-27 10:51:51 334.151 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user me –priority realtime –mode 0 –pid 45’ with pid ‘22200/22200’ finished with exit code 9 after 196,570 seconds.
    22141 22141 2024-08-27 10:51:51 334.231 NXSERVER WARNING! 04C17C39D26394306E571631F8B18856 nxnode died with exit code 9.
    22141 22141 2024-08-27 10:51:51 550.746 ServerRedisServer: Finishing handler.
    22141:signal-handler (1724748711) Received SIGTERM scheduling shutdown…
    22141 22141 2024-08-27 10:51:51 550.791 ServerRedisServer: Waiting handler to terminate.
    22141 22141 10:51:51 580.844 Redis: User requested shutdown….
    22141 22141 10:51:51 580.880 Redis: Saving the final RDB snapshot before exiting..
    22141 22141 10:51:51 587.458 Redis: Redis is now ready to exit, bye bye….
    22141 22141 2024-08-27 10:51:51 587.689 ServerRedisServer: Cleaning up handler information.
    950 950 10:52:17 674.198 Redis: Server started, Redis version 3.0.7.
    950 950 10:52:17 674.919 Redis: DB loaded from disk: 0.001 seconds.
    950 950 2024-08-27 10:52:17 795.844 NXSERVER Starting LS 8.12.12 and services.
    950 950 2024-08-27 10:52:17 795.910 NXSERVER System information: Manjaro Linux, standalone.
    2261 2261 2024-08-27 10:54:34 948.183 NXSERVER Shutting down NoMachine server and services.
    950 950 2024-08-27 10:54:35 025.870 ServerRedisServer: Finishing handler.
    950:signal-handler (1724748875) Received SIGTERM scheduling shutdown…
    950 950 2024-08-27 10:54:35 025.920 ServerRedisServer: Waiting handler to terminate.
    950 950 10:54:35 039.978 Redis: User requested shutdown….
    950 950 10:54:35 040.022 Redis: Saving the final RDB snapshot before exiting..
    950 950 10:54:35 046.905 Redis: Redis is now ready to exit, bye bye….
    950 950 2024-08-27 10:54:35 047.124 ServerRedisServer: Cleaning up handler information.
    2261 2261 2024-08-27 10:54:35 219.575 NXSERVER WARNING! NXRedis: Cannot get output for command ‘get’. Resending commands failed.
    2261 2261 2024-08-27 10:54:35 219.651 NXSERVER WARNING! NXRedisScript: wrong sha: ” for script ‘getAllCMWithTheirPids’. Trying get one more time.
    2261 2261 10:54:35 222.742 Redis: Server started, Redis version 3.0.7.
    2261 2261 10:54:35 223.029 Redis: DB loaded from disk: 0.000 seconds.
    2261 2261 2024-08-27 10:54:35 266.070 ServerRedisServer: Finishing handler.
    2261:signal-handler (1724748875) Received SIGTERM scheduling shutdown…
    2261 2261 2024-08-27 10:54:35 266.120 ServerRedisServer: Waiting handler to terminate.
    2261 2261 10:54:35 323.302 Redis: User requested shutdown….
    2261 2261 10:54:35 323.343 Redis: Saving the final RDB snapshot before exiting..
    2261 2261 10:54:35 330.097 Redis: Redis is now ready to exit, bye bye….
    2261 2261 2024-08-27 10:54:35 330.278 ServerRedisServer: Cleaning up handler information.
    2329 2329 10:54:35 695.305 Redis: Server started, Redis version 3.0.7.
    2329 2329 10:54:35 695.646 Redis: DB loaded from disk: 0.000 seconds.
    2329 2329 2024-08-27 10:54:35 734.035 NXSERVER Starting LS 8.12.12 and services.
    2329 2329 2024-08-27 10:54:35 734.083 NXSERVER System information: Manjaro Linux, standalone.

    2598 2598 2024-08-27 10:56:18 089.252 NXSERVER Connected from remote machine ‘192.168.1.72’ using protocol ‘NX’.
    Info: Handler started with pid 2598 on Tue Aug 27 10:56:18 2024.
    Info: Handling connection from 192.168.1.72 port 46854 on Tue Aug 27 10:56:18 2024.
    2598 2598 2024-08-27 10:56:35 192.059 NXSERVER User ‘me’ logged in from ‘192.168.1.72’ using authentication method NX-password.
    Info: Connection from 192.168.1.72 port 46854 closed on Tue Aug 27 10:56:35 2024.
    Info: Handler with pid 2598 terminated on Tue Aug 27 10:56:35 2024.
    2598 2598 2024-08-27 10:56:36 965.543 NXSERVER User ‘me’ from ‘192.168.1.72’ logged out.
    2598 2598 2024-08-27 10:56:36 965.908 NXSERVER Remote machine ‘192.168.1.72’ disconnected.
    2329 2329 10:59:36 053.813 Redis: 100 changes in 300 seconds. Saving….

    Any idea what’s wrong and how to get NoMachine to run? Is it something with Redis …

    Thanks a lot in advance

    Matthias

    #49400
    Bilbotine
    Participant

    Hi smat70xc,

    We are not able to reproduce this bug, so your logs would be helpful to understand what goes wrong.

    If needed, here’s the procedure to collect NoMachine logs: NoMachine – Collect Server And Client Logs Manually – Knowledge Base

    Can you please send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email?

    #49445
    smat70xc
    Participant

    Hi, using NoMachine from my Mac works, but still not if I try to connect from Manjaro ;-(

    It works also from Android 😉

    #49466
    Bilbotine
    Participant

    Hi smat70xc,

    The logs you sent us don’t show anything wrong.

    But from your description, it seems that the problem is on the client side on that machine (Manjaro).

    Considering this, please check the player side logs (they are in ~/.nx ), and tell us what error it says, etc.

    #49478
    smat70xc
    Participant

    Hi Bilbotine,

    thanks a lot for your time and the response.

    Yesterday and also today I spent few hours trying to understand what’s going wrong.

    After connecting from mac, android and also from my machine but under another linux’es it seems that it something tiny in my Manjaro 24.

    The log file on the client site on Manjaro 24 delivers no really a hint or maybe I interpret as a problem with PulseAudio and it is not correctly or the consequence of that makes some troubles thought?

    I see only many repetitions of a below inserted sequence:

    >>>
    Connection failure: Connection refused
    pa_context_connect() failed: Connection refused
    2294 2294 2024-08-30 17:41:15 224.824 NXNODE   WARNING! Process ‘/bin/pactl info’ with pid ‘2310/2310’ finished with exit code 1 after 0,003 seconds.
    <<<

    For sake of completeness I attach the full nxserver.log from .nx directory.

    Have a nice day

    Matthias

    #49479
    smat70xc
    Participant

    On my another Manjaro machine with similar behavior I can see something more in the client nxserver.log after a try to connect

    #49514
    Britgirl
    Keymaster

    Hi, please submit the logs to forum[at]nomachine[dot]com. I see that the link was not visible in an earlier reply from Bilbotine, so here’s the link.

    https://kb.nomachine.com/DT07S00243

    Please use the title of this topic as the subject of your email.

    #49523
    Britgirl
    Keymaster

    It’s strange that you can connect from other clients without issues. As you said the problem appears to be on the Manjaro device you are connecting from, so for that we need the Player logs which were missing. See “Fourth Step: Collect Client Side Logs” in the link I gave previously.

    #49539
    Britgirl
    Keymaster

    Thanks for the player logs.

    A crash is observed:

    18874 18874 2024-09-03 09:26:14 034,814 ClientSignal: WARNING! Child process ‘18979’ died because of signal ’11’, ‘SIGSEGV’.

    It would be useful to see a backtrace from the core file/crash report. Please see the instructions here:
    https://kb.nomachine.com/AR09L00810

    #49557
    Britgirl
    Keymaster

    You mentioned that you had tried disabling HW decoding, but the crash report indicates that HW decoding is still being loaded. You need to “Quit NoMachine player” before changing it, edit the key to<option key=”Enable hardware accelerated decoding” value=”disabled” /> and save. Open NoMachine and start the session.

    Please refer to this article for reference:

    https://kb.nomachine.com/AR07U01202

Viewing 10 posts - 1 through 10 (of 10 total)

This topic was marked as solved, you can't post.