DHCP, worked with 2.6 but won't work with Solaris 8!

DHCP, worked with 2.6 but won't work with Solaris 8!

Post by Gregory Gul » Thu, 30 Nov 2000 14:04:21



I just upgraded an Ultra AXi based server from Solaris 2.6 to Solaris 8.
Almost everything went very well and the upgrade was well worth the effort
but for some I can't get DHCP to work!

I copied over my known working configuration files from 2.6 and when
I go to try to run the in.dhcpd program I get the following:

Nov 28 22:59:12 server in.dhcpd[22295]: Error binding to UDP receive socket: Address already in use
Nov 28 22:59:12 server in.dhcpd[22295]: Cannot configure any interfaces.

Netstat does show that port 67 is in use but I can't figure out what it
could be:

      *.67                                  Idle

I did check but there isn't a bootpd running.  I even tried rebooting
but I get the exact same error during the automatic starting of
in.dhcpd as well.

--
Gregory Gulik                        NEW!  http://www.drivingevents.com/

 
 
 

DHCP, worked with 2.6 but won't work with Solaris 8!

Post by Dave Mine » Thu, 30 Nov 2000 04:00:00




...
Quote:> Nov 28 22:59:12 server in.dhcpd[22295]: Error binding to UDP receive

socket: Address already in use

Quote:> Nov 28 22:59:12 server in.dhcpd[22295]: Cannot configure any
interfaces.

> Netstat does show that port 67 is in use but I can't figure out what
it
> could be:

>       *.67                                  Idle

> I did check but there isn't a bootpd running.  I even tried rebooting
> but I get the exact same error during the automatic starting of
> in.dhcpd as well.

The "pfiles" command will show you the open fd's (including sockets) for
a process; the following script will narrow it down:

pgrep -U 0|while read p ; do
echo pid $p
pfiles $p|grep port
done

Dave

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

DHCP, worked with 2.6 but won't work with Solaris 8!

Post by Darren Dunha » Thu, 30 Nov 2000 04:00:00



> Netstat does show that port 67 is in use but I can't figure out what it
> could be:
>       *.67                                  Idle
> I did check but there isn't a bootpd running.  I even tried rebooting
> but I get the exact same error during the automatic starting of
> in.dhcpd as well.

Double check your inetd.conf file.  BootP can be run out of there.  If
inetd has it in the conf file, it will listen on the port.

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
      < Please move on, ...nothing to see here,  please disperse >