[FreeNX-kNX] Parse error in remote options string

[John Nicholls]

I had a similar problem this morning and it was driving me crazy, the
server stopped working with the same error (I think it's the smallest NX
server in the world at the moment and is running on an Arm prototype
board 12cm x 9 cm x 1cm)

I have been logging into the server and then running the Knx client
(which is still under development) from there to log into the NoMachine
server. To cut a long story short, when I fired up the server this
morning I received the same Parse error mentioned on this thread.

I decided to have a closer look at the server and I was surprised to see
a nxagent, and a nxproxy process running as user john. I killed these
processes and then deleted everything under the /var/lib/nxserver
subdirectories and successfully logged in as john

I have tried duplicating the problem, but so far I have still been able
to log back in OK, but have noticed that the Knx client seems to be
leaving two nxproxy processes running. These don't seem to cause the
problem, the nxagent process running may be the problem.

I hope this may be helpful to some of the "Gurus" on the list

John





On Sat, 2004-12-11 at 23:00, Gian Filippo Pinzari wrote:
> Rob Thomas wrote:
> > I've fixed my "Parse error in remote options string" problem !!! The
> > NX client session name that I got the other office to setup contained
> > a space, mine didn't. The session name is actually passed as a
> > parameter to the server and therefore it must be seeing the bit after
> > the space as another parameter. I don't know exactly how its passed
> > but maybe it would be better if the client surrounded it with quotes.
> 
> I think that this is a server side issue. The client is already
> surrounding parameters with quotes.
> 
> /Gian Filippo.
> 
> 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx