Sponsored Content
Top Forums UNIX for Dummies Questions & Answers WARNING: init(1M) exited on fatal signal 9: restarting automatically Post 302563064 by anaABB on Monday 10th of October 2011 04:27:47 AM
Old 10-10-2011
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?

Last edited by anaABB; 10-10-2011 at 07:09 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

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... (6 Replies)
Discussion started by: BAM
6 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 for Advanced & Expert Users

rerun a script if aborted and exited

Hello, When I run a script, the script sometimes exited. I need to re-run it automatically again. Currently I am using crontab to run the script each 5 minutes. However, I need to have a better solution. Any idea what to do? thanks (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

4. Solaris

d240 media tray is automatically restarting on sunfire 6800

d240 media tray(domain C) is which is connected to SUNFIRE 6800 (DOMAIN C),automatically restarting.remaining domains A and B are working fine..why i dont know..with out human intervention this domain is restarting automatically for 3 to 4 days in a day..plz solve this problem.why like this going... (4 Replies)
Discussion started by: tv.praveenkumar
4 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. 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

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

8. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies

9. Solaris

./deinstall: Exited from program error

I am wondering if I can get some help here. I am deinstalling Oracle home on solaris. Downloaded deintsall zip file from oracle and then ran ./deinstall -home (Full Path) 10 seconds later I get this: Any idea how to resolve this issue? $ ./deinstall -home... (4 Replies)
Discussion started by: newborndba
4 Replies

10. What is on Your Mind?

PHP Fatal Errors During SSL Cert Management - PHP Fatal error: xc_fcntl_mutex failed

Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup. However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
ctrun(1)							   User Commands							  ctrun(1)

NAME
ctrun - execute command in a process contract SYNOPSIS
/usr/bin/ctrun [options] command [ argument...] DESCRIPTION
The ctrun utility starts a command in a newly created process contract. ctrun holds the contract and can be instructed to output or respond to events that occur within the contract. For additional information about process contracts, see contract(4) and process(4). OPTIONS
The following options are supported: -i event,[event ...] -f event,[event ...] Sets the informative and fatal events, respectively. The following are valid events: core A member process dumped core. core events are informative by default. empty The last member of the process contract exited. exit A member process exited. fork A process was added to the process contract. hwerr A member process encountered a hardware error. hwerr events are fatal by default. signal A member process received a fatal signal from a process in a different process contract. Only core, hwerr, and signal events can be made fatal. More events can be delivered than requested if ctrun requires them for its own purposes. For example, empty messages are always requested if a lifetime of contract is specified. See -l. -l lifetime The following valid lifetime values are supported: child ctrun exits when the command exits, regardless of whether the contract is empty. contract ctrun exits only when the contract exits. This is the default. none ctrun exits immediately, orphaning the contract. -o option,[option ...] The following options are supported: noorphan Kills all processes in the contract if the holder (ctrun) exits. This option is invalid when a lifetime of none is specified. pgrponly If a fatal error occurs, kills at most the process group of which the errant process is a member. regent The contract inherits inheritable contracts when abandoned by member processes. -r count If the contract encounters a fault, this option attempts to restart the command count times. If count is 0, the attempt to restart con- tinues indefinitely. By default, ctrun does not attempt to restart the command. This option is invalid if a lifetime other than contract is specified or if the pgrponly option is used. -t If the contract created by ctrun inherited subcontracts from its member processes, attempts to transfer them to the new contract when restarting. This option is invalid unless -r is also specified. -v Displays contract events and ctrun actions as they occur. -V Displays verbose contract events, as are displayed by the -v option of ctwatch. Implies -v. OPERANDS
The following operands are supported: argument One of the strings treated as an argument to command. command The command to be passed to execvp(2). See exec(2). EXAMPLES
Example 1: Running a Shell in a New Process Contract The following example runs a shell in a new process contract: example% ctrun -l child -o pgrponly ksh The -l child option argument is specified so that ctrun won't wait until all children of the shell have exited. -o pgrponly is specified because an interactive ksh puts each job in a new process group, and an error in one job is unlikely to affect the others. Example 2: Running a Simple Server The following example runs a simple server: example% ctrun -r 0 -t -f hwerr,core,signal server The -r 0 and -t options are specified to indicate that if the server encounters a fatal error, ctrun should try to restart it. The -f option makes "hwerr", "core", and "signal" fatal events. EXIT STATUS
If command is specified and successfully invoked (see exec(2)), the exit status of ctrun is the exit status of command. Otherwise, ctrun exits with one of the following values: 123 The child process exited abnormally. 124 ctrun encountered an internal error. 125 Invalid arguments were provided to ctrun. 126 command was found but could not be invoked. 127 command could not be found. FILES
/system/contract/process/* ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ Human Readable Output is Unstable. Invocation is Evolving. SEE ALSO
ctstat(1), ctwatch(1), exec(2), contract(4), process(4), attributes(5) SunOS 5.10 15 Jul 2004 ctrun(1)
All times are GMT -4. The time now is 07:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy