Technical article 107694

bootp is filling syslog with errors. How can I get rid of them?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

bootp is filling syslog with errors similar to:

pid <xxxx> hardware address not found <xxxx>

As the errors are frequent, syslog can grow to be large.

Cause

bootp assigns IP addresses and network information to devices that don't store their own information, such as network printers.

The errors in syslog can mean that a bootp enabled device on the network is unreachable or non-operational. The device can be either a known device on the local network, or an unknown device across the router on a WAN.

Solution

Directly address the problem reported by the error by finding the offending device, which is trackable by the mac address provided in the error message. Resolve the problem communicating with it.

If this is not possible, perhaps because the device is unknown or remote, you may have to choose a less direct route. bootp is invoked by inetd, and is run according to the script in /etc/inetd.conf. Despite the errors, you will want to keep bootp running, if it is actually meant to support a known working device on your network. In this case, you may disable the error reporting for bootp by setting its debug level to 0. To do this, edit /etc/inetd.conf, and add a -D parameter after bootpd:

bootps dgram udp wait root /etc/bootpd -D bootpd -D

This will keep syslog from filling with errors, but allow bootp
to continue running.  It does, however, introduce the risk that
you will not receive messages that actually can be helpful.

If, on the other hand, you want to disable bootpd entirely, because it is not supporting any known devices on your network, then do the following:

1. In /etc/inetd.conf, comment out the line that starts bootpd:

# bootps dgram udp wait root /etc/bootpd bootpd

2. Find the process id for inetd from the process table:

ps -ef | grep inetd

3. Have users exit networked applications and log off system. Kill the process for inetd with a -1 option, to force a rereading of inetd.conf:

kill -1 <pid>

or restart the system by issuing the command:

init 6

4. This will terminate bootpd, so that the errors no longer appear.

Alternatively, you may boot the system into Maintenance Mode, edit /etc/inetd.conf as specified in step 1, and then either initiate full networking with the command:

init 2

or restart the system, as in step 3.

See also

Manual pages: bootpd(ADMN), bootp(ADMN), inetd.conf(SFF)

From the Xinuos technical article database, record 107694. Reproduced with permission. The original is at www.sco.com/ta/107694, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.