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// -p aa 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
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
