FreeNX - OpenSUSE 11.1 Intermittent Login Problems

English Applications
#1

Hello All,

Despite following the installation guide on the OpenSUSE website, I’m having intermittent login problems when using the NX Client to login to FreeNX on OpenSUSE 11.1 - below is the NX Client log:

NX> 203 NXSSH running with pid: 3440
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.0.8 on port: 22
NX> 211 The authenticity of host ‘192.168.0.8 (192.168.0.8)’ can’t be established.
RSA key fingerprint is f9:c6:5a:57:45:dd:68:dd:07:09:39:3d:8c:a2:2e:35.
Are you sure you want to continue connecting (yes/no)?
Warning: Permanently added ‘192.168.0.8’ (RSA) to the list of known hosts.
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 2.1.0-72 OS (GPL, using backend: not detected)
NX> 105 hello NXCLIENT - Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: admin
NX> 102 Password:
NX> 103 Welcome to: tcsrv1 user: admin
NX> 105 listsession --user=“admin” --status=“suspended,running” --geometry=“1024x768x32+render” --type=“unix-gnome”
NX> 127 Sessions list of user ‘admin’ for reconnect:

Display Type Session ID Options Depth Screen Status Session Name

NX> 148 Server capacity: not reached for user: admin
NX> 105 startsession --link=“adsl” --backingstore=“1” --encryption=“1” --cache=“16M” --images=“64M” --shmem=“1” --shpix=“1” --strict=“0” --composite=“1” --media=“0” --session=“Local” --type=“unix-gnome” --geometry=“1024x738” --client=“winnt” --keyboard=“pc102/gb” --screeninfo=“1024x738x32+render”

NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: not detected)
NX> 700 Session id: tcsrv1-1003-27DEA5D512371EF5E242ADFB96EDCA15
NX> 705 Session display: 1003
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 2e2602601b1e8908780363658319a943
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 2e2602601b1e8908780363658319a943
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate “/home/admin/.nx/F-C-tcsrv1-1003-27DEA5D512371EF5E242ADFB96EDCA15/session”. You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. Session log follows:
/usr/bin/nxserver: line 1371: 4164 Terminated sleep $AGENT_STARTUP_TIMEOUT
Can’t open /var/lib/nxserver/db/running/sessionId{27DEA5D512371EF5E242ADFB96EDCA15}: No such file or directory.
NX> 1006 Session status: closed
NX> 1001 Bye.
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{27DEA5D512371EF5E242ADFB96EDCA15}’: No such file or directory
NX> 280 Exiting on signal: 15

Any help would be greatly appreciated. I don’t understand why, on some occasions, I can login without problem!

Kind Regards,

Paul Smith.

#2

try deleting the NX cache:in the connection window, click on “Configure” then look for “delete files” or something
Maybe your problem happens after an aborted session?

#3

Thanks for your reply. This had occurred to me and I did try that but to no avail. This also happens on multiple user accounts from multiple thin client systems.

Have you any other ideas? Thanks for your thoughts!

#4

Has anyone any more ideas?

#5

> Has anyone any more ideas?

i don’t have a clue what NX or FreeNX is, but i bet if i googled i
could find a forum of folks talking about FreeNX on a web forum, or a
mail list…or i guess i might even be able to find a FAQ or other
documention which gives hints on how to fix your problem…

so, it would be my idea that you also look outside of this forum while
waiting for the one other person on earth with the same problem who
is also running openSUSE 11.1 to drop in…

–
goldie

#6

Hello Goldie,

Please do enlighten me - you’d be forgiven for thinking I haven’t already tried ‘Googling’ for this error message on numerous occasions.

In fact, the only suggested remedy was to ‘uninstall and reinstall FreeNX’ which simply won’t do. The fact there aren’t more suggestions is quite surprising given that this is a generic installation of FreeNX on a clean install of OS.

I’m also quite surprised you have not yet discovered NX, let alone FreeNX - as, in my opinion, an outstanding Open Source rival of Citrix may I suggest you take a look. I’m quite confident you will find its abilities somewhat useful sooner or later!

In the meanwhile, if you happen to find something on Google that I’ve missed, I’d be delighted to hear from you. rotfl!

Best Wishes,

Paul Smith
Managing Director
Anomex Limited

#7

> I’d be delighted to hear from you. rotfl!

laugh all you wish Paul…i was simply trying to be helpful in
responding directly to your invitation “Has anyone any more ideas?”…

in case you missed it, my idea was that while waiting for competent
technical help here (which i freely admitted i couldn’t give) you
might consider seeking assistance from a FreeNX user forum, somewhere…

if you think it better to sit here and laugh, then have at it…

i agree that perhaps i should have saved my energy and left your
request for “any more ideas?” alone…

i wonder if you also post to and then laughed at the lack of help from
the mail lists available here:
https://mail.kde.org/mailman/listinfo/freenx-knx/

or if your problem is covered in any way by Bug IDs: 016086, 015703,
015404…

or if you followed the hint at the source of FreeNX to check out Rick
Stout’s page (linked to under “Fedora” on
http://freenx.berlios.de/download.php) because “Even if your system is
not Fedora, you may find his page useful.” Was it?

or if you really got nothing worthwhile out of the thousands of hits
shown at
http://www.google.com/search?q=FreeNX+“NX+Agent+exited+with+exit+status+1”+suse

hmmmmmmm…i just looked again at your initial post…it kinda looks
like the nx client or server (i can’t tell which you have where, since
you didn’t mention that) has to have write access on /home/admin/.nx/,
/usr/bin/, and /var/lib/nxserver/db/running/ …i have not, and i’m
not going to read the “installation guide on the OpenSUSE website” but
i wonder if read/write capability to those directories is addressed in
the guide…or does the client/server run as root? (which sounds real
scary to me!–but, i know nothing)…

if it could write an actual log to
/var/lib/nxserver/db/running/sessionId{27DEA5D512371EF5E242ADFB96EDCA15}:
maybe then you could then LOOK AT it to see what went wrong causing
the “exit status 1” error…

good luck…hang out here all you wish…surely someone will happen
along and help you…eventually.

–
goldie
Note: Accuracy, completeness, legality, or usefulness of this posting
may be illusive.

#8

Hello Goldie,

Thanks for your reply. I have clearly and unintentionally offended you - perhaps an oversight on my part not having understood the American initialisation of ‘Rotfl’, having intended to use the ‘emoticon’ out of good humour.

I did however feel that your last post was inferring that I had simply come running to this forum seeking help without prior searching on Google etc. Anyway, enough animosity and back to the subject in hand:

I am already a member of the FreeNX mailing list and have posted my problem to the fellow subscribers and awaiting a reply. Sadly, despite the thousands of Google hits, and after hours of clicking through - I did not find much to be of use.

I will however look into some of the other resources that you mention.

Lastly, please do not interpret my posts in the worst possible light as, and I quote, ‘but, i know nothing’ is the very last thing I would imply - I am forever grateful for the help I receive from fellow forum users!

Many thanks again for your help.

Kindest Regards,

Paul Smith
Managing Director
Anomex Limited