Hi, I have a remote frontend (it's kept in the room which I don't have access) which is installed with CentOS 4 and Rocks . So, to use the desktop(Gnome) of the frontend I use the freenx + nomachine following the guide in http://www.centos.org/modules/newbb/viewtopic.php?forum=20&topic_id=1640&viewmode=threaded. It worked. Then, I intended to add user, but I couldn't create the home folder in /home/ for the new user. After browsing, I found that somebody mentioned it's because of the automounter/autofs. So, I played around, enabled and disabled the autofs, and yes, I could create the home folder for the new user. The problem is that, when I tried to log-in to the front end using nomachine (using root) again, I could only get as far as the splash screen of the CentOS. I tried to connect using the putty (terminal), and I could interact (issuing command to the terminal), but I couldn't use the Gnome anymore. So, why in the nomachine I could not pass the splash screen anymore ? Any solution ? Thanks. Send instant messages to your online friends http://uk.messenger.yahoo.com
Eon Strife wrote:> > Hi, > I have a remote frontend (it's kept in the room which I don't have access) which is installed with CentOS 4 and Rocks . So, to use the desktop(Gnome) of the frontend I use the freenx + nomachine following the guide in http://www.centos.org/modules/newbb/viewtopic.php?forum=20&topic_id=1640&viewmode=threaded. It worked. Then, I intended to add user, but I couldn't create the home folder in /home/ for the new user. After browsing, I found that somebody mentioned it's because of the automounter/autofs. So, I played around, enabled and disabled the autofs, and yes, I could create the home folder for the new user. The problem is that, when I tried to log-in to the front end using nomachine (using root) again, I could only get as far as the splash screen of the CentOS. I tried to connect using the putty (terminal), and I could interact (issuing command to the terminal), but I couldn't use the Gnome anymore. So, why in the nomachine I could not pass the splash > screen anymore ? Any solution ? Thanks.Although I can not answer your question directly, did you see anything logged on the system that you are connecting to via the nomachine client? Also, the Nomachine client provides some logging of its own as well. You may want to check for any error or permissions related information in the client's directory. That may point you in the right direction. Sincerely, Alex White -- ethericalzen at gmail.com Life is a prison, death is a release
Hi, Thanks for the reply. I already checked the the current user logged in the freenx by using "nxserver --list", it's only the root (the one I currently using). And yeah, I'm stuck in this screen : http://img.photobucket.com/albums/v708/EonStrife/stuck.jpg I wonder, just say if we don't use the remote desktop, but we access or use the computer directly/physically as usual, what do we do if we're stuck on that screen ? About the log of the nomachine, I think the most interesting part is the bottomost part. Note, there are many occurences of "NXFileMonitor::readData", and some 'stop' and 'destructor' words in the end, even though the nomachine is still running. ==[Wed 21. May 09:48:18 2008]: Setting environment variable 'NX_HANDLEPROXY' to '28077c' [Wed 21. May 09:48:18 2008]: NXService::getWin32DisplayHandler: NX_HANDLEPROXY=28077c [Wed 21. May 09:48:18 2008]: NXService::getWin32DisplayHandler: end [Wed 21. May 09:48:18 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:19 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:20 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: NXFileMonitor::readData [Wed 21. May 09:48:21 2008]: LoginDialog: slotAgentTimer [Wed 21. May 09:48:21 2008]: LoginDialog: Agent found closing windows... [Wed 21. May 09:48:21 2008]: LoginDialog: Slotsingleapplication: setting automatic reconnect to true. [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: LoginDialog: closeEvent received! [Wed 21. May 09:48:21 2008]: LoginDialog::destructor called begin [Wed 21. May 09:48:21 2008]: LoginDialog: stopAllTimers [Wed 21. May 09:48:21 2008]: LoginDialog: stopProgressTimer [Wed 21. May 09:48:21 2008]: Utility::getPreferencesFile: 'nxclient' -> 'C:\Users\Eon Strife/.nx/config/nxclient.cfg' [Wed 21. May 09:48:21 2008]: Settings::flush [Wed 21. May 09:48:21 2008]: Called destructor for protocol class [Wed 21. May 09:48:21 2008]: LoginDialog::destructor called end == Thanks == Eon Strife wrote:> > Hi, > I have a remote frontend (it's kept in the room which I don't have access) which is installed with CentOS 4 and Rocks . So, to use the desktop(Gnome) of the frontend I use the freenx + nomachine following the guide in http://www.centos.org/modules/newbb/viewtopic.php?forum=20&topic_id=1640&viewmode=threaded. It worked. Then, I intended to add user, but I couldn't create the home folder in /home/ for the new user. After browsing, I found that somebody mentioned it's because of the automounter/autofs. So, I played around, enabled and disabled the autofs, and yes, I could create the home folder for the new user. The problem is that, when I tried to log-in to the front end using nomachine (using root) again, I could only get as far as the splash screen of the CentOS. I tried to connect using the putty (terminal), and I could interact (issuing command to the terminal), but I couldn't use the Gnome anymore. So, why in the nomachine I could not pass the splash > screen anymore ? Any solution ? Thanks.Although I can not answer your question directly, did you see anything logged on the system that you are connecting to via the nomachine client? Also, the Nomachine client provides some logging of its own as well. You may want to check for any error or permissions related information in the client's directory. That may point you in the right direction. Sincerely, Alex White -- ethericalzen at gmail.com Life is a prison, death is a release== Send instant messages to your online friends http://uk.messenger.yahoo.com
Hi,
Thanks, it's Gnome, and I'm stuck when I login as root.
By using Putty, I managed to create a new user, and then I tried to login to
desktop(using nomachine) as that user, and yes, it works. The problem now is
that I stuck when I login as the root.
Then, I compared the runlog (the one I wrote in that previous email), between
the root's and the new user's and, they're the same.
Then, I compared the sshlog, and I found discrepancies. In the sshlog of the
root, there are some additional lines saying unable to open a file and unable to
start the sesion:
==NX> 285 Identified internal connection
NX> 285 Using default mode encrypted
NX> 285 Identified options:
nx/nx,options=/cygdrive/C/Users/EONSTR~1/NX73F8~1/S-8728~1.ORG/options:1000
NX> 280 Proxy opened with local: 7 remote: 8
NX> 285 Switching descriptors: 4 and: 5 to: 7
NX> 287 Redirected I/O to channel descriptors
NX> 280 Proxy in: 4 out: 5 transport in: 8 out: 8
NX> 596 Session startup failed.
<- The additional line in the sshlog of the root
NX> 1004 Error: NX Agent exited with exit status 1.
Can't open
/var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}: No
such file or directory.
mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}':
No such file or directory
NX> 1006 Session status: closed
Exited with status 0. User pressed Ok.
==
I checked the permission of that var/lib/nxserver/ (and folders (including
/db/running/ ) and files inside it), the permission is 0700 (read,write,execute
enabled for the owner), with the group is root and owner is the nx. And yes,
also using the root I can view the content of the var/lib/nxserver. If I login
using that new user, I can't view the content.
Oh,yeah, pressing start and leaving for few hours don't solve the problem.
Checking the .bash_history file, these are the commands I issued around the time
when I messed up :
==useradd aaa
useradd --help
useradd abc
passwd aaa
useradd --help
useradd -d /home/aaaa/ -p aaaaaa aaa
which useradd
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
userdel --help
userdel aaa
passwd aaa
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
cd /home/
ls
rmdir --help
cd aaa
ls
del --help
delfile --help
cd \.
cd /.
cd /home/
rm -r /home/aaa/
ls
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs reload
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
ls
/etc/rc.d/init.d/autofs stop
exit
ypcat
ypcat group
group
grouplist
groupls
groups
users
uname
uname -s -n -m -r
id
whoami
w root
w
ps
ps
ps -f
ps -a
==
Thanks.
==
I am not in front of a machine with the nxclient on it, I will be in the
morning and can see what some of the logs look like there; however, the
ling concerning automatic reconnect to true makes me think the device is
attempting to start up a session that doesn't exist. I can't prove that,
but I will have more information tomorrow.
Concerning your screen shot, I've only ever been stuck at that screen
once and simply hitting enter at the keyboard made it vanish. The splash
screen should time out anyhow once the start up stuff times out if
gnome/kde/xfce's initialization routine takes too long.
What desktop (window manager?) are you using? Is it Gnome, KDE or
something else? I've not seen selinux create an issue, but for posterity
is it running? Does it log anything on the system you're attempting to
connect with? Oh, what about permissions for the user? Does the user
have the ability to write to his/her home directory properly? You could
be getting stuck on the splash screen because the user can't write any
data for the initialization.
Sincerely,
Alex White
==
Send instant messages to your online friends http://uk.messenger.yahoo.com
Hi,
Thanks, I check those folders, and they are already empty.
Now, I tried to remove the freenx by using yum, and then I removed the files it
left behind manually in:
/usr/bin/nxserver
/usr/lib/nx
/var/lib/nxserver
/etc/nxserver
along with the nx user and group and reinstall. The problem worsen, no matter
what user I tried, I always got Session Startup Failed:
==NX> 700 Session id: cluster.hpc.org-1014-084919CE7F9816540BDEDD5A7928084E
NX> 705 Session display: 1014
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: ee398e9cedaf3adbba4dc966d4433dee
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: ee398e9cedaf3adbba4dc966d4433dee
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 1077: 8588 Terminated sleep
$AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
NX> 1006 Session status: closed
Can't open
/var/lib/nxserver/db/running/sessionId{084919CE7F9816540BDEDD5A7928084E}: No
such file or directory.
mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{084919CE7F9816540BDEDD5A7928084E}':
No such file or directory
NX> 280 Exiting on signal: 15
==
I tried alternative solution by using VNC. In order to have access to desktop, I
modifed the content of the Xstartup file (for the root in /root/.vnc/xstartup
and
for the regular user in /home/EonStrife/.vnc/xstartup) to be :
==#!/bin/sh
# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#startx &
exec gnome-session &
#twm &
==
The funny thing is that for regular user I can access the desktop, but for the
root I'm only treated with the terminal. (BTW, the client I used are
tightVNC and RealVNC)
Thanks.
===Previous Message==
Eon Strife wrote:> Hi,
> Thanks, it's Gnome, and I'm stuck when I login as root.
> By using Putty, I managed to create a new user, and then I tried to login
to desktop(using nomachine) as that user, and yes, it works. The problem now is
that I stuck when I login as the root.
>
> NX> 596 Session startup failed.
<- The additional line in the sshlog of the root
> NX> 1004 Error: NX Agent exited with exit status 1.
> Can't open
/var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}: No
such file or directory.
> mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}':
No such file or directory
> NX> 1006 Session status: closed
> Exited with status 0. User pressed Ok.
As a regular user you shouldn't be able to look into that directory,
so that's normal. Only root and nx can do that.
Interesting (at least to me) is that you get an error concerning a
session that I do not believe it should be looking for. It's like
it's attempting to reattach to a session that doesn't exist and then
it fails. I could be incorrect, but at this point it's simply a data
point.
On the client machine (assuming it is linux), have you removed all
session data from the user's home directory? By default this is
~/.nx/cache-unix-windowmanagername (for you that is likely gnome)
and ~/.nx/letter-hostname-screen-somerandomhashIthink/
Don't remove the config directory or else you'll have to set up the
nx information again. See if that doesn't fix the issue. It may not,
and I'm sorry if it doesn't, but I am not entirely sure about this
particular issue.
If the client machine is a windows machine there is a .nx directory,
but I am not sure where it's kept. C:\documents and
settings\user\.nx maybe. That is where it resides on my windows
install at work on XP. I may or may not have changed the directory
so you might have to look around a bit.
HTH
Alex White
--
ethericalzen at gmail.com
Life is a prison, death is a release
Send instant messages to your online friends http://uk.messenger.yahoo.com