topic syslog.log in Operating System - HP-UX

syslog.log

Clutier_1 — Tue, 13 Jan 2004 03:37:51 GMT

Hi,

i have some msg like this in the syslog.log file :

Jan 12 22:23:30 ciccogd above message repeats 59 times
Jan 12 16:23:43 ciccogd : getty: cannot open "tty0p1". errno: 2
Jan 12 16:43:24 ciccogd : getty: cannot open "tty0p1". errno: 2
Jan 12 22:43:31 ciccogd above message repeats 59 times
Jan 12 16:43:44 ciccogd : getty: cannot open "tty0p1". errno: 2
Jan 12 17:03:25 ciccogd : getty: cannot open "tty0p1". errno: 2

I do not manage to find the origin of these messages.

Re: syslog.log

Hoefnix — Tue, 13 Jan 2004 03:54:59 GMT

I am not sure, but could it be that there is a respwan-ed getty defined on this device in the /etc/inittab.
Try to remark this and run an "init q" after the edit and see if no new messages are logged.

#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600

Regards,

Peter

Re: syslog.log

Dietmar Konermann — Tue, 13 Jan 2004 04:00:05 GMT

Looks like there is a getty running, trying to open a line.

Error 2 means:

#define ENOENT 2 /* No such file or directory */

Either you deconfigure the getty for that line (usually configured in /etc/inittab.. comment out the entry, run init q) or you create a new device file, if it's still needed.

# mksf -C tty -I 0 -p 1

Best regards...
Dietmar.

Re: syslog.log

Ravi_8 — Tue, 13 Jan 2004 04:15:53 GMT

Hi

another suggestion,
#insf -e

run this command and check for log files again

Re: syslog.log

Andrew Cowan — Wed, 14 Jan 2004 03:57:00 GMT

Using the "#" character as a comment in the "/etc/inittab" is not a good idea. Either begin a comment line with ": " or set the entry to "off", then do an "init q".

If you have faulty entries in your "/etc/inittab" you should see that the "/var/adm/wtmp" will grow out of control, and eventually fill the filesystem.

Re: syslog.log

Elmar P. Kolkman — Wed, 14 Jan 2004 04:10:12 GMT

Any line started with a '#' is seen as comment by init (see the man page of inittab).
It seems you have copied the inittab file or line from a system with more serial ports, or you have removed a serial port/MUX, or something like that. You can see which serial ports exist with ioscan:
ioscan -fnkCtty

Since getty cannot open tty0p1, there are two solutions:
1) if /dev/tty0p1 doesn't exist, you might try to create it. This is already described, but only solves the issue if there is a real device connected to it. So after creating it with mknod, check if it is connected to a real device with ioscan of doing a cat of the device.
2) if /dev/tty0p1 exists, the device has no real hardware connected to it, so you can comment the line and think about removing the device file(s).

Re: syslog.log

Andrew Cowan — Wed, 14 Jan 2004 04:18:32 GMT

Interesting. I don't have a HP-UX machine in front of me, and am surprised that it uses "#" as a comment. In most versions of Unix "/etc/inittab" is an exceptional case, and tends to use ":" or ";" instead.

Re: syslog.log

Cheryl Griffin — Wed, 14 Jan 2004 08:45:40 GMT

Which os's use anything other than #? The # is a shell comment.

From the man page for sh(1) and/or inittab(4)
Comments Lines
A word beginning with # causes that word and all the following characters up to a newline to be ignored.

Re: syslog.log

Andrew Cowan — Wed, 14 Jan 2004 09:10:48 GMT

Oops, sorry should have said that "/etc/inittab" was an exception, and that most OS's dont use "#" as a comment in that particular file. AIX for example uses ": " to dentote comments.