|
|
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
10-01-2003
Thanks for your reply.
But I did not get exactly your solution
I think you mentioned what might have happened, but not what i should do to get the machine again up.
Thanks.
But I did not get exactly your solution
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.
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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT CENTOS
grub2-bios-setup
GRUB-BIOS-SETUP(3) Library Functions Manual GRUB-BIOS-SETUP(3) NAME
grub-bios-setup -- Set up images to boot from a device. SYNOPSIS
grub-bios-setup [-a | --allow-floppy] [-b | --boot-image=FILE] [-c | --core-image=FILE] [-d | --directory=DIR] [-f | --force] [-m | --device-map=FILE] [-s | --skip-fs-probe] [-v | --verbose] DEVICE DESCRIPTION
You should not normally run this program directly. Use grub-install instead. OPTIONS
--allow-floppy Make the device also bootable as a floppy. This option is the default for /dev/fdX devices. Some BIOSes will not boot images cre- ated with this option. --boot-image=FILE Use FILE as the boot image. The default value is boot.img. --core-image=FILE Use FILE as ther core image. The default value is core.img. --directory=DIR Use GRUB files in the directory DIR. The default value is /boot/grub. --force Install even if problems are detected. --device-map=FILE Use FILE as the device map. The default value is /boot/grub/device.map . --skip-fs-probe Do not probe DEVICE for filesystems. --verbose Print verbose messages. SEE ALSO
info grub Wed Feb 26 2014 GRUB-BIOS-SETUP(3)