Re: Fileserver (Samba) überlastet?

Matthias Teege schrieb:
> On Sun, Jan 26, 2003 at 11:18:59AM +0100, Jens Mantel wrote:
>
>>Hallo Liste,
>
> Moin,
>

Hallo,

>
> Was steht denn in den Logdateien von Samba?
>

log.nmbd:
[2003/01/13 03:02:18, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/14 03:02:19, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/15 03:02:20, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/20 03:02:17, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/20 15:59:56, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/21 03:02:17, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/22 03:02:17, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/23 03:02:18, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/24 03:02:19, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/25 03:02:19, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/26 03:02:18, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...
[2003/01/27 03:02:19, 0] nmbd/nmbd.c:sig_term(65)
   Got SIGTERM: going down...

log.pc015 (User, bei dem es das Problem gibt):
[2002/10/24 14:08:27, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Operation timed out
[2002/11/14 14:34:04, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Connection reset by peer
[2002/11/28 18:03:08, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Operation timed out
[2003/01/03 11:43:17, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Connection reset by peer
[2003/01/06 10:49:44, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Operation timed out
[2003/01/16 10:12:07, 0] lib/util_sock.c:read_socket_with_timeout(303)
   read_socket_with_timeout: timeout read. read error = Connection reset
by peer.
[2003/01/16 10:12:07, 0] smbd/oplock.c:oplock_break(766)
   oplock_break: receive_smb error (Connection reset by peer)
   oplock_break failed for file Standard/vogtdabo.dbf (dev = 27405,
inode = 270088).
[2003/01/16 10:12:07, 0] smbd/oplock.c:oplock_break(854)
   oplock_break: client failure in break - shutting down this smbd.
[2003/01/17 11:31:52, 0] smbd/dir.c:dptr_close(280)
   Invalid key 256 given to dptr_close

log.smbd:
[2003/01/01 12:35:34, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Connection reset by peer
[2003/01/01 12:35:34, 0] smbd/connection.c:yield_connection(62)
   yield_connection: tdb_delete failed with error Record does not exist.
[2003/01/03 14:50:42, 0] lib/util_sock.c:read_socket_data(481)
   read_socket_data: recv failure for 4. Error = Connection reset by peer
[2003/01/03 14:50:42, 0] smbd/connection.c:yield_connection(62)
   yield_connection: tdb_delete failed with error Record does not exist.
[2003/01/06 10:39:42, 0] lib/util_sock.c:receive_smb(665)
   Invalid packet length! (95264 bytes).
[2003/01/06 10:39:42, 0] smbd/connection.c:yield_connection(62)
   yield_connection: tdb_delete failed with error Record does not exist.
[2003/01/17 10:30:44, 0] locking/locking.c:delete_fn(255)
   locking : delete_fn. LOGIC ERROR ! Entry for pid 4876 and it no
longer exists !

>
>>Switch und Netzwerk-Karte sind beide auf 100baseTX und half-duplex
>>eingestellt. Am Switch werden mir keine Fehler angezeigt.
>
>
> Gibt es dafür einen Grund?
>

Ich hatte am Anfang die Netzwerkkarte und den Switch auf automatische
Erkennung. Da mir der Switch Rx Errors angezeigt hat, habe ich auf die
"schnelle" half-duplex eingestellt.

Ich will noch hinzufügen, dass das Problem bei Win95c, Win98SE und
Win2000 aufgetreten ist.

Außerdem ist es heute früh (Nutzer meint gegen 7.00 Uhr) wieder passiert.

Jens

To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Mon 27 Jan 2003 - 11:56:22 CET