Sponsored Content
Operating Systems HP-UX INIT: Command respawning too rapidly Post 302174299 by 1bigdog on Monday 10th of March 2008 05:08:57 PM
Old 03-10-2008
Error INIT: Command respawning too rapidly

INIT:Command is respawning too rapidly
Check for errors:
id:cons /usr/sbin/getty console console

A solution I read about in a different HPUX Forums help pages on line, said to add the -h option to this command in the /etc/inittab file to correct the problem.

I tried this and it did not work.

Another solution was to copy over a fresh copy of the inittab, which I did:

#cd /etc
#cp inittab inittab.bak
#cp /usr/newconfig/etc/inittab inittab
#init q

-I then added the -h option, rebooted, and came back with the same error.

Any assistance would be appreciated.
 

9 More Discussions You Might Find Interesting

1. 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. >... (5 Replies)
Discussion started by: finster
5 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 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... (2 Replies)
Discussion started by: westcoast
2 Replies

4. 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. ... (4 Replies)
Discussion started by: honmin
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: 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 . (5 Replies)
Discussion started by: maooah
5 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. 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 Replies)
Discussion started by: tording99z28
2 Replies
lat_manual_setup(7)					 Miscellaneous Information Manual				       lat_manual_setup(7)

NAME
lat_manual_setup - Describes how to manually set up the Local Area Transport (LAT) DESCRIPTION
To run LAT on your system, you must configure LAT in your system's kernel (see the Network Administration manual). Optionally, you can customize your LAT setup. The customization section of the Network Administration manual includes information on gen- eral customization, setting up printers, host-initiated connections, the LAT/Telnet gateway, and creating your own service. For more information on customizing LAT, see the Network Administration manual. Setting Up LAT To set up LAT on your system manually, you must first configure your kernel for LAT (see the Network Administration manual). Then log in as superuser and perform the following steps: Create the LAT device special files. LAT supports SVR4-style and BSD-style devices. You should use SVR4-style devices. See the Network Administration manual for more information. You should use the latsetup utility to create SVR4-style devices to ensure that duplicate minor numbers are not used. You can use the mknod command to create character devices with a major number of 5. If you create SVR4 devices manually, you should observe the following rules: Start the SVR4 device numbers at /dev/lat/620. This avoids overlapping minor numbers from the BSD tty name space. Make the minor number of the SVR4 device the same as the name. For example, device /dev/lat/833 should have minor num- ber 833. The following command would create the SVR4-style LAT device /dev/lat/833: # /usr/sbin/mknod /dev/lat/833 c 5 833 Once you have created the SVR4-style device, check the permissions of the device to make sure they are what you desire. You can create BSD-style devices by running the /dev/MAKEDEV script with the LAT option. The syntax for the MAKEDEV command with the LAT option is as follows: MAKEDEV latN The N variable can be 0 to 38. The /dev/MAKEDEV script creates one BSD-style LAT device special file for each LAT terminal device. When you run the MAKEDEV script, it creates 16 BSD-style LAT device special files, and creates the LAT control device (/dev/streams/lat), if it has not already been created. The MAKEDEV script requires 16 contiguous LAT device special files to be available. (Specifying lat38 requires only 12 contiguous LAT device special files to be available.) For example, the following commands create a total of 32 BSD-style LAT device special files: # cd /dev # MAKEDEV lat0 # MAKEDEV lat1 Record the device special file information displayed by the MAKEDEV script. The special file names vary depending on the number of terminal devices already configured. The following is sample output from the MAKEDEV command: MAKEDEV: special file(s) for lat1: tty16 tty17 tty18 tty19 tty1a tty1b tty1c tty1d tty1e tty1f tty1g tty1h tty1i tty1j tty1k tty1l Edit the /etc/inittab file to include entries for the LAT device special files you created. For example: lat620:34:respawn:/usr/sbin/getty /dev/lat/620 console vt100 lat621:34:respawn:/usr/sbin/getty lat/621 console vt100 lat630:34:respawn:/usr/sbin/lattelnet lat/630 lattelnet The second field (34) specifies the run levels at which the LAT devices are spawned; in this example, the getty process is spawned at either run level 3 or 4. The first entry uses an absolute pathname for the device (/dev/lat/620). The second uses a relative pathname (lat/621). The previous example shows how to add entries to the /etc/inittab file for SVR4 LAT devices. The following example shows entries for BSD LAT devices: lat16:34:respawn:/usr/sbin/getty tty16 console vt100 lat17:34:respawn:/usr/sbin/getty tty17 console vt100 lat18:34:respawn:/usr/sbin/lattelnet tty18 lattelnet18 For more information, see the inittab(4) and getty(8) reference pages. The Network Administration manual provides additional information on SVR4 and BSD devices. Use the following command to spawn the pro- cesses for the LAT device special files that you added to the /etc/inittab file: # /sbin/init q Create the STREAMS special file required by LAT by issuing the following command: # /usr/sbin/strsetup -i Enable LAT automatic startup and shutdown by using the following command: # /usr/sbin/rcmgr set LAT_SETUP 1 When LAT automatic startup and shutdown is enabled, the /sbin/init.d/lat file automatically starts LAT upon reaching run level 3 and automatically stops LAT when exiting run level 3. Start LAT by issuing the following command: # /usr/sbin/latcp -s RELATED INFORMATION
Commands: llogin(1), netstat(1), getty(8), init(8), latcp(8), latsetup(8), MAKEDEV(8), mknod(8), rcmgr(8), strsetup(8). Files: inittab(4). Introduction: lat_intro(7). Network Administration , System Administration delim off lat_manual_setup(7)
All times are GMT -4. The time now is 04:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy