2015-10-5 system crash record
An error occurred when switching to the 5 system level at the 3 system level
[[Email protected] linux]# Init 5
Calling the system Activity Data Collector (SADC) ...
And when switching to the 3 system level, there was the same hint.
Calling the system Activity Data Collector (SADC) ...
Take the current system snapshot immediately and restore the last system snapshot for system-level switching operations
The previous snapshot version of the system does not have any problems, again when switching to the current version of the system, the error is still
I've sorted out the system changes I made between the two versions of the system.
I shut it down. SELinux Firewall
I changed the system font by en -US was replaced by ZH-CN
I put the boot system to the auto-start level 5 was replaced by 3
I shut down most of the boot services
I changed the CRT Port of the remote service, by the A was replaced by 52113
I changed the network listening address by 0.0.0.0 instead of itself IP
In the logical troubleshooting, I ruled out the possibility of 2.5.6, locking the cause at 1.4, but not excluding the possibility of 3.
In order, I first re-open the SELinux firewall, found their own October 1 changes to do the backup, backup is really important, but also a lot of convenience, direct CP back OK
[Email protected] selinux]# Getenforce
Disabled
[Email protected] selinux]# ls/etc/selinux/
Config restorecond.conf semanage.conf
config.cp.20151001 restorecond_user.conf targeted
Turn the firewall back on,
[[email protected] selinux]# CP config.cp.20151001 Config
Cp:overwrite ' config '? Y
Check it out.
[email protected] selinux]# Cat Config | grep selinux=
Selinux=enforcing
This firewall is a sore egg and must be restarted.
Start to see this, SELinux startup also read the bar ...
650) this.width=650; "title=" {3be02bb1-fd40-4729-b1ad-fd67d888ec7c}.jpg "alt=" Wkiom1yuguyzbxy4aajuny4wlic418.jpg " src= "Http://s3.51cto.com/wyfs02/M01/74/1D/wKiom1YUgUyzbXy4AAJunY4Wlic418.jpg"/>
SELinux startup is done, but there is no hint of action still exists
Then change the boot level
[Email protected] linux]# Cat/etc/inittab
# Inittab is a used by upstart for the default runlevel.
#
# ADDING Other CONFIGURATION here would have NO EFFECT on YOUR SYSTEM.
#
# System initialization is started by/etc/init/rcs.conf
#
# individual runlevels is started by/etc/init/rc.conf
#
# Ctrl-alt-delete is handled by/etc/init/control-alt-delete.conf
#
# Terminal Gettys is handled by/etc/init/tty.conf and/etc/init/serial.conf,
# with configuration In/etc/sysconfig/init.
#
# For information on what to write upstart event handlers, or how
# Upstart works, see Init (5), init (8), and Initctl (8).
#
# Default RunLevel. The runlevels used is:
# 0-halt (do not set Initdefault to this)
# 1-single User mode
# 2-multiuser, without NFS (the same as 3, if you don't have networking)
# 3-full Multiuser mode
# 4-unused
# 5-x11
# 6-reboot (do not set Initdefault to this)
#
Id:3:initdefault:
Viewing the startup file you can see that the current start level is level 3, direct boot come in without any problems, I now change back to the 5 level of the system's default boot level, here in order to deal with the problem as a main, direct VI modification
Revise it and check it again.
[Email protected] linux]# cat/etc/inittab |grep ID:
Id:5:initdefault:
Continue to restart
And then I found out that the system couldn't get in directly.
Stuck in the Reading interface
650) this.width=650; "title=" {27b89829-a0b1-4273-baff-7b2f857e4da8}.jpg "alt=" Wkiom1yugykrr9o2aaavzvuuyw0612.jpg " src= "Http://s3.51cto.com/wyfs02/M02/74/1D/wKiom1YUgYKRR9o2AAAVzvuuyw0612.jpg"/>
Switch to CRT observation, the unexpected is the CRT actually logged in, the system started to complete, just can't load graphical interface, that basically can be determined that there is a 5 system level of a startup service does not open
In order to verify their conjecture, the direct init 3 in the CRT switches the level
Sure enough, Level 3, just let me enter my account code to get me logged in.
650) this.width=650; "title=" {28f8cde6-15ad-4723-8cd5-b13524702842}.jpg "alt=" Wkiol1yugclivsjeaabejilzjv0754.jpg " src= "Http://s3.51cto.com/wyfs02/M00/74/1A/wKioL1YUgcLivsJEAABEJilZjv0754.jpg"/>
Now that the specific reason is determined, it is not a waste of time, direct pointing to the boot start service
650) this.width=650; "title=" {2b689ec5-2260-4be0-abad-52ce49570124}.jpg "alt=" Wkiol1yughmq3olraacq_3rlekm444.jpg " src= "Http://s3.51cto.com/wyfs02/M01/74/1A/wKioL1YUghmQ3OlrAAcQ_3rLEKM444.jpg"/>
What I want to do now is to exclude every startup service, of course, some with the naked eye can be ruled out without the need for additional waste of effort, such as network,ip6,vmtools, in order to reduce the workload, I found the last snapshot version of the system's boot service state, can be seen clearly, I turned off a lot of
650) this.width=650; "title=" {5c70a37f-7b59-418d-a7dd-04a9bc3fdjpgb2a}.jpg "alt=" Wkiol1yugojstkzhaazfzddt4ua530.jpg "src=" Http://s3.51cto.com/wyfs02/M02/74/1A/wKioL1YUgojStkzHAAZfZdDt4UA530.jpg "/>
Finally, the culprit was caught and messagebus this service
The event monitoring service, which is responsible for passing messages between the various system processes. That's how Google defines it.
But in my case, he also played the role of Init 5, check the time also found that I have Haldaemon service also turned off, usually use CRT these errors are really difficult to find
Turn on boot from both services
[Email protected] linux]# chkconfig |egrep ' Messagebus|haldaemon ' | awk ' {print ' chkconfig ' on '} ' | Bash
Check it out.
[Email protected] linux]# Chkconfig--list | Egrep ' Messagebus|haldaemon '
Haldaemon 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Then init 51, login successful
This article from "My Blog" blog, declined reprint!
2015-10-5 system crash record