Comment 2 for bug 216358

It did persist, but as there seemed to be something wrong in the OS altogether, I gave it a reboot and after that the problem has not occurred, at least not yet.

The log does not seem to reveal much of anything:

[2008/04/10 19:56:43, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/10 20:28:43, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/10 21:00:43, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/10 21:32:43, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/10 23:40:43, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/12 15:48:17, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/12 18:56:21, 0] smbd/server.c:main(944)
  smbd version 3.0.28a started.
  Copyright Andrew Tridgell and the Samba Team 1992-2008
[2008/04/12 18:56:21, 1] param/loadparm.c:lp_do_parameter(3541)
  WARNING: The "printer admin" option is deprecated
[2008/04/12 19:00:39, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected
[2008/04/12 23:16:39, 0] lib/util_sock.c:get_peer_addr(1232)
  getpeername failed. Error was Transport endpoint is not connected

I am almost ready to blame this for hardware problem now. Before the reboot load was above 9.00, while top still said "99% idle" and showed no process taking up CPU..

But the said hardware (sans the hard drives) has run Windows for two years and memtest for days without any problems, so HW failure is not that likely either.

All in all, if the problem does not come back in few weeks, lets close this bug. I am sorry for the inconvenience.