getty process not running....

[vtpaulson]

Hi,

In one of my 10.20 server getty process is not running properly. Every time I do "init q" or getty it starts the process but immediately it dies. I couldn't see any error in syslog file. This is a working server and I didn't do any major change recently.

Anybody know why its happening like this???

Thanks in advance.

Paulson.

[Madhu Sudhan_1]

Every entry in /etc/inittab file will be of the format
id:rstate:action:process .

Here for getty process the action field should "respawn" which tells init to re-spawn if the process dies.

-Madhu

[Alexander M. Ermes]

Hi there.
Check your /etc/inittab for a line similar to this :

a0:3:respawn:/usr/sbin/getty -h -t60 ttyd2a5 38400m # Dialback Modem

or this :

a1:3:respawn:/usr/sbin/getty -h ttyd2a7 9600
.


If this is ok, check your /var/adm/syslog/syslog.log for the reason, why the process dies.
If you find more details and still need help, let us know.
Rgds
Alexander M. Ermes

[Animesh Chakraborty]

Hi paulson,
I know one case where the console loging used to hang.Are you also facing this problem on colsole login ?

The PPID (parent process id) of the getty running on the console
is vuelogin. When running X-terminal and not using VUE, this situation will
occur. There is a conflict between the two competing processes to spawn a
getty on the console.

In order to alleviate this problem, execute the following:

1. Go into /etc/inittab

2. Change vuerc to off

3. Change the cons entry back to respawn

4. Re-read the inittab file:

init q

Animesh
animesh99@hotmail.com

[vtpaulson]

Guys thanks for your answers...

But I didn't get any solution yet.

my inittab entries are exactly correct. And whenever I restart through init q, getty starts and I could see when I do ps -ef. But the next movement it won't be there!...So I couldn't start my console connection.

There is no error in syslog at all (I started my inetd with -l option)..

[Animesh Chakraborty]

Hi,
Have you tried the microsoft policy?rebooting the server ?

[Animesh Chakraborty]

Hi,
Another thought:
May be your /etc/inittab has become corrupt. To resolve, do the following:

1. Back up your /etc/inittab.

2. cp /usr/newconfig/etc/inittab /etc/inittab

3. init q

Once the getty starts on the console (/dev/console), you can
add additional inittab entries.

[Patrick Wessel]

Try to start the getty from the command line, not out of the inittab. If it generates any kind of error message it will be posted to your terminal.
Can you post us your complete inittab?

[D. Jackson_1]

Is there someone logged on to the master console(server console) - Doesn't the getty process die when someone logs into the console??? I know it does on 11.0 .

[vtpaulson]

Guys,

Thanks for all your answers.

Atlast I find out the root cause of the problem. Actually we are using TAS(Terminal Access server) somehow when we connect the TAS getty process get killed!!...When I connected a dump terminal in the console port and restart the getty it started working fine.

Paulson