NoMachine desktop – web access – no display available

Forums / NoMachine for Linux / NoMachine desktop – web access – no display available

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #16497
    devon
    Participant

    Hi

    Attempting to use the new web access available for 6.0 on the enterprise desktop evaluation.

    Upgrading from 5.3.12 Cloud Server + Enterprise Desktop to NoMachine Enterprise Desktop for Linux 6.0 in docker.

    While using 5.3 I was able to access the physical desktop of the nodes via web access through the cloud Server.

    Upgrading to 6.0 and directly accessing the desktop through the web is resulting in no physical desktop being available.

    I have attached the logs for the nxserver process marked as 5.3 and 6.0, additionally I have attached a screenshot of what appears when I log into web access, no display is appearing. In the 6.0 nxserver logs it appears that the localhost:4000 node cannot register. ( I am assuming this is the physical display node)

    I have ran the nxserver --useredit seluser --trusted physical command and the issue remains.

    I am using fluxbox as my window manager:

    seluser fluxbox -display :51.0 -verbose

    What would result in the physical display being available in 6.0 vs 5.3 ?

     

    Thank you,

    Devon

    #16514
    mlyn
    Contributor

    Hello,

    Based on the information you provided, we cannot say why you are encountering this issue. We will need logs to understand better.

    Please follow the instructions about collecting logs from https://www.nomachine.com/DT07M00098. After editing server.cfg and node.cfg please restart nxserver and send them to forum[at]nomachine[dot]com.

    Could you send also your Dockerfile, it will be also useful in investigation your issue.

    #16560
    devon
    Participant

    I have submitted the required info to the email address provided. It appears to be XServer related.

    NX> 161 Enabled service: nxserver.
    NX> 162 WARNING: Cannot find X servers running on this machine.
    NX> 162 WARNING: Connections to the physical display are not possible.
    NX> 161 Enabled service: nxd.
    NX> 161 Enabled service: nxhtd.
    + tail -f /usr/NX/var/log/nxserver.log
    2017-11-21 15:35:51 206.845 3465 NXSERVER Starting LEDE 6.0.62 and services.
    2017-11-21 15:35:51 206.948 3465 NXSERVER System information: Ubuntu 16.04.3 LTS, standalone.
    2017-11-21 15:35:51 221.209 3465 NXSERVER WARNING! Process ‘/usr/bin/dbus-send –system –dest=org.freedesktop.DBus –type=method_call –print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames’ with pid ‘3474/3474’ finished with exit code 1 after 0,004 seconds.
    2017-11-21 15:35:51 243.819 3465 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec nxhtd.sh start’ with pid ‘3482/3482’ finished with exit code 1 after 0,005 seconds.
    2017-11-21 15:36:40 790.559 12 NXSERVER Starting LEDE 6.0.62 and services.
    2017-11-21 15:36:40 790.644 12 NXSERVER System information: Ubuntu 16.04.3 LTS, standalone.
    2017-11-21 15:36:40 811.359 12 NXSERVER WARNING! Process ‘/usr/bin/dbus-send –system –dest=org.freedesktop.DBus –type=method_call –print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames’ with pid ’21/21′ finished with exit code 1 after 0,004 seconds.
    2017-11-21 15:37:28 265.595 370 NXSERVER User ‘nomachine’ logged in from ‘172.17.0.1’ using authentication method password.
    2017-11-21 15:37:28 266.854 361 NXWEBPLAYER User ‘nomachine’, admin ‘0’, logged into server ‘127.0.0.1’
    2017-11-21 15:42:25 965.631 346 NXSERVER WARNING! Cannot write to FD#8.
    2017-11-21 15:42:25 965.715 346 NXSERVER WARNING! Error is: 32, ‘Broken pipe’.

    #16591
    mlyn
    Contributor

    Hello,

    Thank you for sending the dockerfile.

    Based on provided information I think that in your docker machine there is no xsession running.
    This could be the reason that you are not able to connect there.

    To confirm this issue I need logs, so please uncomment key SessionLogLevel and change value to 7 in both configuration file: server.cfg and node.cfg

    after that please restart NoMachine using command nxserver –restart

    after that please send logs to: forum[at]nomachine[dot]com.
    Full instructions about collecting logs: https://www.nomachine.com/DT07M00098.

    #16597
    devon
    Participant

    Hi myln,

    I submitted the logs + docker app yesterday, I will send again in case a spam filter ate them up.

    Cheers,
    Devon

    #16599
    Britgirl
    Keymaster

    Hi Devon, we got them but debug wasn’t enabled which is what we need to look at 😉

    #16601
    devon
    Participant

    My bad!

    Replied to email with updated logs + app code.

    Cheers,
    Devon

    #16612
    mlyn
    Contributor

    hello,

    you use Enterprise Desktop this license allow to access to already existing physical desktop, NoMachine checks any session is running and allows remote access.

    In that case it looks like you don’t have any running X session, using system command ‘ps’ you can check if it is running.

    To make available connect to this machine you can manually start any X session.
    If ps command return some running X session please send this output and related with it logs with enabled debug (like in last send logs).

    When you use NoMachine in version 5.3.12 you also use docker with the same configuration (dockerfile)?

    In the last provided logs I don’t see an issue with registering node, from your first post:
    “In the 6.0 nxserver logs it appears that the localhost:4000 node cannot register.”

    #16652
    Britgirl
    Keymaster

    We have opened a Trouble Report https://www.nomachine.com/TR11O08272 and there is a workaround available.

    Please use the ‘notify me’ tool to receive a notification from us when the fix has been released.

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

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