Continuous bootps/udp errors in SYSLOG

[William Horton]

I am running HP-UX 11.1i V2 and am getting continuous errors in SYSLOG regarding bootps/udp.
bootpd[8837]:reading "/etc/bootptab" bootpd[8837]: read 1 entries from "/etc/bootptab" bootpd[8837]: reading "/etc/dhcpdeny" bootpd[8837]: read 0 entries from "/etc/dhcpdeny"
inetd[710]: bootps/udp: Died on signal 11

Last week, I had an additional error :
Cannot open /etc/dhcpdeny and I TOUCHED the file to /etc and CHMOD 644 to it and performed an inetd -c

My netdeaemons value for REMOTE_BOOT IS A "1".

The only way we ever boot/re-boot is to login on the console or connect in on the modem and re-boot.. Can I safely set the Remote_Boot value at zero, re-read the inetd and get these errors to stop.

1.) Why are we getting these errors after running without them for years?
2.) System re-boot did NOT stop these errors.

Thank You
Bill

[IT_2007]

Did you setup this for DHCP? check /etc/rc.config.d/netconf for DHCP entries.

If you do man bootpd and here is the information:

When bootpd receives a DHCP/BOOTP request, it first checks if the
hardware address of the client is listed in the /etc/dhcpdeny
database. If yes, this client is denied lease. If the client is not
listed in the dhcpdeny database, it checks whether the client
information is in the /etc/bootptab database. If the client
information is available, bootpd sends back the reply. Otherwise, it
checks whether there is any matched relay information for the client
in the /etc/bootptab database. If so, bootpd goes through a series of
checks to see if it should relay the request. If no matched relay
information was found, bootpd checks whether the client information is
matched by a pool or device group in the /etc/dhcptab database. If a
match is found, bootpd sends back a reply. The request is dropped if
no matched group information is found.

[William Horton]

DHCP_ENABLE[0]=0
Nothing uncommented in bootptab.
no DHCPTAB
We do not dynamic assign. we are static.

Other than that, not sure what I am supposed to do here.
Thanks
Bill

[Robert-Jan Goossens · Accepted solution]

Hi Bill,

What about your /etc/inetd.conf file, is bootps commented out?

# grep bootps /etc/inetd.conf
#bootps dgram udp wait root /usr/lbin/bootpd bootpd

if not use vi to comment out bootps, and reread the inetd.conf "inetd -c"

Did someone setup an Ignite server?

Hope this helps,
Robert-Jan

[William Horton]

We do use ignite but noone set up an ignite server.
Our inetd.conf says this for 'bootps'
bootps dgram udp wait root /usr/lbin/bootpd bootpd

I can comment that and re-read the config using inetd -c

Are you saying that will stop these errors?
Are these dynamic ip requests from some other server or router on the LAN. We never had these for 10 years and now have them
Thanks for your help and fast response.
Bill

[William Horton]

Seems to have taken care of our dilemma.
last entry in SYSLOG says:
inetd[710]: Rereading configuration inetd[710]: bootps/udp: Deleted service inetd[710]: Thru with configuration inetd[710]: Configuration complete
No more BOOTPD errors now.
Thanks for your help and fast response!.
Bill