BOOTREQUEST Error

[paula hawk_2]

Has anyone seen this message? I am receiving it in my syslogs continuously. I am running 10.20.

Aug 21 15:11:21 hp0071 last message repeated 13 times
Aug 21 15:11:24 hp0071 bootpd[795]: Discarding BOOTREQUEST. Could not decode pac
ket.

[Sajid_1]

hello,

This message is from the bootpd daemon. Apply this patch: PHNE_19095

[Sajid_1]

This is the patch description, if you want to check:
http://support1.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=PHNE_19095

[Jeff Schussele]

Hi Paula,

If you're not serving bootp requests then stop the daemon:
/sbin/init.d/rbootd stop

HTH,
Jeff

[S.K. Chan]

I have not seen it before but I'm pretty sure it's related to one or more bootp request that got rejected or it may just be one of those "informational only" logs that fills up your syslog.log. Usually you should only be getting logs like ..
Jan 2 ... bootpd[184]: boot_bootrequest: request from hardware address 008003...
Jun 2 ... bootpd[184]: found 121.X.X.X ....
if bootpd is serving. Take a look at patch PHNE_19095 (cumulative bootpd/DHCP).
http://support1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_19095&context=hpux:800:10:20
Look for keyword BOOTREQUEST and right below that line ..
quote:
Bootpd fills up syslog with events that are confusing or not cared about. The logging and debug level were not in synch with each other.
unquote:
This may just be what you need. Just take note it has dependencies on other patches if you decide to install it.

[paula hawk_2]

Jeff,

I tried stopping the daemon, but it is not running and the messages are continuing. Any other ideas?

[Jeff Schussele]

Hi (again) Paula,

Well, PHNE_17123 addressed the syslog message issue, but PHNE_19095 is the most current.
So at least apply PHNE_17123 if not PHNE_19095.
Neither requires a reboot & both have been out since 2000 or longer, so even the most conservative patch strategy should allow either.

Rgds,
Jeff

[S.K. Chan]

No quite right .. bootp is started from /etc/inetd.conf. Edit the file, comment the line out and re-read the file ..
# inetd -c
Before that kill your bootp daemon. That should stop bootpd from starting up.

[Jeff Schussele]

DOOOOH!!!!
Forgot all about inetd.conf.
S.K. is right on.
Comment that puppy out.
Thanks for the save S.K.!

Rgds,
Jeff

[S.K. Chan]

.. no big deal Jeff .. just happened to be in the neighborhood .. :)