[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 869
  • Last Modified:

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.  
0
juli_ann
Asked:
juli_ann
  • 3
  • 2
1 Solution
 
wesly_chenCommented:
Can you post the result of "ifconfig -a"?
Besides, can you ping other machines after the Gigi card installation?

Wesly
0
 
juli_annAuthor Commented:
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





0
 
wesly_chenCommented:
By the way, do you need DHCP server on those machines? "bootps" is for DHCP server.
If not, just comment out the following line from /etc/inetd.conf :
------
bootps dgram udp wait root /usr/sbin/bootpd bootpd
------
And then restart the inetd.

If yes, then double check the syntax of /etc/bootptab, /etc/services and /etc/inetd.conf.
Check the permission of /etc/bootptab. Try setting it to a 644 authority

Make sure as the following entries are in /etc/services:
----------
bootps          67/udp                          # BOOTP/DHCP server
bootpc          68/udp                          # BOOTP/DHCP client

Wesly
0
 
juli_annAuthor Commented:
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!

0
 
juli_annAuthor Commented:
... 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!

0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now