topic Re: continuous getty error in syslog in Operating System - HP-UX

continuous getty error in syslog

Darryl Darling_1 — Fri, 11 Oct 2002 13:13:05 GMT

I have a 10.20 system that is getting the following error continuously in the system log.

syslog: getty: cannot open "ttydnn". errno: 19 where nn is a numeric value.

Any ideas on this are appreciated

Re: continuous getty error in syslog

Clemens van Everdingen — Fri, 11 Oct 2002 13:16:50 GMT

Hi,

Try this:

1. Modify /etc/inittab by removing the getty entries running on ttys that are not being used.

2. init q

C.

Re: continuous getty error in syslog

MANOJ SRIVASTAVA — Fri, 11 Oct 2002 13:21:03 GMT

Hi

Do a vi /etc/inittab ans check for the ttydnn , you can commnet out the same if the line is not being used , incase it is being used by some serial device the port amy have some problem . Also after you comment the line you need to a ps -aef | grep on the ttydnn and then kill any process assoiated with it

Manoj Srivastava

Re: continuous getty error in syslog

A. Clay Stephenson — Fri, 11 Oct 2002 13:23:04 GMT

Getty is attempting to run on a device, /dev/ttydnn, that does not exist.

You may be missing device nodes. If so, an insf command (insf -C tty) can be used to recreate them. Man insf for details. Hardware may also be bad or have been removed. You can edit /etc/inittab and change the offending entries from 'respawn' to 'off'. After editing inittab, you will need to issue an 'init q' command to cause a re-read on /etc/inittab.

Re: continuous getty error in syslog

Eric Hess — Fri, 11 Oct 2002 13:25:29 GMT

More than likely this message is comming from /etc/inittab. It is a modem that was but is not currently on your system. The /etc/inittab probably looks like this.

ttp1:234:respawn:/usr/sbin/getty -h ttydnn 9600

Just remark that line out of /etc/inittab if thats the case. Hope this helps.

Re: continuous getty error in syslog

Darren Prior — Fri, 11 Oct 2002 14:24:25 GMT

Hi,

errno 19 is no such device (see /usr/include/sys/errno.h)

As others have stated this error is generally caused by having a getty setup in /etc/inittab for a non-existent port.

If you're seeing different values of nn then it suggests that someone has either removed a load of device files that they didn't think they needed. Alternatively someone has restored a previous inittab that did contain many gettys.

The fix is to either recreate the device files if you need them, or remove (or turn off) the getty lines from /etc/inittab and run init q.

regards,

Darren.