NoMachine NX server

[Pinnerite]

I am struggling with NX Server. If I start it and then try to check the
status, It goes like this:

[root@desktop ~]# /usr/NX/bin/nxserver --start
NX> 500 Service already running.
NX> 999 Bye.

[root@desktop ~]# /usr/NX/bin/nxserver --status
NX> 900 Connecting to server ...
NX> 204 Authentication to NX server failed.
NX> 110 NX Server is stopped.
NX> 999 Bye.

I cannot fnd anything on the web that seems to address this situation.







--
________________________________________________
PCLinuxOS release 2011 (PCLinuxOS) for x86_64
Kernel 2.6.38.8-pclos3
KDE version 4.6.5
Running on an AMD 4-core processor

[bra...@gmail.com]

i've got the same issue, and didn't find explanation on the web , nor clear solution.
you've fixed this in the mean time ?

[J G Miller]

On Monday, June 11th, 2012, at 07:04:02h -0700, Braniti wrote:

> i've got the same issue, and didn't find explanation on the web , nor clear solution.
> you've fixed this in the mean time ?
>
>
> On Wednesday, February 22, 2012 1:23:26 PM UTC+1, Pinnerite wrote:
>> I am struggling with NX Server. If I start it and then try to check the
>> status, It goes like this:
>>
>> [root@desktop ~]# /usr/NX/bin/nxserver --start
>> NX> 500 Service already running.
>> NX> 999 Bye.

Always check to see if a server is running with

ps -efw | egrep "server_executable_name"

You cannot rely on the start script truthfully indicating
that the daemon is actually running because some of them
just look to see if there is a lock file or pid file.

And the lock file or pid file may be lying around from
the previous daemon which did startup but crashed.

I seem to remember a similar problem some time ago (not necessarily
with NX) with a daemon service somebody else reported.

It could be that the nxserver is not starting because the port it
needs to bind to is in use or unavailable.