Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Linux \ CentOS card fails to start at boot progress bar certmonger solve     - Python function arguments * args and ** kwargs usage (Programming)

- Python programmers most often committed ten errors (Programming)

- Five programming fallacy (Programming)

- Ubuntu 15.10 15.04 14.10 14.04 Install Ubuntu Tweak (Linux)

- Standard and IO redirection (Linux)

- Disk Management LVM (Linux)

- C # Future: Method Contract (Programming)

- MongoDB relations, references, index query coverage (Database)

- Use GLOBK batch command network adjustment (Linux)

- DataGuard a hardware issue warnings found (Database)

- CentOS 6.6 shortcut command execution (Linux)

- Normal start Lazarus 1.0.8 under Ubuntu (Linux)

- How to monitor network usage by nload in Linux (Linux)

- Ubuntu: To install chat client Chatty 0.6.1 (Linux)

- Linux variable learning experience (Linux)

- Oracle Linux 6.4 (BOND) dual NIC teaming combat - Annotated (Linux)

- Hadoop 2.2.0 installation development environment (standalone pseudo-distributed mode) (Server)

- CentOS installation pycurl (Linux)

- OpenSUSE / Linux network configuration (Linux)

- How to build Memcached Docker container (Server)

 
         
  CentOS card fails to start at boot progress bar certmonger solve
     
  Add Date : 2017-08-31      
         
         
         
  Newly installed CentOS6.4, first boot progress bar will be stuck in there, I thought it was a slow response to the need to wait for some time, about 5 minutes or not, is estimated to be a problem.

After rebooting press Esc or F5 key, you can view the system boot process, the card where I was OK after the start certmonger stuck:

Causes: X11 graphical interface service caused by lead can not boot into the graphical interface.
Solution:
Modify the configuration file / etc / X11 /

By Ctrl + Alt + F2 to enter the CLI interface, log in as root, execute the following command
mv /etc/X11/xorg.conf /etc/X11/old_xorg.conf
If you can not enter the command line interface, when can boot into the single mode, and then modify it.
Modify the startup level (I used this approach, because the graphical interface for me useless, but the system installation specification which was installed)

vim / etc / inittab
. # Default runlevel The runlevels used are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id: 5: initdefault: # The bottom row of 3 to 5, the default to enter the command line interface
     
         
         
         
  More:      
 
- Java development specifications summary (Programming)
- Java singleton mode (Singleton mode) (Programming)
- ORA-01157 & ORA-01110 Troubleshooting (Database)
- To create someone else can not afford to delete the administrator user (Linux)
- HTTP Client Hints Introduction (Server)
- Start Linux ISO image directly from the hard disk (Linux)
- Linux more efficient than select a model epoll (Linux)
- Linux deploy Tutorial (Linux)
- Android memory optimization of the optimal load Bitmap (Linux)
- MySQL binlog automatic cleanup script (Database)
- SSH port forwarding application (Server)
- Some MySQL interview questions (Database)
- Talk about the Linux folder permissions issue again (Linux)
- How Ubuntu Snappy Core 2 running on Raspberry Pi (Linux)
- System Safety: Windows and Linux platforms (Linux)
- How to install the latest version of the Eclipse in Ubuntu 14.04 (Linux)
- DBCA Error: ORA-19809: limit exceeded for recovery files process (Database)
- Linux directory configuration (Linux)
- How to monitor Linux system performance Nmon (Linux)
- linux server security (Linux)
     
           
     
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.