Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29671 - [freenx] FreeNX seems to ignore node.conf

Attached to Project: Arch Linux
Opened by Votan (Votan) - Monday, 30 April 2012, 13:15 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 06 June 2012, 06:04 GMT
Task Type Support Request
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I had nxserver working for months. Today I updated my server and freenx replaced nxserver, as nxserver is nowhere to be found in the repos I suppose that was ok and proceeded.

pacman told me that the conf dir changed so I updated it to the new one (/etc/nxserver/node.conf) and tried to connect.

Now the client is getting an error:

NX> 203 NXSSH running with pid: 5024
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: xxx.xxx.xxx.xxx on port: xxxxx
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

which is strange, as the node.conf clearly states that only ssh auth is enabled. Here's the node.conf: http://codepad.org/99xWVnnr

Is there a problem with the new package?
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 06 June 2012, 06:04 GMT
Reason for closing:  Works for me
Comment by Andreas Radke (AndyRTR) - Monday, 30 April 2012, 13:51 GMT
You need change the key. Have you done that?

pacman should tell you this:

"A new key set is required."
"Please copy to your clients the new client key:"
Comment by Votan (Votan) - Tuesday, 01 May 2012, 19:16 GMT
I did import the key stated by pacman that needs replacement on my client via the gui and verified it if it is the same as on the server and I still get the exact same error message :/

I did nxserver --install several times, tried with --clean etc and did import the new client key to my client. Same error.
Comment by Andreas Radke (AndyRTR) - Sunday, 20 May 2012, 12:16 GMT
Have you solved this? Anything in the logs?
Comment by Andreas Radke (AndyRTR) - Wednesday, 06 June 2012, 06:04 GMT
All changes I do in node.conf are taken over here. Tried it will logging levels and keep logs.

Loading...