Server status is stuck on querying the server

Forums / NoMachine for Linux / Server status is stuck on querying the server

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #39700
    ehammer99
    Participant

    I have freshly installed NoMachine 7.10.1 on Debian 11 to be used as a client. The server status window is just stuck at “Querying the server” and the nxserver.service fails to start according to systemctl.

    ● nxserver.service – NoMachine Server daemon
    Loaded: loaded (/lib/systemd/system/nxserver.service; enabled; vendor preset: enabled)
    Active: failed (Result: start-limit-hit) since Mon 2022-08-15 19:28:31 EDT; 5s ago
    Process: 11959 ExecStart=/etc/NX/nxserver –daemon (code=exited, status=0/SUCCESS)
    Main PID: 11959 (code=exited, status=0/SUCCESS)
    CPU: 333ms

    Aug 15 19:28:31  systemd[1]: nxserver.service: Scheduled restart job, restart counter is at 5.
    Aug 15 19:28:31  systemd[1]: Stopped NoMachine Server daemon.
    Aug 15 19:28:31  systemd[1]: nxserver.service: Start request repeated too quickly.
    Aug 15 19:28:31  systemd[1]: nxserver.service: Failed with result ‘start-limit-hit’.
    Aug 15 19:28:31  systemd[1]: Failed to start NoMachine Server daemon.

     

    There are no logs for some reason

    $ ls -l ~/.nx
    total 68
    drwx—— 2 user user  4096 Aug 15 19:07 cache
    drwx—— 2 user user  4096 Aug 15 19:18 config
    drwxr-xr-x 2 user user 12288 Aug 15 19:26 fonts
    drwx—— 2 user user  4096 Aug 15 19:27 M-localhost-35214-C52C740248BF7FD08E9C82929E921891
    drwxr-xr-x 2 user user  4096 Aug 15 19:16 nxdevice
    -rw——- 1 user user     0 Aug 15 19:07 nxerror.log
    -rw——- 1 user user     0 Aug 15 19:07 nxserver.log
    drwx—— 2 user user  4096 Aug 15 19:27 R-localhost-6143-67AEC333F705F8C352AB66EE8BC87077
    drwx—— 2 user user  4096 Aug 15 19:18 R-localhost-63232-14B3415C45E3957A99F9EF77B6A5D244
    drwx—— 2 user user  4096 Aug 15 19:12 S-localhost-24803-9AF21A51B9C8EB663CD95C302F9A7C86
    drwx—— 2 user user  4096 Aug 15 19:19 S-localhost-27541-C3337215F56D26984557228DF016F438
    drwx—— 2 user user  4096 Aug 15 19:07 S-localhost-27728-0F42E45AEA06E6E3DF8699E793B1512F
    drwx—— 2 user user  4096 Aug 15 19:24 S-localhost-32046-7CC17B236591B61CB72E1B99735689F4
    drwx—— 2 user user  4096 Aug 15 19:10 S-localhost-33824-B160612A0F555188266820CCA40E147A
    drwx—— 2 user user  4096 Aug 15 19:11 S-localhost-53482-C8EA08846428A501F691D244E389DEC6
    drwx—— 2 user user  4096 Aug 15 19:21 S-localhost-60174-E54C1A531311C2F17C717FAC93B998CC
    drwxr-xr-x 2 user user  4096 Aug 15 19:26 temp

     

    If I try and download or upload a file to a server there is nothing to indicate that anything happens. The transfer status is empty and the logs do not change from 0 bytes in size.

    I attempt to change settings on the server settings page and it asks me for a password, I input correctly, and attempt to restart the server fails yet again.

    Where are the logs? Is there a debug mode I can enable somehow? This problem is extremely cryptic.

    #39730
    Britgirl
    Keymaster

    We are not aware of similar issues on Debian 11.

    The “S-log” excerpts you pasted are not from NoMachine. If you have an NX legacy or derivative installed on that machine, or had it installed, I would suggest to uninstall NoMachine and remove all traces including the home, reinstall NoMachine and start again, making sure that you’ve also removed any trace of what other product you might have had (even inadvertently) on that machine.

    sudo dpkg --purge nomachine 
    sudo rm -rf /usr/NX /etc/NX /var/NX .nx

    Then reinstall the NoMachine product of your choice.

    You should check server-side logs (which are in /usr/NX/var/log) – not client.

    For your reference:

    Collect server side logs automatically
    https://kb.nomachine.com/DT11R00182

    or

    Collect server and client logs manually
    https://kb.nomachine.com/DT11R00181

    #39750
    ehammer99
    Participant

    Thank you for the response.

    It appears this error may have been a symptom of a greater OS problem. As earlier today my entire system had a kernel panic and refused to boot (Symptoms included a corrupted root and efi partition)

    Most likely the issue was attributed to this larger system error.

    Reinstall of the OS and NoMachine has resolved the server query problem.

    #39783
    Britgirl
    Keymaster

    Most likely the issue was attributed to this larger system error.

    Thanks for letting us know.

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

You must be logged in to reply to this topic.