Can’t connect anymore after update

Forums / NoMachine for Linux / Can’t connect anymore after update

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #19017
    AvatartheV0ID
    Participant

    I’ve been using NoMachine (free version) for a few months now and it always worked like a charm. I’m running the server on a Linux computer (Ubuntu 16.04 Gnome). I didn’t update it for a few weeks or so, and after I did so today, and rebooted, it stopped working. I cannot connect anymore. I did not change any configuration and did not install any new software packages. The version I am using now is 6.0.78-1.

    The logfile /usr/NX/var/log/nxserver.log on the server system says:

    2018-07-13 18:35:00 633.465 840 NXSERVER Starting LS 6.0.78 and services.
    2018-07-13 18:35:00 633.803 840 NXSERVER System information: Ubuntu 16.04.4 LTS, standalone.
    2018-07-13 18:35:01 271.454 840 NXSERVER ERROR! NXFrameBuffer failed to start.
    2018-07-13 18:35:01 298.647 840 NXSERVER WARNING! Process '/etc/NX/nxserver --virtualsession --sessionid 990BE6BCE8AA441CD807CB668DABC1FF' with pid '888/888' finished with signal 11 after 0,650 seconds.
    2018-07-13 18:35:01 912.794 840 NXSERVER ERROR! NXFrameBuffer failed to start.
    2018-07-13 18:35:01 913.585 840 NXSERVER WARNING! Process '/etc/NX/nxserver --virtualsession --sessionid 7E92DD8A0333559CD791C1B702D9DD70' with pid '904/904' finished with signal 11 after 0,610 seconds.
    2018-07-13 18:35:33 558.732 840 NXSERVER ERROR! NXFrameBuffer failed to start.
    2018-07-13 18:35:33 559.296 840 NXSERVER WARNING! Process '/etc/NX/nxserver --virtualsession --sessionid E3C4C6A4E0931F649F8FB7098CA8D1B8' with pid '1073/1073' finished with signal 11 after 0,609 seconds.

    What could this possibly be and how can I fix this?

    #19028
    Avatarkroy
    Contributor

    We cannot reproduce the problem. Are you able to start desktop physically on that machine? Are there any core dumps? It should be placed on home directory. More info about debug cores you can find there: https://www.nomachine.com/AR09L00810. If you use apport – look for cores on the /var/crash directory.

    To unpack:

    sudo apport-unpack

    Navigate to the and core file should be named there CoreDump. Then follow instruction from above link.

    Please send file with backtrace and also .xsession-errors (which should be on home directory) and compressed folder with logs (/usr/NX/var/log/) to forum[at]nomachine[dot]com.

    #19027
    AvatartheV0ID
    Participant

    Nevermind. Re-installing the NoMachine server (newest version) solved the problem.

    #19038
    AvatarZhiliang Hu
    Participant

    I have the same problem — after updates (both system and local client):

    /usr/NX/bin/nxserver –version: NoMachine – Version 5.1.62 (on a RHEL7)

    Mac OSX (High Sierra) Client: NoMachine – Version 5.3.25 (5.3.25)

    Upon connection: “Could not connect to the server. Error is 61: Connection refused”

    while “sudo /usr/NX/bin/nxserver –start” shows:

    NX> 161 Enabled service: nxserver.

    NX> 162 Disabled service: nxnode.

    NX> 162 Disabled service: nxd.

    My firewall port 4000 is open… and above all, it was working over the past year.

    #19052
    AvatarBritgirl
    Keymaster

    @Zhiliang,  if you’ve kept your NoMachine software up-to-date using automatic updates or manual installation, you should also be on 5.3.25 on the server. Or, are you referring to the update of your system OS?

     

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

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