bind address already in use error every 10 min. in syslog

[Brad Marks]

I'm running HP-UX 10.20 on a K420 and also use a printspooler called EasySpool.

After booting, the error "printer/tcp: bind: Address already in use" appears in syslog every 10 minutes.
I found a document on the HP website that stated the following:

"You are getting this error because the lpsNet process is holding the port. lpsNet is a third-party software made by EasySpool. The lpsNet program is overriding rlpdaemon. Use these steps to resolve the problem:
1.Kill lpsNet process.
2.Restart inetd with the 'indtd -k' command."

Winds up I also needed to use the 'inetd' command to restart what the -k killed.

After trying this, the syslog error changed a bit. Now it says: bootps/udp: bind: Address already in use.

Two questions:
1. How can I get rid of this error message?
2. What can I do to prevent this from happening again after next boot?

Thanks, thanks, thanks!

[Rick Garland]

Can you change the port that EasySpool is using?
If so, find the entry in the /etc/services file, make the modification, and then do inetd -c to reread the inetd configuration.

[Brad Marks]

I can't seem to find an entry in /etc/services for lpsNet or EasySpool and will, therefore, contact EasySpool for assistance. Thanks for your help!

[Shannon Petry]

Address already in use means that someone on your network has the same IP address as the K. Best to check this with arp -a on a few seats, and grep out the K box's IP address. If you see multiple MAC's assigned that IP, then find that MAC and kill it! LOL
It sounds easier that it reads. The only way a MAC would be present is if machines were already talking (unless you use static ARP tables that is).
Best bet would be look at multiple networks. I.E. PC net versus UNIX net.
If the server is running BIND, it may also have a problem in one of it's databases, which cause this error, but I have the feeling that this is a not a name server.

IF the problem were in services, the error would say something like unknown socket error, or something I would think.
.

Best Regards,
Shannon

[Brad Marks]

Shannon,
I don't think that the address refers to an ip address; more like a port address. I've contacted the software mfg. and, hopefully, they will be able to point me in the right direction.
Thanks, though.

[Denver Osborn]

Could it be that Easyspool is attempting to create it's own service useing the port that is already established by /etc/services file.

Have you tried commenting the rlp entries out of /etc/services and /etc/inetd.conf if any and reread changes with inetd -c

[Brad Marks]

Denver,
I found and commented out an rlp entry in /etc/inetd.conf, did an inetd -c....
and the same thing: "bootps/udp: bind: Address already in use". I even did an inetd -k followed by inetd; to no avail.

The software mfg. says that EasySpool is going after port 515, but I find no entry for that port in /etc/services. I've also made sure that EasySpool is the very last startup script executed at boot time.

I appreciate you help and will couple it with expected further comments from the mfg.

I'd also award you some points, but ITRC is not asking me to!?!?

[Rita C Workman]

So if I understand correctly...your problem is that this is filling up your syslog and it is annoying when you have to read your syslog???
Why don't you just try removing it from your log before you read it (or at scheduled times...) when it would not hurt to fix your syslog. I get msgs every 2 min because I turned on the inetd log for telnet and ftp....registrar/tcp stuff. It's just a nuisance, but I clean it up early in the am..with a overly simple script
**********************
cat syslog.log | grep -v -e 'what I don't want to see' -e 'the other msgs I don't care about' > syslog.tmp
cp syslog.tmp syslog.log
rm syslog.tmp
****************************
I am very specific about what goes inside the quotes...cause I don't want to lose info I need to see.
Some folks may prefer to leave the syslog in tact and just read the tmp file....
But this will remove the info you don't want to read ... and just leave what you do want to see..
Just a thought,

[Denver Osborn]

you're sure 515 is not in /etc/services? Maybe try adding it and then inetd -c

printer 515/tcp spooler

[Brad Marks]

Rita,
You're kinda right; I don't like having to sift through unwanted stuff in syslog. However, I'm probably too anal but I see this as something that is wrong and want it right. I, myself, turned off ftp logging (we have an every-ten-seconds auto-ftp process that REALLY filled syslog). Thanks for the script; I just might bite the bullet and use it.

Denver,
I'm certain that there isn't a 515 in services, so I'll try your suggestion and post the results.

Thanks all!

[Anthony deRito · Accepted solution]

Try inetd -k again but this time make sure bootpd is not running. It comes alive every so often so make sure it is actaully not running.

Tony

[Brad Marks]

Anthony,
Are you suggesting that I kill the process if it is running (which it is)?

[Anthony deRito]

Yes, shut it down for a few seconds and then try your inetd -k. Your bootp clients will not be able to aquire an IP but hey, your the sysadmin!!

Don't be concerned about starting it. You won't be able to on the command line or with inetd -c. When a client makes a request, it will come alive.

Tony

[Brad Marks]

Tony et al.,
This did the trick: 30 minutes without a warning.
The big question now is, how do I prevent this from happening after rebooting the box?

Thanx 2 all

[Berlene Herren]

Kill bootpd and run inetd -c. Issuing inetd -k while bootpd was running probably is what started it.

Berlene