Sponsored Content
Top Forums UNIX for Dummies Questions & Answers WARNING - exit init (PID1) died. Post 41241 by BAM on Wednesday 1st of October 2003 08:13:37 AM
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.
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
SYMLINKS(8)						      System Manager's Manual						       SYMLINKS(8)

NAME
symlinks - symbolic link maintenance utility SYNOPSIS
symlinks [ -cdrstv ] dirlist DESCRIPTION
symlinks is a useful utility for maintainers of FTP sites, CDROMs, and Linux software distributions. It scans directories for symbolic links and lists them on stdout, often revealing flaws in the filesystem tree. Each link is output with a classification of relative, absolute, dangling, messy, lengthy, or other_fs. relative links are those expressed as paths relative to the directory in which the links reside, usually independent of the mount point of the filesystem. absolute links are those given as an absolute path from the root directory as indicated by a leading slash (/). dangling links are those for which the target of the link does not currently exist. This commonly occurs for absolute links when a filesystem is mounted at other than its customary mount point (such as when the normal root filesystem is mounted at /mnt after booting from alternative media). messy links are links which contain unnecessary slashes or dots in the path. These are cleaned up as well when -c is specified. lengthy links are links which use "../" more than necessary in the path (eg. /bin/vi -> ../bin/vim) These are only detected when -s is specified, and are only cleaned up when -c is also specified. other_fs are those links whose target currently resides on a different filesystem from where symlinks was run (most useful with -r ). OPTIONS
-c convert absolute links (within the same filesystem) to relative links. This permits links to maintain their validity regardless of the mount point used for the filesystem -- a desirable setup in most cases. This option also causes any messy links to be cleaned up, and, if -s was also specified, then lengthy links are also shortened. Links affected by -c are prefixed with changed in the output. -d causes dangling links to be removed. -r recursively operate on subdirectories within the same filesystem. -s causes lengthy links to be detected. -t is used to test for what symlinks would do if -c were specified, but without really changing anything. -v show all symbolic links. By default, relative links are not shown unless -v is specified. BUGS
symlinks does not recurse or change links across filesystems. AUTHOR
symlinks has been written by Mark Lord <mlord@bnr.ca>, the developer and maintainer of the IDE Performance Package for linux. SEE ALSO
symlink(2) Version 1.2 November 1994 SYMLINKS(8)
All times are GMT -4. The time now is 11:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy