WARNING - exit init (PID1) died.


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers WARNING - exit init (PID1) died.
# 1  
Old 09-28-2003
Data WARNING - exit init (PID1) died.

Hi,

Today, on one of my SCO machines, i was getting the following:

PANIC : exit cannot exec /etc/init (PID1).

I used two floppy boot/root disks to boot from floppy.
I followed the procedures to restore the files:

/usr/lib/libc.so.1 and /etc/init.

When I reached the part of making sure that both above files are owned and executable by bin, I wanted to use the "chown" command, but this command was not found (not foun error).

So then i proceded without the chown step, umnounted the hard disk, reboot, but this time instead of getting a panic error, i am getting a warning instead:

WARNING - exit init (PID1) died.


Any help would be appreciated, meanwhile i will try to insert the /bin/chown in the floppy root disk to :

cp /mnt/bin/chown . (of course doing that after cd /mnt/bin), maybe this is the step that is still missing.

Thanks.
# 2  
Old 09-29-2003
Suggest a search on A.P. Lawrence.com for "exit cannot exec /etc/init".

That is where you will find this:
Quote:
Panic cannot exec /etc/init ( PID 1) status 9 *can* be caused by a missing symbolic link for /usr/lib/libc.so.1
If so you need to boot from other media and recreate the link- it's in /opt/K/SCO/Unix/5.0.*/usr/lib
This can also be caused by /etc/init's link being missing; the real file for that is in /opt/K/SCO/Unix/etc
Other circumstances can also cause this-
and other info relating to your problem.
# 3  
Old 09-30-2003
I appreciate your reply.
I already tried this solution and after applying it, i started receiving a init died message instead of the cannot exce init.

I think my problem is bigger than that, /bin has only one component: the posix directory....it is empty man.


Quote:
Originally posted by RTM
Suggest a search on A.P. Lawrence.com for "exit cannot exec /etc/init".

That is where you will find this:

and other info relating to your problem.
# 4  
Old 09-30-2003
Unless you have a good backup then it looks like a rebuild.
# 5  
Old 09-30-2003
I assume that you have mounted your root filesystem on another box or something so that you can examine it?

I have access to a SCO box. uname -a says:
SCO_SV scobox 3.2 2 i386

/bin is nothing but a bunch of symbolic links.
For example:
sh -> /opt/K/SCO/Unix/5.0.2Dp/bin/sh

That directory is the most common one in my symlinks, but there are others.

So my guess is that someone removed all of your symbolic links. That would take something like
find / -type l -exec rm "{}"
run as root.

Removing a symbolic link or anything else will update the inode change time on the directory which contained it. If you have not touched /bin yet:
ls -lcd /bin
will tell you when that happened. sulog and/or wtmp may give an idea as to who did it. Unless everyone just logs on as root.
# 6  
Old 10-01-2003
Thanks for your reply.

But I did not get exactly your solution Smilie
I think you mentioned what might have happened, but not what i should do to get the machine again up.

Thanks.

Quote:
Originally posted by Perderabo
I assume that you have mounted your root filesystem on another box or something so that you can examine it?

I have access to a SCO box. uname -a says:
SCO_SV scobox 3.2 2 i386

/bin is nothing but a bunch of symbolic links.
For example:
sh -> /opt/K/SCO/Unix/5.0.2Dp/bin/sh

That directory is the most common one in my symlinks, but there are others.

So my guess is that someone removed all of your symbolic links. That would take something like
find / -type l -exec rm "{}"
run as root.

Removing a symbolic link or anything else will update the inode change time on the directory which contained it. If you have not touched /bin yet:
ls -lcd /bin
will tell you when that happened. sulog and/or wtmp may give an idea as to who did it. Unless everyone just logs on as root.
# 7  
Old 10-01-2003
I would reload the os, rebuild my file systems, and read in my last backup tape. That will be much easier than trying to undo a disaster like that.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. SCO

PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200

Hi to all, I hope that you can help me with this... SCO Unix 5.0.5, old mashine Pentium III x86, SCSI HDD 36.4 Gb PANIC: exit – Cannot exec /etc/init (PID 1), status 0x00000200 Cannot dump 49055 pages to dumpdev hd (1/41) : space for only 48640 pages Dump not completed Safe to Power Off... (1 Reply)
Discussion started by: lakicevic
1 Replies

2. UNIX for Dummies Questions & Answers

WARNING: init(1M) exited on fatal signal 9: restarting automatically

Have you ever got these : WARNING: init(1M) exited on fatal signal 9: restarting automatically and how did you solve it? (3 Replies)
Discussion started by: anaABB
3 Replies

3. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies

4. UNIX for Advanced & Expert Users

Problem on init 0, execution is the same with init 6

Hi, I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS. When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies

5. SCO

PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200.

hi all when ever i power on my sco server it give me the message:PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200. its not booting. any help?? (1 Reply)
Discussion started by: Danish
1 Replies

6. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies

7. HP-UX

boot failure-init died

Hello. system fails on reboot this AM. received message about not possible for kernel to find process that caused crash. system does memory dump succesfully, then tries to boot again. looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies

8. UNIX and Linux Applications

My VNC died

Greetings all, I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message: "vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies

9. UNIX for Advanced & Expert Users

Init 6 & Init 0 problem

Hi Expert, I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0.. I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies

10. UNIX for Advanced & Expert Users

Many dtexec process that do not died

Hi, I have a problem on CDE 1.4 Solaris 8. It looks like each time I lock the screen, the dtexec that invoke the dtscreen (that is o.k.) do not died after it done his job and it stay in the system and cause many zombie. Any suggestions? Thanks, Itay. (3 Replies)
Discussion started by: itayst
3 Replies
Login or Register to Ask a Question