gysbert1
asked on
INIT: error loading initresource
My linux setup has been working perfectly for around a year now, but a few weeks ago I started getting the problem that whenever I change runlevels (including when I shut down in other words) I get about 10000 messages saying
INIT: error loading initresource
the /var/log/messages file confirms the fact that I get around 10000 of these. (The amount is never the same)
I've searched long and hard through my /etc/inittab for errors, and gone through all the files in /etc/rc.d
Has anybody ever experienced this and found the answer? For a good answer you can score a cool 400 points....
INIT: error loading initresource
the /var/log/messages file confirms the fact that I get around 10000 of these. (The amount is never the same)
I've searched long and hard through my /etc/inittab for errors, and gone through all the files in /etc/rc.d
Has anybody ever experienced this and found the answer? For a good answer you can score a cool 400 points....
ASKER
I did not purposefully change anything, and I didn't have a disk crash. I did have to do a forced reboot once or twice though, but it never detected anything wrong with the inodes on startup. It just ran fsck on my drives.
Which version of init are you using? And which kernel and distribution?
ASKER
Distribution: Redhat 3.03
Kernel: 2.0.25
Init is the same one I originally got with this distribution. Not sure offhand what its version number is. I have tried with kernels ranging from 1.2.13, 2.0.0, 2.0.7 to 2.0.25 since I still had zImages of all those, but it doesn't make any difference.
Kernel: 2.0.25
Init is the same one I originally got with this distribution. Not sure offhand what its version number is. I have tried with kernels ranging from 1.2.13, 2.0.0, 2.0.7 to 2.0.25 since I still had zImages of all those, but it doesn't make any difference.
Linux 2.0 needs sysvinit version 2.64.
To find out your init version, use (taken from /usr/src/linux/Documentati
cat /proc/`cat /var/run/syslog.pid`/envir
If you get 2.59 or lower, you should upgrade. (Grab the RPM from RedHat or one of its mirrors.)
But that would not explain why you get the errors on a 1.2.13 kernel.
To find out your init version, use (taken from /usr/src/linux/Documentati
cat /proc/`cat /var/run/syslog.pid`/envir
If you get 2.59 or lower, you should upgrade. (Grab the RPM from RedHat or one of its mirrors.)
But that would not explain why you get the errors on a 1.2.13 kernel.
ASKER
I have got sysinit version 2.64. I think its definately something that went wrong at some point. When I upgraded to kernel 2 for the first time, I downloaded an upgrade rpm package which upgraded a whole bunch of files on my computer. That was quite long ago though, and the computer worked fine for a long time after that....
I guess your /sbin/init has become corrupted by the disk crash. If this is the case, reinstalling init will solve your problem.
If it doesn't, I don't know what's wrong.
If it doesn't, I don't know what's wrong.
ASKER
Been there, Done that, no luck.
Thanx for trying anyway ...
Any other ideas ?
Thanx for trying anyway ...
Any other ideas ?
/dev/initctl or /var/run/utmp corrupt?
These should repair themselves after a reboot.
I'm clueless.
These should repair themselves after a reboot.
I'm clueless.
ASKER
ggeens: Just send me an answer, any answer. One of your comments did it for me (the init version) For some reason I had version 2.58 and version 2.64 on the machine, and it was using 2.58 because it was in the /sbin directory. I don't know why 2.64 wasn't there though....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, but as soon as I saw what the problem was, I fixed all offending files. I think at some stage an rpm must have stuffed or something, or I was dreaming when I installed it. Thanks for the help, my linux is now nice again :)
Did you have a disk crash?
Did you had to do a forced reboot?