Hard Lock

Tue Jan 10 22:15:03 GMT 2006

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Once again one of my mailscanner systems locked up.  I had quite a scare
with this one, and I am sure I will be in during the weekend building
another system for when this one kills over.  This time I had to take out
the RAM and replug the HDs in order to it to get a sense of itself, but I
am wondering if it has something to do with the powerleaps we have in the
Dell Optiplex G1s.  Could they be overheating and causing the lockups? 
If this is possible that would explain why it booted after I messed with
the other hardware.  But this is what I retried from the
/var/log/messages.  Better information, but not something I understand. 
Can you make sense of it??

---------------------------

 Jan 10 13:05:03 wks-lin9 crond(pam_unix)[11999]: session closed for user root
Jan 10 13:05:15 wks-lin9 crond(pam_unix)[12000]: session closed for user root
Jan 10 13:05:22 wks-lin9 crond(pam_unix)[11473]: session closed for user root
Jan 10 13:06:49 wks-lin9 smbd[12451]: [2006/01/10 13:06:49, 0] lib/util_sock.c:get_peer_addr(1000) 
Jan 10 13:06:49 wks-lin9 smbd[12451]:   getpeername failed. Error was Transport endpoint is not connected 
Jan 10 13:06:49 wks-lin9 smbd[12451]: [2006/01/10 13:06:49, 0] lib/util_sock.c:get_peer_addr(1000) 
Jan 10 13:06:49 wks-lin9 smbd[12451]:   getpeername failed. Error was Transport endpoint is not connected 
Jan 10 13:06:49 wks-lin9 smbd[12451]: [2006/01/10 13:06:49, 0] lib/util_sock.c:write_socket_data(430) 
Jan 10 13:06:49 wks-lin9 smbd[12451]:   write_socket_data: write failure. Error = Connection reset by peer 
Jan 10 13:06:49 wks-lin9 smbd[12451]: [2006/01/10 13:06:49, 0] lib/util_sock.c:write_socket(455) 
Jan 10 13:06:49 wks-lin9 smbd[12451]:   write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer 
Jan 10 13:06:49 wks-lin9 smbd[12451]: [2006/01/10 13:06:49, 0] lib/util_sock.c:send_smb(647) 
Jan 10 13:06:49 wks-lin9 smbd[12451]:   Error writing 4 bytes to client. -1. (Connection reset by peer) 
Jan 10 13:06:50 wks-lin9 winbindd[2518]: [2006/01/10 13:06:50, 0] tdb/tdbutil.c:tdb_log(725) 
Jan 10 13:06:50 wks-lin9 winbindd[2518]:   tdb(/var/cache/samba/netsamlogon_cache.tdb): rec_free_read bad magic 0x42424242 at offset=7252 
-------------------
that is the last information posted to messages before the boot up information is written.

On 1/9/06, Information Services <lbcadmin at gmail.com> wrote:
      I am going to check into the HDs.  All three systems have the
      exact same HDs in them.  All the same sw is running on them
      also, except for squid on the two mailscanner boxes.  I will
      also try the suggestions posted in a previous reply to this
      also.  I definitely need to resolve this issue.  I don't want
      my production systems to be locking up, especially not at
      0200 hours.

      On 1/7/06, Glenn Steen <glenn.steen at gmail.com > wrote:
            On 06/01/06, Information Services
            <lbcadmin at gmail.com> wrote:
            (snip)
            >  clamav-0.87

            Update cöam asap.
            (snip)
            >
            >  First,
            >
            >  When I reboot the systems, it takes about 20
            minutes before the login
            > screen appears. I am able to shell into the
            systems themselves and work on
            > them, but I would like to resolve why they
            don't bring the login screen up
            > right away after the boot process. The GUI
            either sets at the blank screen
            > with the black curser outlined in white and is
            an 'X' symbol, or at the
            > progress bar at 100 percent until it finally
            shows the login screen.

            Assuming you are referring to a graphical logon
            screen, this is
            usually a display manager for X.... Which in turn
            usually means that
            extreme slowness is due to a network
            misconfiguration. Having no valid
            name lookup (in /etc/hosts) for the loopback IF
            address usually has
            this effect... So check that all names (including
            loopback) resolve as
            they should. If you have it configured for a X
            font sever, check that
            it is running, and that you have no network
            issues in reaching it.

            >
            >  Issue 2:
            >
            >  I have been havin problems with both servers
            locking up. One server more
            > than the other.
            >
            (snip)
            Nothing jumps out and grabs ones attention.... So
            suspect the usual
            things: HW and kernel. One is easy to change....
            so why not try your
            hand on doing a "custom kernel";-). since both
            machines are more or
            less of an age, and fairly similar in makeup.....
            shoddy drivers come
            to mind, as well as diverse age-related cr*p.

            --
            -- Glenn
            email: glenn < dot > steen < at > gmail < dot >
            com
            work: glenn < dot > steen < at > ap1 < dot > se

            ------------------------ MailScanner list
            ------------------------
            To unsubscribe, email jiscmail at jiscmail.ac.uk
            with the words:
            'leave mailscanner' in the body of the email.
            Before posting, read the Wiki
            (http://wiki.mailscanner.info/) and
            the archives (
            http://www.jiscmail.ac.uk/lists/mailscanner.html
            ).

            Support MailScanner development - buy the book
            off the website!

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/)
and the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!