Can’t start Opensuse 13.1

Forum / NoMachine for Linux / Can’t start Opensuse 13.1

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #8424
    alaios
    Participant

    Dear all,

    I cannot start my service in OpenSuse 13.1

    I have searched and tried a lot.

    It looks my problem is similar to the https://www.nomachine.com/forums/topic/nxserver-cant-start-on-opensuse-13-2

    but there is no solution given there.

    I am running:/etc/issue

    Welcome to openSUSE 13.1 “Bottle” – Kernel \r (\l).

    service nxserver status
    nxserver.service – NoMachine Server daemon
    Loaded: loaded (/lib/systemd/system/nxserver.service; enabled)
    Active: active (exited) since Wed 2015-09-30 10:15:58 CEST; 9min ago
    Process: 13591 ExecStop=/etc/NX/nxserver –shutdown –silence –systemd (code=exited, status=0/SUCCESS)
    Process: 13657 ExecStart=/etc/NX/nxserver –startup –systemd (code=exited, status=0/SUCCESS)
    Main PID: 13657 (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/nxserver.service
    `-13679 /usr/NX/bin/nxserver.bin root 13657 –daemon
    Sep 30 10:15:58 caracus nxserver[13657]: NX> 161 Enabled service: nxnode.
    Sep 30 10:15:58 caracus systemd[1]: Started NoMachine Server daemon.

    Although servers look that is running I can not see it being binded on the configured port

    My linux box see the following ports from the nx

    netstat -tulpn | grep nx

    tcp 0 0 127.0.0.1:12001 0.0.0.0:* LISTEN 14533/nxnode.bin
    tcp 0 0 127.0.0.1:25001 0.0.0.0:* LISTEN 14575/nxclient.bin
    tcp 0 0 127.0.0.1:59474 0.0.0.0:* LISTEN 14779/nxplayer.bin
    tcp 0 0 127.0.0.1:21622 0.0.0.0:* LISTEN 14515/nxserver.bin
    tcp 0 0 127.0.0.1:7001 0.0.0.0:* LISTEN 14533/nxnode.bin
    tcp 0 0 ::1:7001 :::* LISTEN 14533/nxnode.bin
    udp 34176 0 0.0.0.0:5353 0.0.0.0:* 14575/nxclient.bin
    udp 0 0 0.0.0.0:5353 0.0.0.0:* 14575/nxclient.bin

    when my server starts gives me the following

    tail -n 7 /usr/NX/var/log/nxerror.log

    11631 11631 10:02:54 224.276 Socket: WARNING! Can’t bind the IPv6 socket.
    11631 11631 10:02:54 224.339 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.
    11764 11764 10:06:04 264.188 Socket: WARNING! Can’t bind the IPv6 socket.
    11764 11764 10:06:04 264.253 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.
    11781 11781 10:06:08 842.630 Socket: WARNING! Can’t bind the IPv6 socket.
    11781 11781 10:06:08 842.692 Socket: WARNING! Error is 99 ‘Cannot assign requested address’.

    I have also disabled firewall but this is not the problem. My /etc/hosts looks like (in the post I gave at the beginning where the user had the similar problem there was a solution mentioned for hosts file)

    127.0.0.1 localhost

    # special IPv6 addresses
    ::1 localhost ipv6-localhost ipv6-loopback
    fe00::0 ipv6-localnet
    ff00::0 ipv6-mcastprefixff02::1 ipv6-allnodes
    ff02::2 ipv6-allrouters
    ff02::3 ipv6-allhosts
    127.0.0.1 MyPc.IamHidingThisPart

    ipvs6 was disabled but I enabled it but this did not fix the problem.
    And at last the nxserver.log

    tail -n 20 /usr/NX/var/log/nxserver.log

    2015-09-30 10:32:13 812.752 14515 NXSERVER NXPL::NXGetRandomString start.
    2015-09-30 10:32:13 812.819 14515 NXSERVER NXPL::NXGetRandomString stop.
    2015-09-30 10:32:13 812.884 14515 NXSERVER isLoginWindowByNXPL random string: 080F4A7A94957849D3E75B905C555172
    2015-09-30 10:32:13 812.975 14515 NXSERVER isLoginWindowByNXPL tempfile: /var/NX/nx/.nx/080F4A7A94957849D3E75B905C555172.lcookie_2
    2015-09-30 10:32:13 813.198 14515 NXSERVER isLoginWindowByNXPL addCookie(/var/NX/nx/.nx/080F4A7A94957849D3E75B905C555172.lcookie_2, :0, MIT-MAGIC-COOKIE-1, ********) return 0
    2015-09-30 10:32:13 813.272 14515 NXSERVER isLoginWindowByNXPL set XAUTHORITY to /var/NX/nx/.nx/080F4A7A94957849D3E75B905C555172.lcookie_2
    2015-09-30 10:32:13 813.338 14515 NXSERVER isWMRunningByDisplay call on :0
    2015-09-30 10:32:13 814.145 14515 NXSERVER NXPL::NXWmRunning(:0) [1]
    2015-09-30 10:32:13 814.260 14515 NXSERVER isLoginWindowByNXPL isWMRunningByDisplay return [1]
    2015-09-30 10:32:13 814.327 14515 NXSERVER isLoginWindowByNXPL clean out file: /var/NX/nx/.nx/080F4A7A94957849D3E75B905C555172.lcookie_2
    2015-09-30 10:32:13 814.435 14515 NXSERVER isLoginWindowByNXPL(0, ********) return [1]
    2015-09-30 10:32:13 814.540 14515 NXSERVER PhysicSessions::isLoginWindowByCK missed all checkpoints
    2015-09-30 10:32:13 814.867 14515 NXSERVER Checking local session with line: NX> 153 1000:apa:0:opensuse+13.1+%%28bottle%%29+%%28x86_64%%29:desktop:session:1596:%%2fvar%%2flib%%2fkdm%%2fAuthFiles%%2fA%%3a0-bPBiyb:*****:1:empty .
    2015-09-30 10:32:13 815.052 14515 NXSERVER Checking local X server for pid: 1596.
    2015-09-30 10:32:13 815.128 14515 NXSERVER Session C954C5034DB258B08EF7DA0E23618AF2 associated with pid 1596 is already known.
    2015-09-30 10:32:13 815.197 14515 NXSERVER Found node assigned to session C954C5034DB258B08EF7DA0E23618AF2.
    2015-09-30 10:32:13 815.275 14515 NXSERVER Node stdin: FD#10, stdout: FD#11, socket FD#10.
    2015-09-30 10:32:13 815.345 14515 NXSERVER Session C954C5034DB258B08EF7DA0E23618AF2 associated with pid 1596 is already running.
    2015-09-30 10:32:13 815.424 14515 NXSERVER Found node assigned to session C954C5034DB258B08EF7DA0E23618AF2.
    2015-09-30 10:32:13 815.489 14515 NXSERVER Node stdin: FD#10, stdout: FD#11, socket FD#10.

    Can you please help me see what the problem might be?

    Regards

    Alex

    #8478
    Haven
    Participant

    Hello Alex,
    None of those errors looks critical.

    We will more need debug NoMachine server logs to investigate further.
    Please follow the instructions here:
    https://www.nomachine.com/AR07K00677
    Send them to forum[at]nomachine[dot]com

    After enable debug logs on problematic machine please execute:
    /etc/NX/nxserver --restart
    and after that try to reproduce the issue.

    Additionally please provide output of command:
    ps -Af | grep X

    Please make sure that NX is in ClientConnectionMethods key in server.cfig file.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.