Syslog messages

[Omar Alvi_1]

Hi,

I have the following messages appearing in syslog.

Sep 1 17:07:49 rprod1 bootpd[19424]: reading "/etc/bootptab"

Sep 1 17:07:49 rprod1 bootpd[19424]: read 1 entries from "/etc/bootptab"

Sep 1 17:07:49 rprod1 bootpd[19424]: reading "/etc/dhcpdeny"

Sep 1 17:07:49 rprod1 bootpd[19424]: error opening "/etc/dhcpdeny": No such
fiy
Sep 1 17:07:55 rprod1 inetd[696]: bootps/udp: Died on signal 11

Sep 1 17:08:01 rprod1 bootpd[19444]:

Sep 1 17:08:01 rprod1 bootpd[19444]: reading "/etc/bootptab"

Sep 1 17:08:01 rprod1 bootpd[19444]: read 1 entries from "/etc/bootptab"

Sep 1 17:08:01 rprod1 bootpd[19444]: reading "/etc/dhcpdeny"

Sep 1 17:08:01 rprod1 bootpd[19444]: error opening "/etc/dhcpdeny": No such file.

These messages are rapidly increasing the logfile size.

I donot think disabling bootp is an option since I find I have an entry for a printer in the /etc/boottab file.

What other options do I have to get rid of these messages.

Thanks and Regards

-Alvi

Oh, by the way I have a sendmail config problem posted (subject: sendmail - external mail) , need some help there ... urgently.

thanks again

[Sridhar Bhaskarla]

What is this server used for?. Looks like you enabled DHCP on this server. Try disabling it if you don't use it or touch a file "/etc/dhcpdeny".

-Sri

[Tim Adamson_1]

Have you made any changes to the server recently?

It might pay to disable bootps in the short term just to stop the messages. In the meantime you can investigate potential cause of the problem.


Tim.

[T G Manikandan]

Comment out

#bootps dgram udp wait root /usr/lbin/bootpd bootpd

in the /etc/inetd.conf file

Then do a
#/usr/sbin/inetd -c

[Steven E. Protter]

It would appear that you have an Ignite DHCP server thats been messed up. I'd look at stopping the DHCP conflict.

Either you want it on or you want it off.

This looks like an Ignite setup, so you might quickly reconfigure the DHCP portion as follows:

/opt/ignite/bin/ignite

There is a User Interface for reconfiguring the server in there and you might be able to stop the messaging in that way.

If not, cp the syslog to another filesystem so you don't have problems with /var filling up.

SEP

[Con O'Kelly]

Hi

One other thought, if you have logging enabled for inetd (-l), this might be generating alot of messages in syslog.log for bootpd.
Check if logging is enabled for inetd & if so turn it off until you resolve your bootpd issue.

Also post the entry for bootps from your /etc/inetd.conf. Someone might be able to help with the bootpd config & solve your problem.

Cheers
Con

[T G Manikandan]

Also loading these patches should fix these

If 11.00

http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_19241&context=hpux:800:11:00

if 10.20

PHNE_19095
http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_19095&context=hpux:800:10:20

[SM_3]

TG

How do you find the patches for a given problem?

Do you just search using a keyword?

You always seem to get it spot on!

Thanks

[Omar Alvi_1]

Thanks for your responses.

Very important point I remembered. I've been having these messages since installing the latest jetDirect. In fact i have these messages (with some variations) on the other machines on which I installed jetDirect as well.

Since I have an entry in /etc/boottab, for a printer in use, I cannot disable the bootp protocol.

As for the patch PHNE_19241, it claims to fix the problem "3. BOOTPD messages filling up syslog.log." however, I have the patch installed and still getting these messages.

Regards,

-Alvi

[T G Manikandan]

If you are using bootpd then you can follow what Sri has mentioned.

Just create a empty file

#touch /etc/dhcptab

This should fix it.

Revert

[Pete Randall]

T.G.,

I think that should be "/etc/dhcpdeny". Create (touch) /etc/dhcpdeny and that shoud fix (at least some of) these messages.


Pete

[T G Manikandan]

Pete,

typo error.
I will make sure that small typo errors does not create big problems.

Thanks for pointing out
It is

/etc/dhcpdeny

[T G Manikandan]

Also,the messages can be reduced by increasing the timeout value of the bootpd.

The bootpd starts when there is a boot request .
the bootpd timeouts when there is no request for 500 minutes.

So adding the -t0 option should tell that there is no timeout and less messages are logged into syslog. i.e when the bootpd starts after a timeout it checks the bootptab and logs all those informational messages into syslog.

Also you can set the logging messages level using the -d option.the levels vary from 1-3.

it can be configured like

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

Thanks