INIT: Command respawning too rapidly

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 init 0 and boot disk1 on same command line

Hello all, Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ...

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

3. Red Hat

INIT: Id "x" respawning too fast

Hi, OS: Oracle Enterprise Linux 4 My system was working normal then when i reboot the machine the system started but it is halting the boot sequence with this message "INIT: Id "x" respawning too fast: disabled for 5 minutes" Q: any solution to this reply is highly appreciated .

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

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

6. Solaris

Server Hang @ init command

Guys, I am having difficulties in bringing my server to OBP. The server hung infinitely after issuing init 0 command. I have already stopped all the applications running but to no avail. :confused: Has anyone encountered this problem before? Appreciate if you could shed some lights. ...

7. UNIX for Dummies Questions & Answers

HP-UX respawning boot failure

Hello. System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below) From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab...

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

9. UNIX for Dummies Questions & Answers

Command is respawning too rapidly..message

Ran into a new one today at work...... I was told to start 2 servers which were shut down due to a power outage(I don't believe they were shut down incorrectly). After fsck, both console logins appear with the message: INIT: Command is respawning too rapidly. Check for possible errors. >...

LEARN ABOUT OPENSOLARIS

systemd-getty-generator

SYSTEMD-GETTY-GENERATOR(8)				      systemd-getty-generator					SYSTEMD-GETTY-GENERATOR(8)

NAME

       systemd-getty-generator - Generator for enabling getty instances on the console

SYNOPSIS

       /lib/systemd/system-generators/systemd-getty-generator

DESCRIPTION

       systemd-getty-generator is a generator that automatically instantiates serial-getty@.service on the kernel console(s), if they can function
       as ttys and are not provided by the virtual console subsystem. It will also instantiate serial-getty@.service instances for virtualizer
       consoles, if execution in a virtualized environment is detected. If execution in a container environment is detected, it will instead
       enable console-getty.service for /dev/console, and container-getty@.service instances for additional container pseudo TTYs as requested by
       the container manager (see Container Interface[1]). This should ensure that the user is shown a login prompt at the right place, regardless
       of which environment the system is started in. For example, it is sufficient to redirect the kernel console with a kernel command line
       argument such as console= to get both kernel messages and a getty prompt on a serial TTY. See kernel-parameters.txt[2] for more information
       on the console= kernel parameter.

       systemd-getty-generator implements systemd.generator(7).

       Further information about configuration of gettys can be found in systemd for Administrators, Part XVI: Gettys on Serial Consoles (and
       Elsewhere)[3].

SEE ALSO

       systemd(1), agetty(8)

NOTES

	1. Container
	       Interface
	   https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface/

	2. kernel-parameters.txt
	   https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

	3. systemd for Administrators, Part XVI: Gettys on Serial Consoles (and Elsewhere)
	   http://0pointer.de/blog/projects/serial-console.html

systemd 237														SYSTEMD-GETTY-GENERATOR(8)

HP-UX