[FreeNX-kNX] freenx was working, now authentication error

[Ben Voigt]

Thanks for the help.

Turns out it wasn't the crash at all, but:

I am using CVS version of freeNX, so I did 'emerge -C nxserver-freenx' some
time ago.  Everything still worked.
But now I did 'emerge depclean' and that removed net-util/gnu-netcat and
dev-tcltk/expect.

I did 'emerge -p nxserver-freenx' to find that out, and emerged all freenx
dependencies directly to the world file.  Now everything is OK.
I think injecting freenx would have been better, but emerge says inject is
deprecated...

****************************

Ben Voigt
University of Pennsylvania
Electrical Engineering PhD Candidate

voigt at seas.upenn.edu <mailto:voigt at seas.upenn.edu>
BVoigt at kas.com <mailto:BVoigt at kas.com>

Support a Constitutional Amendment to protect the Pledge of Allegiance and
National Motto.
Click here for more information. <http://www.wepledge.com/>

****************************


> -----Original Message-----
> From: Jon Severinsson [mailto:jon at severinsson.net]
> Sent: Monday, March 28, 2005 8:44 AM
> To: 'FreeNX-kNX'
> Subject: Re: [FreeNX-kNX] freenx was working, now authentication error
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi
>
> As you speek of emerge, I suppose you run Gentoo and have installed
> freeNX 0.2.8 through portage. Is this assumption correct?
>
> The easiest way to track down errors is to enable logging (in
> 0.2.x set
> NX_LOGGING=1 in the nxserver script, in 0.3.x set NX_LOGGING=1 in the
> node.conf file). After a single login attempt you will have a
> /tmp/nxserver.log (0.2.x) or /var/log/nxserver.log (0.3.x).
> First try to
> read it and se if you make anything out of it, if you cant'
> attack it to
> the list.
>
> I think the error most likely is either a misconfiguration in
> ssh during
> the update (check that both PasswordAuthentication and
> PubkeyAuthentication is enabled in /etc/ssh/sshd_config) or
> that some nx
> component went missing in the crach.
> The later can be fixed (guaranteed, but will take some time)
> by removing
> all nx components (emerge -avC nxcomp nxproxy nx-x11 nxserver-freenx
> nxssh nxclient && rm -r /usr/NX) followed by 'emerge -av
> nxserver-freenx'. I would recomend trying to use the log to
> figgure out
> what component/file has the error instead of reinstalling it all, but
> mainly becouse it'll take a few hours to recompile it all...
>
> Hope this help
>
> Regards
> Jonno
>
> Ben Voigt wrote:
> | I'm running CoLinux, and it caused a Windows STOP error, so my
> | reiserfs filesystem was unmounted uncleanly.  When I rebooted, dmesg
> | said "finishing unlinking" some 15 files, given numericly
> (the inodes
> | I would guess).
> |
> | Now I can still log into ssh, but the NoMachine NX client
> only gets as
> | far as authenticating and then says authentication failed.  I guess
> | some important freenx file got unlinked by the filesystem crash.  I
> | tried nxserver --stop and nxserver --start in order to recopy the
> | public keys, but that didn't help.
> |
> | I had also been upgrading some software with emerge -uavD world,
> | perhaps something there affected freenx.
> |
> | Any advice on how to track down the cause of failure?
> | _______________________________________________
> | FreeNX-kNX mailing list
> | FreeNX-kNX at kde.org
> | https://mail.kde.org/mailman/listinfo/freenx-knx
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFCSAocOOpxqcksWu4RAmtmAJ40oMhHw072s18OBgdW6iiN944jEwCgkVwr
> SwaC9MLugAOlsOVqXL7VB/E=
> =Vo2W
> -----END PGP SIGNATURE-----
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 3/27/2005
>