1834395 Members
1834 Online
110066 Solutions
New Discussion

inetd

 
SOLVED
Go to solution
DD-CC
Occasional Advisor

inetd

I'm running hpux 10.20 where I just installed the network backup part of HPUX Ignite
This added entries into /etc/inetd.conf:
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

The syslog.log file now reports:
inetd[458]: Rereading configuration
inetd[458]: tftp/udp: New arguments for server /usr/lbin/tftpd
inetd[458]: instl_boots/udp: bind: Address already in use
inetd[458]: instl_boots/udp: Added service, server /opt/ignite/lbin/instl_bootd
inetd[458]: Configuration complete

I checked the contest of /etc/services:
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
instl_boots 1067/udp # installation bootstrap protocol server
instl_bootc 1068/udp # installation bootstrap protocol client


I have tried to restart inetd without solving my problem. I've been looking for an other service witch uses the same port but without success.

Any suggestions ???


S?ren
When all you've got is a nailgun, every problem looks like a Messiah...
5 REPLIES 5
Kofi ARTHIABAH
Honored Contributor

Re: inetd

Soren:

you might want to check out this thread:

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0xd88bc3d7fb78d4118fef0090279cd0f9,00.html

The problem arises from the file /etc/opt/ignite/instl_boottab which contains the list of IP and mac addresses - you might have an entry in there that is already being used. examine the file and ensure that the addresses listed in there are not allocated to any machines.

Good luck
PS. Do a man on instl_bootd
nothing wrong with me that a few lines of code cannot fix!
Alex Glennie
Honored Contributor
Solution

Re: inetd

DocId:
KBRC00000431

Updated:
1/4/00 12:24:12 PM


PROBLEM

/var/adm/syslog/syslog.log repeats the following message:
[host_name] inetd: instl_boots/udp: bind: Address already in use.


RESOLUTION

This problem usually occurs when the kernel fails to release the open socket
that?s used for communication between rbootd and instl_bootd. Killing the 2
daemons and inetd has not been known to resolve the problem.

The only solution is to reboot the system.
DD-CC
Occasional Advisor

Re: inetd

Thanks for the answer

Rebooting tmy server solved the problem.

S?ren
When all you've got is a nailgun, every problem looks like a Messiah...
Damian O'Hara_1
Advisor

Re: inetd

All,

i had the same problem and followed the advice given in this forum.

Here's what happened ...

C180 workstation unable to "boot lan install" to ignite server.

Error in ignite:/var/adm/syslog/syslog.log showed:

instl_boots/udp: bind: Address already in use

Hp website suggested rebooting server. Rebooted server but no fix!

Emptied all client MAC addresses from file /etc/opt/ignite/instl_bootd and rebooted server. Still no fix.
Noticed that some (now obsolete) clients were still showing active build status in the ignite gui. Cleared these errors so that all clients show "Complete" and rebooted server.

Client now boots successfully.
harry d brown jr
Honored Contributor

Re: inetd

Get a copy of lsof :

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.61/


live free or die
harry
Live Free or Die