Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

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

Posted on 2004-10-22
5
Medium Priority
?
855 Views
Last Modified: 2013-12-23
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
Comment
Question by:juli_ann
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 38

Expert Comment

by:wesly_chen
ID: 12386091
Can you post the result of "ifconfig -a"?
Besides, can you ping other machines after the Gigi card installation?

Wesly
0
 

Author Comment

by:juli_ann
ID: 12391653
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
 
LVL 38

Accepted Solution

by:
wesly_chen earned 2000 total points
ID: 12391744
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
 

Author Comment

by:juli_ann
ID: 12401558
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
 

Author Comment

by:juli_ann
ID: 12401647
... 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

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses

618 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question