Hi.
I have updated system/server that worked for a long time. It was upgrade from 6.4 to latest.
After restart, system freezes after most/all of the daemons are booted.
From interactive mode I found out that services starting are:
... ... atd jexec atieventsd libvirtd certmonger libvirt-guests local nxsensor nxserver webmin
As soon as I allow webmin to pass, system freezes. BUT, if I stop after nxserver, and leave booting process at question weather to start webmin, and I login via SSH, I can start webmin.
Question is how I find out what comes after webmin service.
/var/log/messages is not written to, and I do not see anything in /var/log/boot.log
System can operate normally if I leave it like that, I can even log-in via NX.
On 01/27/2014 03:18 PM, Ljubomir Ljubojevic wrote:
Hi.
I have updated system/server that worked for a long time. It was upgrade from 6.4 to latest.
After restart, system freezes after most/all of the daemons are booted.
From interactive mode I found out that services starting are:
... ... atd jexec atieventsd libvirtd certmonger libvirt-guests local nxsensor nxserver webmin
As soon as I allow webmin to pass, system freezes. BUT, if I stop after nxserver, and leave booting process at question weather to start webmin, and I login via SSH, I can start webmin.
Question is how I find out what comes after webmin service.
/var/log/messages is not written to, and I do not see anything in /var/log/boot.log
System can operate normally if I leave it like that, I can even log-in via NX.
Freeze is manifested with non responsive direct console, nothing on the screen, but also with network dying out.
I disabled SELinux because restorecon was spewing file not found on some Windows files hosted there via Samba.
I also tried disabling kdump.
On 01/27/2014 03:22 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 03:18 PM, Ljubomir Ljubojevic wrote:
Hi.
I have updated system/server that worked for a long time. It was upgrade from 6.4 to latest.
After restart, system freezes after most/all of the daemons are booted.
From interactive mode I found out that services starting are:
... ... atd jexec atieventsd libvirtd certmonger libvirt-guests local nxsensor nxserver webmin
As soon as I allow webmin to pass, system freezes. BUT, if I stop after nxserver, and leave booting process at question weather to start webmin, and I login via SSH, I can start webmin.
Question is how I find out what comes after webmin service.
/var/log/messages is not written to, and I do not see anything in /var/log/boot.log
System can operate normally if I leave it like that, I can even log-in via NX.
Freeze is manifested with non responsive direct console, nothing on the screen, but also with network dying out.
I disabled SELinux because restorecon was spewing file not found on some Windows files hosted there via Samba.
I also tried disabling kdump.
Ok, so adding "3" to kernel line did boot system to multi-text mode. I will check drivers and nomodeset next
On Mon, Jan 27, 2014 at 9:18 AM, Ljubomir Ljubojevic centos@plnet.rswrote:
Hi.
I have updated system/server that worked for a long time. It was upgrade from 6.4 to latest.
After restart, system freezes after most/all of the daemons are booted.
From interactive mode I found out that services starting are:
... ... atd jexec atieventsd libvirtd certmonger libvirt-guests local nxsensor nxserver webmin
As soon as I allow webmin to pass, system freezes. BUT, if I stop after nxserver, and leave booting process at question weather to start webmin, and I login via SSH, I can start webmin.
Question is how I find out what comes after webmin service.
Does "ls /etc/rc5.d/S*" give you the order that services are started for level 5?
/var/log/messages is not written to, and I do not see anything in
/var/log/boot.log
System can operate normally if I leave it like that, I can even log-in via NX.
--
Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS, Mikrotik and CentOS/RHEL/Linux consultant _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 01/27/2014 03:53 PM, Phelps, Matt wrote:
ls /etc/rc5.d/S*
Yeah, thanks.
I managed to find out X server is a culprit (system is server with Virtual Windows accessed remotely but has X system in place).
Funny thing is that startx (from init 3) does not write to the X.org.log at all.
Well, off to digging :(
On 01/27/2014 04:01 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 03:53 PM, Phelps, Matt wrote:
ls /etc/rc5.d/S*
Yeah, thanks.
I managed to find out X server is a culprit (system is server with Virtual Windows accessed remotely but has X system in place).
Funny thing is that startx (from init 3) does not write to the X.org.log at all.
Well, off to digging :(
It seams as Proprietary ATI/AMD video driver issue with 6.4 and 6.5. Funny it is with [AMD/ATI] BeaverCreek [Radeon HD 6550D] integrated graphics.
I will experiment with drivers, maybe I just leave stock drivers from kernel.
I consider this Solved.
On 01/27/2014 04:16 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 04:01 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 03:53 PM, Phelps, Matt wrote:
ls /etc/rc5.d/S*
Yeah, thanks.
I managed to find out X server is a culprit (system is server with Virtual Windows accessed remotely but has X system in place).
Funny thing is that startx (from init 3) does not write to the X.org.log at all.
Well, off to digging :(
It seams as Proprietary ATI/AMD video driver issue with 6.4 and 6.5. Funny it is with [AMD/ATI] BeaverCreek [Radeon HD 6550D] integrated graphics.
I will experiment with drivers, maybe I just leave stock drivers from kernel.
search for libglamoregl on the elrepo list I havent had that issue but it sounds familiar
On 01/27/2014 05:46 PM, Nicolas Thierry-Mieg wrote:
On 01/27/2014 04:16 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 04:01 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 03:53 PM, Phelps, Matt wrote:
ls /etc/rc5.d/S*
Yeah, thanks.
I managed to find out X server is a culprit (system is server with Virtual Windows accessed remotely but has X system in place).
Funny thing is that startx (from init 3) does not write to the X.org.log at all.
Well, off to digging :(
It seams as Proprietary ATI/AMD video driver issue with 6.4 and 6.5. Funny it is with [AMD/ATI] BeaverCreek [Radeon HD 6550D] integrated graphics.
I will experiment with drivers, maybe I just leave stock drivers from kernel.
search for libglamoregl on the elrepo list I havent had that issue but it sounds familiar
found it, in short this could solve your problem: yum erase xorg-x11-glamor (will remove xorg-x11-drv-ati and the meta package xorg-x11-drivers, which you don't use since you use the proprietary ATI driver)
On 01/27/2014 05:50 PM, Nicolas Thierry-Mieg wrote:
On 01/27/2014 05:46 PM, Nicolas Thierry-Mieg wrote:
On 01/27/2014 04:16 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 04:01 PM, Ljubomir Ljubojevic wrote:
On 01/27/2014 03:53 PM, Phelps, Matt wrote:
ls /etc/rc5.d/S*
Yeah, thanks.
I managed to find out X server is a culprit (system is server with Virtual Windows accessed remotely but has X system in place).
Funny thing is that startx (from init 3) does not write to the X.org.log at all.
Well, off to digging :(
It seams as Proprietary ATI/AMD video driver issue with 6.4 and 6.5. Funny it is with [AMD/ATI] BeaverCreek [Radeon HD 6550D] integrated graphics.
I will experiment with drivers, maybe I just leave stock drivers from kernel.
search for libglamoregl on the elrepo list I havent had that issue but it sounds familiar
found it, in short this could solve your problem: yum erase xorg-x11-glamor (will remove xorg-x11-drv-ati and the meta package xorg-x11-drivers, which you don't use since you use the proprietary ATI driver)
Thanks. I saw that on one of the lists. But I might keep kernels driver, since machine is up and running, and it looks like it will work good enough without proprietary driver.
-
Ljubomir Ljubojevic -
Nicolas Thierry-Mieg -
Phelps, Matt