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.
I have old CentOS 4.6 server and its unable to boot now, I have access to it in Single user mode over KVM and I desperately need help to get it running so that I can take necessary backup, after that I will do OS upgrade and other upgrade such cent os 5.2 etc..
Error I am getting is :
Code:
INIT: /etc/inittab["line_number"] : missing action field
INIT: /etc/inittab["line_number"] : missing action field
INIT: /etc/inittab["line_number"] : missing action field
"NIT: Cannot Execut /etc/rc.d/rc.sysinit
I looked forum and I found that might be bcz I edited /etc/inittab from windows machine as difference of line handling in windows and linux causes problem.
Prior to this problem, I had upgraded PERL using "CPAN" on my server and added MONIT, for Monit I had added following lines in /etc/inittab as per docs. And it is the only Modification I did to inittab.
I later removed it using vi over console but still same error.
Also I had this error lately :
Code:
INIT: "X" respawning too fast
INIT: "X" respawning too fast
INIT: "X" respawning too fast
but server was running and I had plan to troubleshoot it once I upgrade my perl etc.
but now I am unable to boot.
Below is my /etc/inittab
Code:
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#
# Default runlevel. The runlevels used by RHS 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:3:initdefault:
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
#For MONIT
#mo:2345:respawn:/usr/local/bin/monit -Ic /etc/monitrc
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
Now I am connect to server over KVM in single user mode, please help me what I am supposed to do now ..
No, vi will preserve the DOS/Windows line endings. There maybe a way of forcing vi to save with Unix line endings, I'm not sure. dos2unix is quick and easy
Does that means that in single user mode, its readonly mode ?
I didn't think so. See what the 'mount' command tells you, should see (rw) after each mount. Also see what 'dmesg' reports, that's the boot log, look for any signs of errors. Is it possible that you actually have a harddrive problem?
Are you sure your booting into 'single' mode and not 'emergency' mode? I think everything is mounted read-only in emergency mode.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.