'some logger thread(s) are stuck' crash...?

From: Alex J. Avriette (alex_at_posixnap.net)
Date: 11/29/03

  • Next message: Gowda, Sanjay: "Solaris 8 - Oracle - Apps - softunlock ... What is it?"
    Date: Sat, 29 Nov 2003 16:19:35 -0500
    To: sunmanagers@sunmanagers.org
    
    

    I got the following email while I was out of town this weekend:

    ##

    >From root@nectarine.posixnap.net
    Date: Tue, 18 Nov 2003 03:20:08 -0500 (EST)
    From: Super-User <root@nectarine.posixnap.net>
    Message-Id: <200311180820.hAI8K8f2004556@nectarine.posixnap.net>
    To: root@nectarine.posixnap.net
    Subject: syslogd shut down Content-Length: 103

    syslogd(nectarine): some logger thread(s) are stuck (including the
    console); +syslogd is shutting down.

    ##

    Nectarine is my nameserver, and it irks me that it went down. When
    I came back, it was nonresponsive on the network, and not responsive
    on the console. Sending it a break woke it up, but only to an 'ok'
    prompt. When I then fed it 'go', it resumed being hosed. A reboot
    seems to have cured the machine, but I really hate to just issue
    The Microsoft Procedure without understanding what really went wrong
    with it.

    Any insight here would be much appreciated, and of course I'll
    summarize. Hope you all had a happy holiday.

    Alex

    --
    alex@posixnap.net
    Alex J. Avriette, Solaris Artillery Officer
    "Among the many misdeeds of the British rule in India, history will look upon the act of depriving a whole nation of arms, as the blackest." - Mahatma Gandhi
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    

  • Next message: Gowda, Sanjay: "Solaris 8 - Oracle - Apps - softunlock ... What is it?"

    Relevant Pages

    • Stopping "Link down - cable problem?" Messages
      ... messages only going to the console and not /var/adm/messages? ... If I run syslogdin debug mode, I see the output (heavily edited for ... all "kern" messages should be logged. ... syslogd: version 1.99 ...
      (SunManagers)
    • Re: serial console oddity
      ... >> see syslogd output to the console get corrupted. ... >> syslogd writes seems to get truncated or otherwise corrupted. ... > This is a longstanding bug in ttymsg(). ... > last close of the console affects the underlying tty. ...
      (freebsd-current)
    • serial console oddity
      ... output to the console and userland writes to /dev/console. ... syslogd writes seems to get truncated or otherwise corrupted. ... the first character of the month, or sometimes just a space, or ... When the syslogd output is being corrupted, I can cat a file to ...
      (freebsd-current)
    • Re: how do I suppress system messages?
      ... > System messages print out to the console on tty0 only, ... Simply put a # in front, save the file, and restart syslogd by doing ...
      (freebsd-questions)
    • Re: syslogd logs to console, syslog.conf has no /dev/console entries
      ... This behavior stops ... each time I make a change I restart syslogd and send it ... HUP using kill but each time the console still gets warning messages ... Weird - the first thing that comes to mind would be that Postfix ...
      (comp.unix.bsd.freebsd.misc)