Results 1 to 9 of 9
  1. #1
    Join Date
    Nov 2004
    Location
    Switzerland
    Posts
    855

    init: Id "wd" respawning too fast: disabled for 5 minutes

    Hi

    I have got this error on the /var/log/messages:


    Sep 13 22:57:55 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:02:56 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:07:57 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:12:58 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:17:59 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:23:00 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:28:01 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:33:02 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:38:03 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes
    Sep 13 23:43:04 IPDMFG0043MIA init: Id "wd" respawning too fast: disabled for 5 minutes


    Any idea?
    .:. Enterprise SAN Consultant .:.

  2. #2
    Join Date
    Nov 2004
    Location
    Switzerland
    Posts
    855
    Looks as a watchdog issue. If you have got any info to share....
    .:. Enterprise SAN Consultant .:.

  3. #3
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,290
    what kernel?
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

  4. #4
    Join Date
    Oct 2002
    Location
    Canada
    Posts
    3,100
    Posting distro name and version would help. Can you post your /ect/inittab too. It looks like something set to respawn is not able to start up for some reason so it keeps trying.

  5. #5
    Join Date
    Nov 2004
    Location
    Switzerland
    Posts
    855
    The server crashed. When it is online again, I willl post the resquested info. Thank you for your concern.
    .:. Enterprise SAN Consultant .:.

  6. #6
    Join Date
    Nov 2004
    Location
    Switzerland
    Posts
    855
    The Kernel:

    2.6.8-022stab078.10-enterprise #1 SMP Wed Jun 21 12:20:51 MSD 2006 i686 athlon i38

    The hardware:

    4 Opteron 265 Cores
    8 Gb RAM
    Hardware RAID1 - SATA

    /etc/inittab


    #
    # inittab This file describes how the INIT process should set up
    # the system in a certain run-level.
    #
    # Author: Miquel van Smoorenburg, <[email protected]>
    # Modified for RHS Linux by Marc Ewing and Donnie Barnes
    #

    # Default runlevel. The runlevels used by RHS are:
    # 0 - halt (Do NOT set initdefault to this)
    # 1 - Single user mode
    # 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
    # 3 - Full multiuser mode
    # 4 - unused
    # 5 - X11
    # 6 - reboot (Do NOT set initdefault to this)
    #
    id:3:initdefault:

    # System initialization.
    si::sysinit:/etc/rc.d/rc.sysinit

    l0:0:wait:/etc/rc.d/rc 0
    l1:1:wait:/etc/rc.d/rc 1
    l2:2:wait:/etc/rc.d/rc 2
    l3:3:wait:/etc/rc.d/rc 3
    l4:4:wait:/etc/rc.d/rc 4
    l5:5:wait:/etc/rc.d/rc 5
    l6:6:wait:/etc/rc.d/rc 6

    # Trap CTRL-ALT-DELETE
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now

    # When our UPS tells us power has failed, assume we have a few minutes
    # of power left. Schedule a shutdown for 2 minutes from now.
    # This does, of course, assume you have powerd installed and your
    # UPS connected and working correctly.
    pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

    # If power was restored before the shutdown kicked in, cancel it.
    pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"

    # Run gettys in standard runlevels
    1:2345:respawn:/sbin/mingetty tty1
    2:2345:respawn:/sbin/mingetty tty2
    S0:12345:respawn:/sbin/mgetty ttyS0 -s 9600 -r
    #3:2345:respawn:/sbin/mingetty tty3
    #4:2345:respawn:/sbin/mingetty tty4
    #5:2345:respawn:/sbin/mingetty tty5
    #6:2345:respawn:/sbin/mingetty tty6

    # Run xdm in runlevel 5
    #x:5:respawn:/etc/X11/prefdm -nodaemon
    #wd:23:respawn:/usr/sbin/watchdog
    .:. Enterprise SAN Consultant .:.

  7. #7
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,290
    #wd:23:respawn:/usr/sbin/watchdog

    i notice thats commented out.
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

  8. #8
    Join Date
    Nov 2004
    Location
    Switzerland
    Posts
    855
    Yes, it was just commented out. I have been said that this Kernel has no support for watchdog and this was causing the problem.
    .:. Enterprise SAN Consultant .:.

  9. #9
    Join Date
    Mar 2003
    Location
    California USA
    Posts
    13,290
    Thats probably the case.
    Steven Ciaburri | Industry's Best Server Management - Rack911.com
    Software Auditing - 400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com
    Fully Managed Dedicated Servers (Las Vegas, New York City, & Amsterdam) (AS62710)
    FreeBSD & Linux Server Management, Security Auditing, Server Optimization, PCI Compliance

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •