Solved

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

Posted on 2004-10-22
824 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
Question by:juli_ann
    5 Comments
     
    LVL 38

    Expert Comment

    by:wesly_chen
    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
    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:
    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
    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
    ... 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

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Let’s list some of the technologies that enable smooth teleworking. 
    If your business is like most, chances are you still need to maintain a fax infrastructure for your staff. It’s hard to believe that a communication technology that was thriving in the mid-80s could still be an essential part of your team’s modern I…
    Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
    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…

    846 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

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now