issue in syslog

[lawrenzo_1]

We have softare that gives us root access to all servers in our organisation, so to access all other servers on the network we run command and a display is brought up using x-windows. This is currently either not working or taking over 2 minutes for the display to be displayed, message in the syslog is:

Apr 14 10:38:24 host bootpd[1940]: stat on "/etc/dhcptab": No such file or directory
Apr 14 10:38:24 host bootpd[1940]: Received DHCPDISCOVER creating DHCPOFFER. Request data: ci = 01080020F0E052, req IP not sent, ciaddr 0.0.0.0, giaddr 0.0.0.0, broadcast reply off, server id not sent.
Apr 14 10:38:24 host ltid[17230]: ltid received request type 92
Apr 14 10:38:24 host above message repeats 54 times
Apr 14 10:38:24 host ltid[17230]: ltid received request type 92

seems to be a problem with the DHCP server, has anyone seen this previously?

[lawrenzo_1]

also seems to be an issue with:

ptyfork failed in ptysystem,

I'm pretty sure this haas something to do with the kernel params being exceeded but which one?

Thanks

[Pete Randall]

I don't use DHCP so I have no idea what you may be running into, but I would suggest checking dmesg output and "glance > reports > system info > system tables reports" for help on kernel parameter overflows.


Pete

[Pete Randall]

Also "sar -v" can give you a little glimpse into the kernel.


Pete

[Joseph Loo]

hi,

a somewhat similar problem is seen in the knowledge base:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000076640931

regards.

[Biswajit Tripathy · Accepted solution]

You are seeing the messages because
(intentionally or not) your machine is running a
DHCP server. Since a DHCP server is supposed to
read a dhcptab file (which does not exist on your
machine), accept a DHCPDISCOVER and reply with
a DHCPOFFER, there is nothing really wrong in the
above messages.

Since you don't have a dhcptab file, my guess is,
it is not your intention to run DHCP server on
the system. So you need to stop running DHCP
server daemon. Steps to do this are:

1) Comment the line starting with bootps in file
/etc/inetd.conf (i.e place a '#' char as the first char
of the line).
2) Reconfigure inetd by executing
# inetd -C
3) Find pid of currently running bootpd process and
kill it.

- Biswajit

[lawrenzo_1]

issue is with the pty count in the kernel

thanks for your help