Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Old users can't log in via NX after upgrade from 11.4 to 12.1

  1. #1

    Default Old users can't log in via NX after upgrade from 11.4 to 12.1

    Hi everyone, I have a problem that I've tried to fix for over a week now and have run out of ideas and hair. (Apologies if this is the wrong forum for this.)

    Problem is that after upgrading from 11.4 to 12.1, my old user (one that existed in 11.4) cannot connect via NX/FreeNX, however new users (created in 12.1) can.

    Obviously, the fact that new users can connect successfully means that the various packages and configuration are functional. I suspect some sort of cache/session artifact is the problem... but I don't know where to go looking for said artifact. I also don't know if maybe something else has changed in 12.1 that's causing the problem.

    I've tried connecting to a desktop session with NX as well as simply a console, neither work. A core file appears in the user directory each time. I've tried replacing the old user's home directory with a new one from skeleton, I've tried deleting the user and creating a new one with same uid, I've tried clearing /tmp completely each boot...

    nxserver.log provides no hint as to why the sessions fail for the old user and succeed for the new ones.

    Any ideas where I should look?

    Versions:
    openSUSE 11.4, 12.1 i586 with LXDE desktop
    NX server 3.4.0 (tried from various repositories)
    FreeNX 0.7.3 (tried from various repositories)
    NX client 3.4.0 on Windows7

  2. #2

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    If new users can connect but old users can't, I would say that the dsa key pair has changed. Try to import the key saved in /var/lib/nxserver/home/.ssh/client_id_dsa.key on the server in the nomachine client (if you're using that one) by clicking on configure -> General -> Key... The key here should match the one on the server. It is saved among various session settings in the file ~/.nx/config/sessionname.nxs. You can also copy this file from a user who can connect, change ownership and login name. To clear the cache, click on Advanced -> Remove all cache files.

  3. #3

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Hi please_try_again, thanks for the response. BTW, it's your repository I'm currently using for FreeNX/NX, so I appreciate your response even more.

    I checked the dsa key and they match... that actually makes sense, since I used the nomachine key to keep stuff as simple as possible and that shouldn't have changed between 11.4 and 12.1. Just in case, I deleted the cache in the NX Client as well as deleted and re-created the session.

    When I try to connect, I seem to pass authentication without issue. The black !M window appears for about 3 seconds, then it disappears to be replaced by a dialog "The connection with the remote server was shut down. Please check the state of your network connection." There is a another dialog that states "Session suse12.1-local failed". When I click on the Detail button, I get the following:

    Info: Display running with pid '8068' and handler '0x71f9c'.

    NXPROXY - Version 3.4.0

    Copyright (C) 2001, 2010 NoMachine.
    See NoMachine NX - Desktop Virtualization and Remote Access Management Software for more information.

    Info: Proxy running in client mode with pid '3788'.
    Session: Starting session at 'Mon Nov 28 22:44:59 2011'.
    Info: Connection with remote proxy completed.
    Warning: Unrecognized session type 'unix-desktop'. Assuming agent session.
    Info: Using ADSL link parameters 512/24/1/0.
    Info: Using cache parameters 4/4096KB/16384KB/16384KB.
    Info: Using pack method 'adaptive-7' with session 'unix-desktop'.
    Info: Using ZLIB data compression 1/1/32.
    Info: Using ZLIB stream compression 4/4.
    Info: No suitable cache file found.
    Info: Forwarding X11 connections to display ':0'.
    Info: Listening to font server connections on port '11002'.
    Session: Session started at 'Mon Nov 28 22:45:03 2011'.
    Info: Established X server connection.
    Info: Using shared memory parameters 0/0K.
    Error: Connection with remote peer broken.
    Error: Please check the state of your network and retry.
    Session: Terminating session at 'Mon Nov 28 22:45:07 2011'.
    Session: Session terminated at 'Mon Nov 28 22:45:07 2011'.


    Checking nxserver.log suggests that nxserver thinks all is well:

    Info: Using fds #4 and #3 for communication with nxnode.
    HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.4.0)
    NX> 105 hello NXCLIENT - Version 3.2.0
    NX> 134 Accepted protocol: 3.2.0
    NX> 105 SET SHELL_MODE SHELL
    NX> 105 SET AUTH_MODE PASSWORD
    NX> 105 login
    NX> 101 User: myuser
    NX> 102 Password:
    Info: Auth method: ssh Password:
    NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.4.0)
    NX> 716 Slave mode started successfully.
    nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.4.0)
    nxnode_reader: NX> 716 finished
    nxnode_reader: NX> 1001 Bye.

    NX> 103 Welcome to: linux-up2t user: myuser
    NX> 105 listsession --user="myuser" --status="suspended,running" --geometry="1050x
    1680x32+render" --type="unix-application"
    NX> 127 Sessions list of user 'myuser' for reconnect:

    Display Type Session ID Options Depth Screen
    Status Session Name
    ------- ---------------- -------------------------------- -------- ----- -------
    ------- ----------- ------------------------------


    NX> 148 Server capacity: not reached for user: myuser
    NX> 105 startsession --virtualdesktop="1" --application="startlxde" --link="ads
    l" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --defer="1"
    --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="tumb
    leweed-local" --type="unix-application" --geometry="800x600" --client="winnt" --
    keyboard="pc105/en_US" --screeninfo="800x600x32+render"

    &virtualdesktop=1&application=startlxde&link=adsl&backingstore=1&encryption=1&ca
    che=16M&images=64M&defer=1&shmem=1&shpix=1&strict=0&composite=1&media=0&session=
    tumbleweed-local&type=unix-application&geometry=800x600&client=winnt&keyboard=pc
    105/en_US&screeninfo=800x600x32+render&clientproto=3.2.0&user=myuser&userip=192.16
    8.91.1&uniqueid=DAFF60F243659C665AE417EE02F81505&display=1002&host=127.0.0.1
    nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.4.0)
    NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.4.0)
    server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3
    .4.0)
    nxnode_reader: NX> 700 Session id: linux-up2t-1002-DAFF60F243659C665AE417EE02F81
    505
    NX> 700 Session id: linux-up2t-1002-DAFF60F243659C665AE417EE02F81505
    server_nxnode_echo: NX> 700 Session id: linux-up2t-1002-DAFF60F243659C665AE417EE
    02F81505
    nxnode_reader: NX> 705 Session display: 1002
    NX> 705 Session display: 1002
    server_nxnode_echo: NX> 705 Session display: 1002
    nxnode_reader: NX> 703 Session type: unix-application
    NX> 703 Session type: unix-application
    server_nxnode_echo: NX> 703 Session type: unix-application
    nxnode_reader: NX> 701 Proxy cookie: 86dc0fc28a53f018242fc4b7d45676ab
    NX> 701 Proxy cookie: 86dc0fc28a53f018242fc4b7d45676ab
    server_nxnode_echo: NX> 701 Proxy cookie: 86dc0fc28a53f018242fc4b7d45676ab
    nxnode_reader: NX> 702 Proxy IP: 127.0.0.1
    NX> 702 Proxy IP: 127.0.0.1
    server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
    nxnode_reader: NX> 706 Agent cookie: 86dc0fc28a53f018242fc4b7d45676ab
    NX> 706 Agent cookie: 86dc0fc28a53f018242fc4b7d45676ab
    server_nxnode_echo: NX> 706 Agent cookie: 86dc0fc28a53f018242fc4b7d45676ab
    nxnode_reader: NX> 704 Session cache: unix-application
    NX> 704 Session cache: unix-application
    server_nxnode_echo: NX> 704 Session cache: unix-application
    nxnode_reader: NX> 707 SSL tunneling: 1
    NX> 707 SSL tunneling: 1
    server_nxnode_echo: NX> 707 SSL tunneling: 1
    nxnode_reader: NX> 1009 Session status: starting
    NX> 1009 Session status: starting
    server_nxnode_echo: NX> 1009 Session status: starting
    nxnode_reader: NX> 710 Session status: running
    NX> 710 Session status: running
    server_nxnode_echo: NX> 710 Session status: running
    nxnode_reader: NX> 1002 Commit
    NX> 1002 Commit
    server_nxnode_echo: NX> 1002 Commit
    nxnode_reader: NX> 1006 Session status: running
    NX> 1006 Session status: running
    NX> 105 session_status DAFF60F243659C665AE417EE02F81505 Running
    server_nxnode_echo: NX> 1006 Session status: running
    bye
    Bye
    NX> 999 Bye
    Info: Closing connection to slave with pid 20637.
    nxnode_reader: 1001 Bye.
    1001 Bye.
    nxnode_reader: NX> 1001 Bye.
    NX> 1001 Bye.
    server_nxnode_echo: NX> 1001 Bye.
    Info: Closing connection to slave with pid 20637.

    The only place where I see a problem, is in the nx user session file (~/.nx/C-linux-up2t-1002-DAFF60F243659C665AE417EE02F81505/session):

    NXAGENT - Version 3.4.0

    Copyright (C) 2001, 2010 NoMachine.
    See NoMachine NX - Desktop Virtualization and Remote Access Management Software for more information.

    Info: Agent running with pid '21174'.
    Session: Starting session at 'Mon Nov 28 22:45:27 2011'.
    Info: Proxy running in server mode with pid '21174'.
    Info: Waiting for connection from '127.0.0.1' on port '5002'.
    Info: Accepted connection from '127.0.0.1'.
    Info: Connection with remote proxy completed.
    Info: Using ADSL link parameters 512/24/1/0.
    Info: Using agent parameters 5000/10/50/0/0.
    Info: Using cache parameters 4/4096KB/16384KB/16384KB.
    Info: Using pack method 'adaptive-7' with session 'unix-desktop'.
    Info: Using ZLIB data compression 1/1/32.
    Info: Using ZLIB stream compression 4/4.
    Info: No suitable cache file found.
    Info: Listening to X11 connections on display ':1002'.
    Info: Established X client connection.
    Info: Using shared memory parameters 1/1/0/0K.
    *** glibc detected *** /usr/lib/NX/nxagent: free(): invalid pointer: 0x084f0e48
    ***
    ======= Backtrace: =========
    /lib/libc.so.6(+0x6ed8b)[0xb73a0d8b]
    /lib/libc.so.6(cfree+0x9b)[0xb73a528b]
    /usr/lib/NX/nxagent[0x80b4830]
    /usr/lib/NX/nxagent[0x80b5c5e]
    /usr/lib/NX/nxagent[0x80c2e9d]
    /usr/lib/NX/nxagent[0x80543c9]
    /lib/libc.so.6(__libc_start_main+0xf3)[0xb734b003]
    /usr/lib/NX/nxagent[0x8054cd9]
    ======= Memory map: ========
    08048000-08488000 r-xp 00000000 08:02 2444 /usr/lib/NX/nxagent
    08488000-08489000 r--p 00440000 08:02 2444 /usr/lib/NX/nxagent
    08489000-084ae000 rw-p 00441000 08:02 2444 /usr/lib/NX/nxagent
    084ae000-08775000 rw-p 00000000 00:00 0 [heap]
    b7127000-b718d000 rw-p 00000000 00:00 0
    b718d000-b718f000 r-xp 00000000 08:02 2280 /usr/lib/libXdamage.so.1.1.0
    b718f000-b7190000 r--p 00001000 08:02 2280 /usr/lib/libXdamage.so.1.1.0
    b7190000-b7191000 rw-p 00002000 08:02 2280 /usr/lib/libXdamage.so.1.1.0
    b7191000-b7198000 r-xp 00000000 08:02 2381 /usr/lib/libXrandr.so.2.2.0
    b7198000-b7199000 r--p 00006000 08:02 2381 /usr/lib/libXrandr.so.2.2.0
    b7199000-b719a000 rw-p 00007000 08:02 2381 /usr/lib/libXrandr.so.2.2.0
    b719a000-b719b000 rw-p 00000000 00:00 0
    b719b000-b71a0000 r-xp 00000000 08:02 2283 /usr/lib/libXtst.so.6.1.0
    b71a0000-b71a1000 r--p 00004000 08:02 2283 /usr/lib/libXtst.so.6.1.0
    b71a1000-b71a2000 rw-p 00005000 08:02 2283 /usr/lib/libXtst.so.6.1.0
    b71a2000-b71be000 r-xp 00000000 08:02 5981 /lib/libgcc_s.so.1
    b71be000-b71bf000 r--p 0001b000 08:02 5981 /lib/libgcc_s.so.1
    b71bf000-b71c0000 rw-p 0001c000 08:02 5981 /lib/libgcc_s.so.1
    b71c0000-b72a2000 r-xp 00000000 08:02 23397 /usr/lib/libstdc++.so.6.0.16
    b72a2000-b72a6000 r--p 000e2000 08:02 23397 /usr/lib/libstdc++.so.6.0.16
    b72a6000-b72a7000 rw-p 000e6000 08:02 23397 /usr/lib/libstdc++.so.6.0.16
    b72a7000-b72ae000 rw-p 00000000 00:00 0
    b72ae000-b72ee000 r-xp 00000000 08:02 2403 /usr/lib/libjpeg.so.62.0.0
    b72ee000-b72ef000 r--p 00040000 08:02 2403 /usr/lib/libjpeg.so.62.0.0
    b72ef000-b72f0000 rw-p 00041000 08:02 2403 /usr/lib/libjpeg.so.62.0.0
    b72f0000-b7300000 rw-p 00000000 00:00 0
    b7300000-b732a000 r-xp 00000000 08:02 187 /usr/lib/libpng12.so.0.46.0
    b732a000-b732b000 r--p 00029000 08:02 187 /usr/lib/libpng12.so.0.46.0
    b732b000-b732c000 rw-p 0002a000 08:02 187 /usr/lib/libpng12.so.0.46.0
    b732c000-b732d000 rw-p 00000000 00:00 0
    b732d000-b7330000 r-xp 00000000 08:02 5893 /lib/libdl-2.14.1.so
    b7330000-b7331000 r--p 00002000 08:02 5893 /lib/libdl-2.14.1.so
    b7331000-b7332000 rw-p 00003000 08:02 5893 /lib/libdl-2.14.1.so
    b7332000-b7498000 r-xp 00000000 08:02 76 /lib/libc-2.14.1.so
    b7498000-b749a000 r--p 00165000 08:02 76 /lib/libc-2.14.1.so
    b749a000-b749b000 rw-p 00167000 08:02 76 /lib/libc-2.14.1.so
    b749b000-b749e000 rw-p 00000000 00:00 0
    b749e000-b74a0000 r-xp 00000000 08:02 3056 /usr/lib/libXcomposite.so.1.0.0
    b74a0000-b74a1000 r--p 00001000 08:02 3056 /usr/lib/libXcomposite.so.1.0.0
    b74a1000-b74a2000 rw-p 00002000 08:02 3056 /usr/lib/libXcomposite.so.1.0.0
    b74a2000-b74a7000 r-xp 00000000 08:02 3055 /usr/lib/libXfixes.so.3.1.0
    b74a7000-b74a8000 r--p 00004000 08:02 3055 /usr/lib/libXfixes.so.3.1.0
    b74a8000-b74a9000 rw-p 00005000 08:02 3055 /usr/lib/libXfixes.so.3.1.0
    b74a9000-b74b2000 r-xp 00000000 08:02 2404 /usr/lib/NX/lib/libXrender.so.1
    .2.2
    b74b2000-b74b3000 r--p 00008000 08:02 2404 /usr/lib/NX/lib/libXrender.so.1
    .2.2
    b74b3000-b74b4000 rw-p 00009000 08:02 2404 /usr/lib/NX/lib/libXrender.so.1
    .2.2
    b74b4000-b74b5000 rw-p 00000000 00:00 0
    b74b5000-b74bf000 r-xp 00000000 08:02 612 /usr/lib/NX/lib/libXcompshad.so
    .3.4.0
    b74bf000-b74c0000 r--p 00009000 08:02 612 /usr/lib/NX/lib/libXcompshad.so
    .3.4.0
    b74c0000-b74c1000 rw-p 0000a000 08:02 612 /usr/lib/NX/lib/libXcompshad.so
    .3.4.0
    b74c1000-b74cf000 r-xp 00000000 08:02 532 /usr/lib/NX/lib/libXcompext.so.
    3.4.0
    b74cf000-b74d0000 r--p 0000d000 08:02 532 /usr/lib/NX/lib/libXcompext.so.
    3.4.0
    b74d0000-b74d1000 rw-p 0000e000 08:02 532 /usr/lib/NX/lib/libXcompext.so.
    3.4.0
    b74d1000-b74d2000 rw-p 00000000 00:00 0
    b74d2000-b75c7000 r-xp 00000000 08:02 526 /usr/lib/NX/lib/libXcomp.so.3.4
    .0
    b75c7000-b75c8000 ---p 000f5000 08:02 526 /usr/lib/NX/lib/libXcomp.so.3.4
    .0
    b75c8000-b75cb000 r--p 000f5000 08:02 526 /usr/lib/NX/lib/libXcomp.so.3.4
    .0
    b75cb000-b75cc000 rw-p 000f8000 08:02 526 /usr/lib/NX/lib/libXcomp.so.3.4
    .0
    b75cc000-b75d1000 rw-p 00000000 00:00 0
    b75d1000-b75e2000 r-xp 00000000 08:02 3111 /usr/lib/libXpm.so.4.11.0
    b75e2000-b75e3000 r--p 00010000 08:02 3111 /usr/lib/libXpm.so.4.11.0
    b75e3000-b75e4000 rw-p 00011000 08:02 3111 /usr/lib/libXpm.so.4.11.0
    b75e4000-b760d000 r-xp 00000000 08:02 5931 /lib/libm-2.14.1.so
    b760d000-b760e000 r--p 00028000 08:02 5931 /lib/libm-2.14.1.so
    b760e000-b760f000 rw-p 00029000 08:02 5931 /lib/libm-2.14.1.so
    b760f000-b7610000 rw-p 00000000 00:00 0
    b7610000-b7626000 r-xp 00000000 08:02 5091 /lib/libz.so.1.2.5
    b7626000-b7627000 r--p 00015000 08:02 5091 /lib/libz.so.1.2.5
    b7627000-b7628000 rw-p 00016000 08:02 5091 /lib/libz.so.1.2.5
    b7628000-b7730000 r-xp 00000000 08:02 242 /usr/lib/NX/lib/libX11.so.6.2
    b7730000-b7731000 ---p 00108000 08:02 242 /usr/lib/NX/lib/libX11.so.6.2
    b7731000-b7732000 r--p 00108000 08:02 242 /usr/lib/NX/lib/libX11.so.6.2
    b7732000-b7735000 rw-p 00109000 08:02 242 /usr/lib/NX/lib/libX11.so.6.2
    b7735000-b7736000 rw-p 00000000 00:00 0
    b7736000-b7746000 r-xp 00000000 08:02 2399 /usr/lib/NX/lib/libXext.so.6.4
    b7746000-b7747000 r--p 0000f000 08:02 2399 /usr/lib/NX/lib/libXext.so.6.4
    b7747000-b7748000 rw-p 00010000 08:02 2399 /usr/lib/NX/lib/libXext.so.6.4
    b7748000-b77cc000 r-xp 00000000 08:02 17213 /usr/lib/libfreetype.so.6.7.2
    b77cc000-b77d0000 r--p 00083000 08:02 17213 /usr/lib/libfreetype.so.6.7.2
    b77d0000-b77d1000 rw-p 00087000 08:02 17213 /usr/lib/libfreetype.so.6.7.2
    b77d6000-b77d7000 rw-p 00000000 00:00 0
    b77d7000-b77e0000 r-xp 00000000 08:02 3134 /usr/lib/libXcursor.so.1.0.2
    b77e0000-b77e1000 r--p 00008000 08:02 3134 /usr/lib/libXcursor.so.1.0.2
    b77e1000-b77e2000 rw-p 00009000 08:02 3134 /usr/lib/libXcursor.so.1.0.2
    b77e2000-b77e5000 rw-p 00000000 00:00 0
    b77e5000-b7804000 r-xp 00000000 08:02 3402 /lib/ld-2.14.1.so
    b7804000-b7805000 r--p 0001f000 08:02 3402 /lib/ld-2.14.1.so
    b7805000-b7806000 rw-p 00020000 08:02 3402 /lib/ld-2.14.1.so
    bfa9b000-bfabc000 rw-p 00000000 00:00 0 [stack]
    ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
    Warning: Parent process appears to be dead. Exiting keeper.
    xrdb: Connection refused
    xrdb: Can't open display ':1002'

    I don't think this is good... but I don't know how to further debug what's going wrong with nxagent - especially why it fails with myuser, but works with newuser...

  4. #4

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Are the clients Linux machines? If so, you can look in the session administrator if there are older sessions that you could remove. You'll start it with the command:
    Code:
     /usr/NX/bin/nxclient -admin
    The sessions are in subdirectories of the user's ~/.nx on the client, normally starting with S followed by -servername, then the display number defined in /etc/nxserver/node.conf (default is 1000), then a 32bit session ID. Example:

    Code:
    ls ~/.nx
    cache-unix-xdm  config  S-odeon-1000-D6DAAE4F000F6C1EC16A89D72FE33556  temp
    Remove those directories if there are any.

    On the server, when a session is active, you should see a directory starting with C, followed by -servername, display number, etc. Example:

    Code:
    ls ~/.nx
    cache-unix-xdm  config  C-vashti-1001-B221DAA5B4593F73EA7B84CA2E8C91AC  temp
    These directories contain session and error logs. When you close the session, the session directory is deleted from the server. If you have such directories for sessions that no longer exist, you should delete them.

    If you see the M and a black screen, you are connected but the client is unable to start its window manager. It depends on the type of session you choose in the nxclient, the default display manager of the user on the server, and whether a login manager (like xdm, kdm, gdm) is used to start X or not. The FreeNX version in my repo is working with xdm/gdm/kdm but will start the default session directly rather than the login manager itself (gdm, kdm login screen where you could choose the desktop session you want). The No Machine NX server will display the gdm or kdm login screen. Older FreeNX versions will display a black screen at this point.

    I haven't done any change on my FreeNX package for 12.1. It's exactly the same as the one for 11.4. It was built automatically in OBS after I added the repo for 12.1. I have installed the 32bit version in kvm virtual machines and on the server I'm working on (32 bit also). It's working. I assume the 64bit will work too - I will be able to tell as soon as I get a 64bit 12.1 installed and configured.

  5. #5

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    The station is Windows 7, running the NoMachine 3.4 client.. I've tried having it run 'startlxde' after connection as well as simply open a terminal window.

    I changed the node.conf to keep the session data around (SESSION_LOG_CLEAN=0) so I could see the contents of the session file. The session file is where I found the error data below (full data is in my previous post). Any idea what it means or how to debug it?

    Info: Established X client connection.
    Info: Using shared memory parameters 1/1/0/0K.
    *** glibc detected *** /usr/lib/NX/nxagent: free(): invalid pointer: 0x084f0e48
    ***
    ======= Backtrace: =========
    /lib/libc.so.6(+0x6ed8b)[0xb73a0d8b]
    /lib/libc.so.6(cfree+0x9b)[0xb73a528b]
    /usr/lib/NX/nxagent[0x80b4830]
    /usr/lib/NX/nxagent[0x80b5c5e]
    /usr/lib/NX/nxagent[0x80c2e9d]
    /usr/lib/NX/nxagent[0x80543c9]
    /lib/libc.so.6(__libc_start_main+0xf3)[0xb734b003]
    /usr/lib/NX/nxagent[0x8054cd9]
    ======= Memory map: ========
    ...
    Warning: Parent process appears to be dead. Exiting keeper.
    xrdb: Connection refused
    xrdb: Can't open display ':1002'

  6. #6

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Quote Originally Posted by susestylin View Post
    Warning: Parent process appears to be dead. Exiting keeper.
    xrdb: Connection refused
    xrdb: Can't open display ':1002'
    DISPLAY is the value of DISPLAY_BASE (defined in node.conf), which gets incremented by each connection. For some reason, "old" users are not allowed to open the display on the server. IMO, it is a X authentification issue, not a FreeNX problem. Are there any MIT-MAGIC-COOKIEs in the user ~/.nx/temp (files starting with "serverauth") that could be removed? What about renaming the user's ~/.nx directory and initiate a new connection?

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    On 2011-11-28 06:06, susestylin wrote:
    > A core file appears in the user directory each
    > time.


    I think it is possible to see what program crashed and dumped core.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  8. #8

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Quote Originally Posted by please_try_again View Post
    DISPLAY is the value of DISPLAY_BASE (defined in node.conf), which gets incremented by each connection. For some reason, "old" users are not allowed to open the display on the server. IMO, it is a X authentification issue, not a FreeNX problem. Are there any MIT-MAGIC-COOKIEs in the user ~/.nx/temp (files starting with "serverauth") that could be removed? What about renaming the user's ~/.nx directory and initiate a new connection?
    I renamed the ~/.nx directory on the Windows client, renamed the ~/.nx directory in the user account on the server, and I ran nxsetup --uninstall --purge ; nxsetup --install --setup-nomachine-key --clean --purge on the server. As far as I can know, any FreeNX/NX-related data should have been created new.

    Like you, I don't think it's a FreeNX problem per se. I suspect it is related to what happens after the NX connection is established. I just don't know what the next step is, so I don't know where to look or how to debug.

  9. #9

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Quote Originally Posted by robin_listas View Post
    On 2011-11-28 06:06, susestylin wrote:
    > A core file appears in the user directory each
    > time.


    I think it is possible to see what program crashed and dumped core.
    Hi Robin, that's a good suggestion. Any idea what tool I use to read the file? When I vi it there's a lot of binary garbage and really long lines.

  10. #10

    Default Re: Old users can't log in via NX after upgrade from 11.4 to 12.1

    Quote Originally Posted by susestylin View Post
    I renamed the ~/.nx directory on the Windows client, renamed the ~/.nx directory in the user account on the server, and I ran nxsetup --uninstall --purge ; nxsetup --install --setup-nomachine-key --clean --purge on the server. As far as I can know, any FreeNX/NX-related data should have been created new.
    All right. It's a Windows client. Last time I used Windows ... it was on Earth before the eugenic war ... I didn't know it was still used in the Alpha Quadrant. OK, I'm kidding. But I'm afraid I cannot be very helpful with Windows clients. I know what I would try next however: connect to the server as the same user (the one who cannot access the display) but from another machine, preferably a Linux client.


    Quote Originally Posted by susestylin View Post
    Like you, I don't think it's a FreeNX problem per se. I suspect it is related to what happens after the NX connection is established.
    Yes. This error clearly indicates that you are connected (aware of the display) but you cannot access it.

    Code:
    xrdb: Connection refused
    xrdb: Can't open display ':1002'

    Quote Originally Posted by susestylin View Post
    I just don't know what the next step is, so I don't know where to look or how to debug.
    Hmmm ... Maybe you could start a new thread about this DISPLAY access problem. I would assume that people looking in this thread are mainly people interested in FreeNX, probably not the majority of users. But I'm sure there are others who might do better suggestions if a subject catches their attention.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •