Link to home
Start Free TrialLog in
Avatar of juli_ann
juli_ann

asked on

Getting error message: inetd[626]: [ID 667328 daemon.error] bootps/udp server failing (looping), service terminated

Any idea as to what is causing this error message (sent to root):

 inetd[626]: [ID 667328 daemon.error] bootps/udp server failing (looping), service terminated


We are running Solaris 9, with Samba shares to Windows 2000 servers.  Two days ago we upgraded the Sun 280R's with gig ethernet cards.  These three 280R's are in a Veritas cluster, and each machine is sending the same error message to root.  

Thanks for your help! Let me know if you need any other information.  
Avatar of wesly_chen
wesly_chen
Flag of United States of America image
Can you post the result of "ifconfig -a"?
Besides, can you ping other machines after the Gigi card installation?

Wesly
Avatar of juli_ann
juli_ann

ASKER

It looks like I can ping every machine.  Here is ifconfig -a for each machine.   Sun #3 is not sending this error message to root.  Please let me know if you need any other info :)


Sun #1
Last login: Sun Oct 24 01:03:49 2004 from bc010.ici.org
Sun Microsystems Inc.   SunOS 5.9       Generic May 2002
root@core1:/> ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.2.67 netmask ffff0000 broadcast 172.16.255.255
        ether 0:3:ba:16:b0:20
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.30 netmask ffff0000 broadcast 172.16.255.255
ce0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.13 netmask ffff0000 broadcast 172.16.255.255

Sun #2
root@core2:/> ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.2.68 netmask ffff0000 broadcast 172.16.255.255
        ether 0:3:ba:2:ae:47
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.24 netmask ffff0000 broadcast 172.16.255.255
ce0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.58 netmask ffff0000 broadcast 172.16.255.255
ce0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.67 netmask ffff0000 broadcast 172.16.255.255
ce0:4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.60 netmask ffff0000 broadcast 172.16.255.255
ce0:5: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.61 netmask ffff0000 broadcast 172.16.255.255
ce0:6: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.59 netmask ffff0000 broadcast 172.16.255.255
ce0:7: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.56 netmask ffff0000 broadcast 172.16.255.255


Sun #3 -- No error messages are coming from this machine (core3)

root@core3:/> ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.2.69 netmask ffff0000 broadcast 172.16.255.255
        ether 0:3:ba:14:9b:e1
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.2.71 netmask ffff0000 broadcast 172.16.255.255
ce0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.10 netmask ffff0000 broadcast 172.16.255.255
ce0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.51 netmask ffff0000 broadcast 172.16.255.255
ce0:4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.63 netmask ffff0000 broadcast 172.16.255.255

Sun #4
root@core4:/> ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.2.70 netmask ffff0000 broadcast 172.16.255.255
        ether 0:3:ba:12:f0:59
ce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 172.16.1.57 netmask ffff0000 broadcast 172.16.255.255
root@core4:/> ping core1
core1 is alive





ASKER CERTIFIED SOLUTION
Avatar of wesly_chen
wesly_chen
Flag of United States of America image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of juli_ann
juli_ann

ASKER

Yes- we are using DHCP :o)  I "commented out" the bootps line in the inetd.conf file,  and restarted inetd.  Now- no more error messages, and everything runs fine!  Awesome!!  Thank you so much!

Avatar of juli_ann
juli_ann

ASKER

... we are using a separate DHCP server, not those particular Sun's for DHCP, so it didn't need to be running :)  

I found out today that one of our sysadmins added a jetdirect printing package to our servers that unknowingly added that line to our inetd.conf file, but isn't necessary for our printing set up, so it can stay disabled.

Thanks Again!