1844191 Members
2820 Online
110229 Solutions
New Discussion

syslog.log

 
Jim Spencer_1
Occasional Contributor

syslog.log

I'm getting the following message every ten minutes in my syslog.log and don't know where to look to fix the problem.

Jul 29 07:14:06 Avenger inetd[13805]: bootps/udp: bind: Address already in use
Jul 29 07:14:06 Avenger inetd[13805]: bootps/udp: Service enabled
Jul 29 07:24:06 Avenger inetd[13805]: bootps/udp: bind: Address already in use
Jul 29 07:24:06 Avenger inetd[13805]: bootps/udp: Service enabled

There is a time to laugh and a time not to laugh, and this is not one of them.
5 REPLIES 5
Michael Kelly_5
Valued Contributor

Re: syslog.log

This almost certainly means that the inetd daemon is trying to bind to the bootp port but some other process has already opened it.
If you have lsof installed you can use it to find the process.

HTH,
Michael.
The nice thing about computers is that they do exactly what you tell them. The problem with computers is that they do EXACTLY what you tell them.
Steve Steel
Honored Contributor

Re: syslog.log

Hi

Try

a:Comment out the bootp entry in inetd.conf
b:inetd -c
c:Then kill the bootpd that is running
d:inetd -c
e:Reverse the first step and remove the comment on the bootp entry in inetd.conf
f:inetd -c

Look for the latest patch

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Jerome Baron
Respected Contributor

Re: syslog.log

Hi,

If inetd was killed with a -k option while bootpd was running, this
is the result. Inetd will start a bootpd process on demand and that
process will service new bootpd requests for a set period of time
before it exits due to no more bootp requests. This causes the
UDP port for bootpd to be held "open" by the running bootpd process,
even after you have killed the inetd process with the "inetd -k".
If you kill running bootpd, then run #inetd -c, it should stop.

Regards,
Jerome
Zigor Buruaga
Esteemed Contributor

Re: syslog.log

Hi,

Check with "netstat -a" if bootps port is being used, and who is using it, probably another instance of the same program.
Kill the daemon and restart "inetd -c".

Hope this helps.

Regards,
Zigor
Steven E. Protter
Exalted Contributor

Re: syslog.log

Might be an address being served by bind and bootps.

The bootps service lets you boot other boxes off your system into Ignite Disaster Recovery and lets you push or pull Ignite images.

You might try /opt/ignite/bin/ignite and reconfigure the IP address assigned to the process.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com