You are not logged in.
freenx broken after update last night to
[root@thor sydney]# pacman -Q freenx nxserver nx-common nxclient
freenx 0.5.0-4
nxserver 2.0.0-2
nx-common 2.0.0-2
nxclient 2.0.0-2conneting is okay but doesent get a screen, drop me back to nxclient -username -password query.
errorcode
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
1006 unix-kde 09A8FAB4D30C260A8A25486F6E2D4B84 -RD--PSA 32 2560x1024 Running test
1002 unix-kde 0F7A54E34314C65FA54B808F8E21FEA7 -RD--PSA 32 1280x1024 Running test
1003 unix-kde 1646A8CA905B637D8A449F52CE820A09 -RD--PSA 32 2560x1024 Running test
1000 unix-kde 3C02D4DC721F621CC45BD34CBAD6FC95 -RD--PSA 32 2560x1024 Running test
1000 unix-kde 49F7564B3E6BB798E5F3C4C653118424 -RD--PSA 32 2560x1024 Running test
1000 unix-kde 5565903B0B2119C5028C251D8F31A09C -RD--PSA 32 1280x1024 Running test
1005 unix-kde 5B0ADA9A5CC548828F354405B4AC7506 -RD--PSA 32 2560x1024 Running test
1001 unix-kde 6B3C133132242CD962FFCF7D61B7D3A4 -RD--PSA 32 1280x1024 Running test
1000 unix-kde 6BBC1212888EFED70D86A164C227963F -RD--PSA 32 2500x950 Running Server
1004 unix-kde 7807E042247339BCA55B38694F9A65D9 -RD--PSA 32 2560x1024 Running test
1004 unix-kde 79485EC8C0F862F962166375F735E972 -RD--PSA 32 2560x1024 Running test
1001 unix-kde 8DA8A014EBC3AD906FD1BAD3CF19BB28 -RD--PSA 32 1280x1024 Running test
1001 unix-kde 918B5307F5A51A6AD71F65F47849113C -RD--PSA 32 2500x950 Running Server
1000 unix-kde 9A1FE621F0E741A8CD31A86818E2D4E5 -RD--PSA 32 2500x950 Running Server
1001 unix-kde B0E58BA45AAAAB06E0AC49BECEEA349A -RD--PSA 32 2560x1024 Running test
1000 unix-kde E4AFE4DB4C4A9E90D9582C32D74079BE -RD--PSA 32 2560x1024 Running test
NX> 148 Server capacity: not reached for user: sydney
NX> 105 startsession --session="Linux Server" --type="unix-kde" --cache="32M" --images="64M" --link="wan" --kbtype="pc102/de" --nodelay="1" --backingstore="never" --geometry="1024x768" --media="0" --agent_server="" --agent_user="" agent_password="******"" --screeninfo="1024x768x32+render"
NX> 1000 NXNODE - Version 1.5.0-50 OS (GPL)
NX> 700 Session id: thor-1000-A2A57E5DEB5289B5E57EF1C35470D499
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 0a32d88d49de9fafef81d8b86a638ec2
NX> 702 Proxy IP: 192.168.2.27
NX> 706 Agent cookie: 0a32d88d49de9fafef81d8b86a638ec2
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
NX> 1006 Session status: closed
/opt/NX/bin/nxserver: line 1077: 960 Terminated sleep $AGENT_STARTUP_TIMEOUT
Can't open /opt/NX/var/db/running/sessionId{A2A57E5DEB5289B5E57EF1C35470D499}: No such file or directory.
mv: cannot stat `/opt/NX/var/db/running/sessionId{A2A57E5DEB5289B5E57EF1C35470D499}': No such file or directory
Killed by signal 15.Thanks for helping
Offline
I've got exactly the same problem. I haven't got any time to investigate yet though.
Offline
to me this sounnds like the too long dir bug, i experienced on windows clients.
if you use windows client change it to a shorter path. On linux i haven't had this problem yet.
Offline
also you could try to clean your /opt/NX/var dirs, perhaps the old files just kill your setup
Offline
Hi tpowa,
Windows / Linux client, error is on both clients.
"clean your /opt/NX/var dirs" doesent work.
I remove and install again freenx nxserver nx-common.
Now works.
Offline
Same problem here!
The client gives a pretty clear information about the problem of a too long filename:
/opt/NX/bin/nxserver: line 371: /opt/NX/var/db/running/sessionId{sessionName=SCL-P&display=1000&status=Running&startTime=1207546565&foreignAddress=192.168.111.10&sessionRootlessMode=0&type=unix-kde&sessionId=&creationTime=1207546565&userName=root&serverPid=&screeninfo=1024x768x24+render&geometry=1024x768+288+193&host=127.0.0.1}: File name too long
cat: /opt/NX/var/db/running/sessionId{}: No such file or directoryNX> 280 Exiting on signal: 15
...but I don't know anyway how to solve. On older installation the upgrade didn't do any harm.
Edit: Sorry, this seems to be a different problem.
Last edited by jcci (2008-04-07 05:41:13)
Offline