[FreeNX-kNX] Arch Linux - After reboot have to login 4 times to work ????? (every single time)
Jeremy Wilkins
wjeremy at shaw.ca
Thu Nov 26 21:42:07 UTC 2009
Oops need to correct Marcelo on paths though. Your path is /opt/NX/db
Jeremy Wilkins wrote:
>
> I agree with Marcelo. It sounds like it is a db file/port conflict. Try
> these and report back.
>
>
> Marcelo Boveto Shima wrote:
>>
>> Hi,
>>
>> I can see two possible causes:
>> 1 - /var/lib/nxserver/db/running/ should be empty after the reboot.
>> $nxserver --cleanup should clean the directory
>> 2 - Ports needed by the four session are been used. Set the
>> DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.
>>
>> Hope this helps.
>> Regards.
>>
>> Marcelo
>>
>> On Wed, Nov 25, 2009 at 4:53 PM, yossarianuk <morgancoxuk at gmail.com>
>> wrote:
>>>
>>> Hi.
>>>
>>> 100% sure it is not fsck'ing ...
>>>
>>> For a start I can always ssh , it also doesn't matter how long I leave
>>> it -
>>> I can leave it hours and the result will be the same - fail 4 times,
>>> then
>>> success...
>>>
>>> After setting SESSION_LOG_CLEAN=0 I have seen the following
>>>
>>> [root at winwinwinwin yossarian]# cat
>>> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
>>> $DISPLAY is not set or cannot connect to the X server.
>>>
>>> xrdb: No such file or directory xrdb: Can't open display ':1000'
>>> $DISPLAY is
>>> not set or cannot connect to the X server.
>>>
>>> After the 4th attempt it works fine ???
>>>
>>>
>>>
>>>
>>>
>>> ChrisB-6 wrote:
>>>>
>>>> yossarianuk <morgancoxuk at gmail.com> wrote on 23/11/2009 17:29:56:
>>>>
>>>>>
>>>>> Hi.
>>>>>
>>>>> This issue has been going on for at least 4-6 months now...
>>>>>
>>>>> I am running latest freenx on archlinux (686)
>>>>>
>>>>> It works absolutely fine, until I reboot.
>>>>>
>>>>> Then every single time I have to try to login (and fail) 3 times, then
>>>> on
>>>>> the 4th login to works, then anyone can login - freenx will then be
>>>>> 100%
>>>>> fine until the next reboot.
>>>>
>>>>
>>>> Are you sure you aren't waiting for fsck etc to finish ??
>>>>
>>>>>
>>>>> Can anyone think of ANYTHING I can do to stop this happening ??? It
>>>>> is
>>>>> really annoying,
>>>>>
>>>>> I did raise a post about this several months ago, I followed advice at
>>>> the
>>>>> end, it still happens.
>>>>>
>>>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>>>
>>>>> Here is an example fail.
>>>>>
>>>>> ====================================
>>>>> Display Type Session ID Options
>>>>> Depth
>>>>> Screen Status Session Name
>>>>> ------- ---------------- -------------------------------- --------
>>>>> -----
>>>>> -------------- ----------- ------------------------------
>>>>>
>>>>>
>>>>> NX> 148 Server capacity: not reached for user: yossarian
>>>>> NX> 105 startsession --link="adsl" --backingstore="1"
>>>>> --encryption="1"
>>>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>>>> --screeninfo="1280x976x24+render"
>>>>>
>>>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>>>> NX> 705 Session display: 1000
>>>>> NX> 703 Session type: unix-kde
>>>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>>>> NX> 702 Proxy IP: 127.0.0.1
>>>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>>>> NX> 704 Session cache: unix-kde
>>>>> NX> 707 SSL tunneling: 1
>>>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>>>> $AGENT_STARTUP_TIMEOUT
>>>>
>>>> no agent
>>>>
>>>>
>>>>
>>>>> 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/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>>>
>>>> Did you do this ?? What did it say ??
>>>>
>>>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode
>>>>> --agent
>>>> to
>>>>> test the basic functionality. Session log follows:
>>>>> Can't open
>>>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>>>> such
>>>>> file or directory.
>>>>> mv: cannot stat
>>>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}':
>>>>> No
>>>>> such file or directory
>>>>> NX> 1006 Session status: closed
>>>>> NX> 280 Exiting on signal: 15
>>>>>
>>>>> ====================================
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>>>> time%29-tp26482511p26482511.html
>>>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>>>
>>>>> ________________________________________________________________
>>>>> Were you helped on this list with your FreeNX problem?
>>>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>>>
>>>>>
>>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>>>
>>>>> Don't forget to check the NX Knowledge Base:
>>>>> http://www.nomachine.com/kb/
>>>>>
>>>>> ________________________________________________________________
>>>>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>>>> ________________________________________________________________
>>>>
>>>> ________________________________________________________________
>>>> Were you helped on this list with your FreeNX problem?
>>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>>
>>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>>
>>>> Don't forget to check the NX Knowledge Base:
>>>> http://www.nomachine.com/kb/
>>>>
>>>> ________________________________________________________________
>>>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>>> ________________________________________________________________
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>>
>
>
--
View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26535250.html
Sent from the freenx-knx mailing list archive at Nabble.com.
More information about the FreeNX-kNX
mailing list