mgetty problem

mgetty problem

[Beginner]

Hi Admins,

FC4 on HP Proliant

I had a problem today where users couldn't login to the telnet 
application they use. In the end a reboot solved it. I noticed that 
there were a lot of errors in the messages file:

Jul 29 04:00:07 mgetty[7424]: init chat failed, exiting...: 
Interrupted system call
Jul 29 04:00:07 mgetty[7424]: failed in mg_init_data, dev=ttyS0, 
pid=7424
Jul 29 04:00:52 mgetty[7472]: init chat failed, exiting...: 
Interrupted system call
Jul 29 04:00:52 mgetty[7472]: failed in mg_init_data, dev=ttyS0, 
pid=7472
Jul 29 04:01:38  mgetty[7533]: init chat failed, exiting...: 
Interrupted system call
Jul 29 04:01:38 mgetty[7533]: failed in mg_init_data, dev=ttyS0, 
pid=7533

and in mgetty.log.ttyS0:

07/31 11:14:29 yS0  timeout in chat script, waiting for `OK'
07/31 11:14:29 yS0  init chat timed out, trying force-init-chat
07/31 11:14:53 yS0  timeout in chat script, waiting for `OK'
07/31 11:14:53 yS0  init chat failed, exiting...: Interrupted system 
call

In the past ttyS0 was used (with a modem) as a dial-in terminal but 
it hasn't been used in over a year. From my searches I suspect I need 
to disable this now.

Will commenting out the lines in/etc/mgetty+sendfax/mgetty.config do 
it. Or am I barking up the wrong tree?

port ttyS0
debug 4
data-only y

Any thought appreciated? Thanx,
Dp.

Re: mgetty problem

[Carl]

Beginner wrote:
> Hi Admins,
>
> FC4 on HP Proliant
>
> I had a problem today where users couldn't login to the telnet 
> application they use. In the end a reboot solved it. I noticed that 
> there were a lot of errors in the messages file:
>
> Jul 29 04:00:07 mgetty[7424]: init chat failed, exiting...: 
> Interrupted system call
> Jul 29 04:00:07 mgetty[7424]: failed in mg_init_data, dev=ttyS0, 
> pid=7424
> Jul 29 04:00:52 mgetty[7472]: init chat failed, exiting...: 
> Interrupted system call
> Jul 29 04:00:52 mgetty[7472]: failed in mg_init_data, dev=ttyS0, 
> pid=7472
> Jul 29 04:01:38  mgetty[7533]: init chat failed, exiting...: 
> Interrupted system call
> Jul 29 04:01:38 mgetty[7533]: failed in mg_init_data, dev=ttyS0, 
> pid=7533
>
> and in mgetty.log.ttyS0:
>
> 07/31 11:14:29 yS0  timeout in chat script, waiting for `OK'
> 07/31 11:14:29 yS0  init chat timed out, trying force-init-chat
> 07/31 11:14:53 yS0  timeout in chat script, waiting for `OK'
> 07/31 11:14:53 yS0  init chat failed, exiting...: Interrupted system 
> call
>
> In the past ttyS0 was used (with a modem) as a dial-in terminal but 
> it hasn't been used in over a year. From my searches I suspect I need 
> to disable this now.
>
> Will commenting out the lines in/etc/mgetty+sendfax/mgetty.config do 
> it. Or am I barking up the wrong tree?
>
> port ttyS0
> debug 4
> data-only y
>
> Any thought appreciated? Thanx,
> Dp.
>
>   
First up a warning. I'm going to suggest you edit /etc/inittab manually 
which if done
incorrectly can cause serious system failure. You may even have a gui tool
in kde/gnome etc that would be safer to use but i dont known the 
available tools.

Most likely you need to turn off the respawn of the mgetty process in 
/etc/inittab.

Check /etc/inittab for a line that looks something like:

     ttyS0:2345:respawn:/sbin/mgetty dev=ttyS0 baud=19200

Yours will be different as i haven't run mgetty for years but it will 
reference mgetty (not mingetty, getty, agetty or uugetty).
You need to change the "respawn" field in the line to be "off" and then 
tell init to re-read inittab with "telinit q" as root.

Feel free to post your /etc/inittab for further guidance before editting it.

Re: mgetty problem

[Dermot Paikkos]

On 31 Jul 2007 at 14:29, Carl wrote:

> Beginner wrote:
> > Hi Admins,
...snipped

Found it. Here is the line I added yeas ago:

# Added by DP for modem use
# respawn off by DP on 31-07-07
S3:345:off:/sbin/mgetty -x3 ttyS0

> 
> Most likely you need to turn off the respawn of the mgetty process in
> /etc/inittab.
> 
> Check /etc/inittab for a line that looks something like:
> 
>      ttyS0:2345:respawn:/sbin/mgetty dev=ttyS0 baud=19200
> 
> Yours will be different as i haven't run mgetty for years but it will
> reference mgetty (not mingetty, getty, agetty or uugetty). You need to
> change the "respawn" field in the line to be "off" and then tell init
> to re-read inittab with "telinit q" as root.


Should I HUP init now for the change to take effect? Thanx,
Dp.

Re: mgetty problem

[Martin Klier]

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Am Dienstag 31 Juli 2007 15:41 schrieb Dermot Paikkos:
> Should I HUP init now for the change to take effect? Thanx,
> Dp.
# init q
should do it. Watch your system log at this time to see any surprises 
immediately.

Regards
-- 
Freundliche Grüße

i.A.
Martin Klier
Systemadministration/Datenbanken
------------------------------------------------------------------
A.T.U Auto-Teile-Unger
Handels GmbH & Co. KG
Dr.-Kilian-Str. 4 
92637 Weiden i.d. OPf.

Tel.: +49 961 306-5663
Fax : +49 961 306-5982

martin.klier@atu.de
www.atu.eu

Sitz: Weiden i. d. Opf., Amtsgericht Weiden i. d. OPf., HRA 2012
UST-ID Nr. DE814195392, WEEE-Nr. DE53789710
Persönlich haftende Gesellschafterin:
AFM Autofahrerfachmarkt Geschäftsführungs GmbH
Sitz: Weiden i. d. OPf., Amtsgericht Weiden i. d. OPf., HRB 2842
Geschäftsführer: Karsten Engel, Dirk Müller, Manfred Ries

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: mgetty problem

[terry white]

... ciao:

: on "7-31-2007" "Martin Klier" writ:
: # init q
: should do it

    may not be necessary, but i prefer:

    init q ; init u ...



-- 
... i'm a man, but i can change,
    if i have to , i guess ...