Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Salvete! I have a CentOS 2.6 system that I am setting up as a server. I think the system updated the kernel and now it won't complete the boot process.
When I installed the OS, I installed the GUI too, because I am still learning, and it helps. However, when I have everything ready, I will change the boot options to skip the GUI.
At any rate, my problem is that it won't finish booting now. Here is the readout that I get if I escape out of the splash screen:
Code:
Calling the system activity data collector (sadc): Cannot open /var/log/sa/sa19: Permission denied
Starting Monitoring.... [OK]
ip6tables... [OK]
Bringing up Loopback interface: [OK]
Starting auditd: [FAILED]
Starting portreserve: [OK]
Starting system logger: _
Now, I *am* able to boot to level 1, but not to level 3. So I booted to level 1 and
restarted with bootlevel1 and ran chmod 740 -R /var/log/sa
no dice.
With respect to this computing is binary, there is no need for "thinking", "guessing" or "worrying": you can check if the kernel was updated or not by reading whatever log file Yum(-updatesd?) logs to (usually syslog) by booting into runlevel 1 and 'less /var/log/messages'.
Quote:
Originally Posted by brother.gabriel
When I installed the OS, I installed the GUI too, because I am still learning, and it helps. However, when I have everything ready, I will change the boot options to skip the GUI.
Kinda OT but a server rarely requires X server, a Desktop Environment and graphical interface tools. Installing those packages pulls in a myriad of dependencies, adds to maintenance, running it requires resources and exposes the server more in terms of risk than strictly necessary. My suggestion would be to remove any packages you don't need now: you can always install them later on.
* While you're at it please do invest time reading the documentation Centos comes with and properly harden the machine. Once waste passed through the bowels starts hitting devices for creating currents of air your investment will show you it was worth it.
Quote:
Originally Posted by brother.gabriel
Code:
Calling the system activity data collector (sadc): Cannot open /var/log/sa/sa19: Permission denied
What does 'ls -alZ /var/log/sa/sa19; ls -aldZ /var/log/sa /var/log /var' return?
And 'audit2allow < /var/log/audit/audit.log' if the audit service is enabled?
Quote:
Originally Posted by brother.gabriel
Starting system logger: _[/CODE]
From this we can't see what's going on under the hood. Please boot into runlevel 1 and 'less /var/log/messages'.
Thanks for answering, unSpawn. If I reinstall the OS without the GUI, will I miss out on anything, considering I plan to use the machine to host Asterisk? On our old 2.4 CentOS, we had the GUI, but back then you could use the GUI for configuring more things, such as SAMBA and SUDO. In 2.6, the GUI does not come with that configuration, and it has to be done via CLI, anyway. When you say "myriad of dependencies, ...maintenance, and resources", I think you got me. If I won't miss anything in Asterisk (FreePBX, perhaps) then I'll do away with the GUI. What do you think?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.