David C. Moody
2013-05-02 21:30:51 UTC
Hello everyone,
I need some help. I was doing my standard update today to keep the system up to date and it blew up in my face.
Now after finally working all day and getting the users able to log back in. They can log in, and run any apps that run via ltsp-local-apps, however any apps that run on the base system cause the user to get kicked out back to the login screen.
Pertinent system information:
[***@shopltsp ~]# rpm -qa|grep ltsp
ltsp-release-5-9.el6.noarch
ltsp-server-5.4.5-20.el6.i686
ltspfs-1.1-7.el6.i686
[***@shopltsp ~]# cat /etc/*release*
CentOS release 6.4 (Final)
LSB_VERSION=base-4.0-ia32:base-4.0-noarch:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
cat: /etc/lsb-release.d: Is a directory
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA
This is what I'm seeing in messages log:
[***@shopltsp log]# tail messages
May 2 17:36:17 shopltsp gnome-keyring-daemon[3579]: dbus failure unregistering from session: Connection is closed
May 2 17:36:18 shopltsp xinetd[1474]: START: ldminfod pid=3673 from=::ffff:192.168.10.15
May 2 17:36:18 shopltsp xinetd[1474]: EXIT: ldminfod status=0 pid=3673 duration=0(sec)
May 2 17:36:41 shopltsp spice-vdagent[3861]: Missing virtio device '/dev/virtio-ports/com.redhat.spice.0': No such file or directory
May 2 17:37:00 shopltsp gnome-keyring-daemon[3863]: dbus failure unregistering from session: Connection is closed
May 2 17:37:00 shopltsp gnome-keyring-daemon[3863]: dbus failure unregistering from session: Connection is closed
May 2 17:37:01 shopltsp xinetd[1474]: START: ldminfod pid=3963 from=::ffff:192.168.10.15
May 2 17:37:01 shopltsp xinetd[1474]: EXIT: ldminfod status=0 pid=3963 duration=0(sec)
May 2 17:37:57 shopltsp spice-vdagent[4151]: Missing virtio device '/dev/virtio-ports/com.redhat.spice.0': No such file or directory
May 2 17:40:14 shopltsp avahi-daemon[1195]: Invalid query packet.
I've done some googling, but I've been unable to turn up anything that corrects the problem as of yet.
Thanks for any help!
-David
I need some help. I was doing my standard update today to keep the system up to date and it blew up in my face.
Now after finally working all day and getting the users able to log back in. They can log in, and run any apps that run via ltsp-local-apps, however any apps that run on the base system cause the user to get kicked out back to the login screen.
Pertinent system information:
[***@shopltsp ~]# rpm -qa|grep ltsp
ltsp-release-5-9.el6.noarch
ltsp-server-5.4.5-20.el6.i686
ltspfs-1.1-7.el6.i686
[***@shopltsp ~]# cat /etc/*release*
CentOS release 6.4 (Final)
LSB_VERSION=base-4.0-ia32:base-4.0-noarch:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch
cat: /etc/lsb-release.d: Is a directory
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA
This is what I'm seeing in messages log:
[***@shopltsp log]# tail messages
May 2 17:36:17 shopltsp gnome-keyring-daemon[3579]: dbus failure unregistering from session: Connection is closed
May 2 17:36:18 shopltsp xinetd[1474]: START: ldminfod pid=3673 from=::ffff:192.168.10.15
May 2 17:36:18 shopltsp xinetd[1474]: EXIT: ldminfod status=0 pid=3673 duration=0(sec)
May 2 17:36:41 shopltsp spice-vdagent[3861]: Missing virtio device '/dev/virtio-ports/com.redhat.spice.0': No such file or directory
May 2 17:37:00 shopltsp gnome-keyring-daemon[3863]: dbus failure unregistering from session: Connection is closed
May 2 17:37:00 shopltsp gnome-keyring-daemon[3863]: dbus failure unregistering from session: Connection is closed
May 2 17:37:01 shopltsp xinetd[1474]: START: ldminfod pid=3963 from=::ffff:192.168.10.15
May 2 17:37:01 shopltsp xinetd[1474]: EXIT: ldminfod status=0 pid=3963 duration=0(sec)
May 2 17:37:57 shopltsp spice-vdagent[4151]: Missing virtio device '/dev/virtio-ports/com.redhat.spice.0': No such file or directory
May 2 17:40:14 shopltsp avahi-daemon[1195]: Invalid query packet.
I've done some googling, but I've been unable to turn up anything that corrects the problem as of yet.
Thanks for any help!
-David