On Tuesday, December 18, 2012 06:02:09 PM Russell Clay1 wrote:
Hello,
Hi Russell
My understanding is that you no longer have the issue.
Yes, it is so
The changes you made to the grub.conf should not have impacted shutdown / startup times.
I am wondering if one of the services, such as httpd, had an active connection and therefore refused to shutdown ?
I'm sure that is not been an active connection
I would put the grub changes back, and then try shutting down and re-booting to see if you can re-create the problem.
I have only deleted the string rhgb and quiet; Sincerely do not think they influence
If you are unable to re-create the problem so well and good. Otherwise open another session and check the services that are running - This should help identify the service that is not closing / starting. Check all log files under /var.
At right time keep an eye tracking Thanks in advance
Regards
Cheers
Russell
On Tuesday 18 December 2012 08:23:32 Paolo De Michele wrote:
On 12/17/2012 11:53 PM, Russell Clay1 wrote:
Hi,
Good morning Russell,
To change runlevel, use the following command as root:
telinit 1
In console I've configured telinit1 and telinit 1 1>stdout.txt 2>stderr.txt but I have not found anything in these files In /etc/grub/ I have deleted the rhnb and quiet string and the machine startup is correct I tried to reboot or power off/on the machine and now it starts correctly
I checked /var/log/messages and dmesg but I have not found anything serious
Why? How can I resolve this issue? I don't understand why it behaves so Thanks in advance
Cheers
Do this twice, once capturing the output and the other looking at output on screen.
Regards
Russell
On Monday 17 December 2012 22:07:47 you wrote:
On 12/17/2012 10:30 PM, Russell Clay1 wrote:
Hi
Hi Russel
My understanding is that your problem only occurs on a reboot / shutdown.
What I would do is this:
- Log on as root, and identify which services are running:
a) service --status-all
a) http://nopaste.info/d7e4b36500.html
b) chkconfig
b) http://nopaste.info/4c500c96ab.html
c) runlevel
c) N 3
- Then I would change the runlevel to 1, capturing the output
telinit 1 1>stdout.txt 2>stderr.txt
how to change the runlevel?
I would also recreate the situation and identify which script hangs / takes a long time to shut down.
Thanks for your help Cheers
Regards
Russell
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Paolo De Michele