On 12/11/06, James Oakley <[EMAIL PROTECTED]> wrote:
On Monday 11 December 2006 6:50 pm, Greg Freemyer wrote: > NX> 1000 NXNODE - Version 1.5.0-50 OS (GPL) > NX> 700 Session id: Forensic1000-1001-05F4A69B17CB9F316E1161050DC96BEC > NX> 705 Session display: 1001 > NX> 703 Session type: unix-kde > NX> 701 Proxy cookie: 16b0982cc9fa49cb82e49a52db9fbe82 > NX> 702 Proxy IP: 24.99.15.6 > NX> 706 Agent cookie: 16b0982cc9fa49cb82e49a52db9fbe82 > 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. > /usr/bin/nxserver: line 1077: 2566 Terminated sleep > $AGENT_STARTUP_TIMEOUT > Can't open > /var/lib/nxserver/db/running/sessionId{05F4A69B17CB9F316E1161050DC96BEC}: > No such file or directory. > NX> 1006 Session status: closed > mv: cannot stat > `/var/lib/nxserver/db/running/sessionId{05F4A69B17CB9F316E1161050DC96BEC}': > No such file or directory > Killed by signal 15.It looks like it's trying to connect to a running session that's not actually running. Try looking at the session list with nxserver --list and terminating them. -- James Oakley [EMAIL PROTECTED]
nxserver --list is showing nothing. ie. it runs and shows column titles, but no sessions. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
