Samba bricht zusammen

Dieses Thema im Forum "Samba" wurde erstellt von w-d-h-o, 10.03.2008.

  1. #1 w-d-h-o, 10.03.2008
    Zuletzt von einem Moderator bearbeitet: 10.03.2008
    w-d-h-o

    w-d-h-o Grünschnabel

    Dabei seit:
    28.02.2008
    Beiträge:
    4
    Zustimmungen:
    0
    Hallo
    ich hatte Samstag einen sehr unangenemen Zusammenbruch unserer EDV, den ich mir nicht erklären kann.

    Der Linux-Server läuft sehr zuverlässig, wird oft über ein Jahr nicht heruntergefahren. Aber gelegentlich (zum Glück nur selten) bekommt er einen Rappel, dann bricht alles zusammen, weil Samba seine Freigaben sperrt (oplock_break).
    Der Server läuft im produktiven System, ein Zusammenbruch ist daher sehr unangenehm. Vielleicht hat jemand eine Ide wie es zu dem Fehler kommt und wie man ihn abstellen kann.

    Der Fehler fängt langsam an:
    Einige Clients bleiben hängen - zunächts mit einigen offenen Programmen, hängen sich i.d.R. dann aber ganz auf. Andere Clients arbeiten zu der Zeit noch problemlos. Nach und nach weitet sich das Problem aus (ca. 15 Minuten) bis kein Client mehr irgendeine Sambafreigabe erreichen kann.

    Ich habe dann den Server runtergefahren und nach kurzer Pause neu gestartet.
    Nun konnten für kurze Zeit einige Clients arbeiten, bis alles wieder stand.
    Ich habe alle Clients abgeschaltet und mehrfach SMBD neu gestartet.
    Nun (nach einer Stunde Ausfall) läuft alles wieder problemlos.

    Angefangen hat alles anscheinend mit "read_data: read failure for 4. Error = Connection reset by peer". Wieso kann ein Datenfehler das ganze System runterziehen? Es wid kein Festplattenfehler (dev/md0) gemeldet.
    "oplock_break" ist ja normal, aber so gehäuft? Wenn ein Client abschmiert (was bei Windows fast täglich geschieht - ohne Folgen) bleiben oplocks offen. Aber die werden doch nach spätestens 30 Sekunden beendet (keep alive = 30)?!
    Warum hat der Server-Neustart nicht geholfen?
    Kann ich blockierte Freigaben auch einfacher, als mit einem reboot beenden?


    Zu unserem System:
    Wir Nutzen seit 5 Jahren einen SuSe-Linux 8.0 Server (ich weis, nicht ganz aktuell, aber never tuch a running system) mit SAMBA 2.2.3a und pervasive Datenbank für bis zu 15 Windows-Clients (überwigend Win98SE, aber auch win95 und xp [xp lief aber vermutlich zu der Zeit garnicht]).
    Verbunden über Switch mit 10/100 bit
    Der Server nutz Sofware-RAID 1. cat /proc/mdstat und auch das LOG weisen keinerlei Fehler aus.

    Auszug aus smb.conf:
    Code:
    [global]
       workgroup = ABC
       guest account = %U
       keep alive = 30
       os level = 2
       kernel oplocks = false
       security = user
       encrypt passwords = yes
       null passwords = Yes
       min passwd length = 0
       password level = 10
       interfaces = 192.168.101.100/255.255.255.0
    [CD_Copy]
       comment = Kataloge
       path = /home/CD
       read only = no
       locking = no
       browsable = yes
    
    Auszug aus /var/log/messages:
    Code:
    Mar  8 12:31:10 server smbd[6528]: [2008/03/08 12:31:10, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:31:10 server smbd[6528]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:31:32 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:31:32 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:41:20 server smbd[6415]: [2008/03/08 12:41:20, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:41:20 server smbd[6415]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:41:21 server smbd[9417]: [2008/03/08 12:41:21, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:41:21 server smbd[9417]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:41:25 server smbd[19980]: [2008/03/08 12:41:25, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:41:25 server smbd[19980]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:41:28 server smbd[6386]: [2008/03/08 12:41:28, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:41:28 server smbd[6386]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:42:18 server smbd[6496]: [2008/03/08 12:42:18, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:42:18 server smbd[6496]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:43:42 server smbd[22655]: [2008/03/08 12:43:42, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:43:42 server smbd[22655]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:43:42 server smbd[22655]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:43:42 server smbd[22655]: [2008/03/08 12:43:42, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:43:42 server smbd[22655]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:43:47 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:43:47 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:44:12 server smbd[22978]: [2008/03/08 12:44:12, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:44:12 server smbd[22978]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:44:12 server smbd[22978]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:44:12 server smbd[22978]: [2008/03/08 12:44:12, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:44:12 server smbd[22978]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:44:15 server smbd[22362]: [2008/03/08 12:44:15, 0] smbd/oplock.c:oplock_break(788) 
    Mar  8 12:44:15 server smbd[22362]:   oplock_break: no break received from client within 30 seconds. 
    Mar  8 12:44:15 server smbd[22362]:   oplock_break failed for file MAIL/standard/popstate.dat (dev = 901, inode = 29399, file_id = 1). 
    Mar  8 12:44:15 server smbd[22362]: [2008/03/08 12:44:15, 0] smbd/oplock.c:oplock_break(833) 
    Mar  8 12:44:15 server smbd[22362]:   oplock_break: client failure in oplock break in file MAIL/standard/popstate.dat 
    Mar  8 12:44:42 server smbd[23160]: [2008/03/08 12:44:42, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:44:42 server smbd[23160]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:44:42 server smbd[23160]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:44:42 server smbd[23160]: [2008/03/08 12:44:42, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:44:42 server smbd[23160]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:45:18 server smbd[23306]: [2008/03/08 12:45:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:45:18 server smbd[23306]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:45:18 server smbd[23306]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:45:18 server smbd[23306]: [2008/03/08 12:45:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:45:18 server smbd[23306]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:45:48 server smbd[23519]: [2008/03/08 12:45:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:45:48 server smbd[23519]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:45:48 server smbd[23519]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:45:48 server smbd[23519]: [2008/03/08 12:45:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:45:48 server smbd[23519]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:46:18 server smbd[23665]: [2008/03/08 12:46:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:46:18 server smbd[23665]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:46:18 server smbd[23665]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:46:18 server smbd[23665]: [2008/03/08 12:46:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:46:18 server smbd[23665]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:46:48 server smbd[23813]: [2008/03/08 12:46:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:46:48 server smbd[23813]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:46:48 server smbd[23813]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:46:48 server smbd[23813]: [2008/03/08 12:46:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:46:48 server smbd[23813]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:47:18 server smbd[23959]: [2008/03/08 12:47:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:47:18 server smbd[23959]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:47:18 server smbd[23959]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:47:18 server smbd[23959]: [2008/03/08 12:47:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:47:18 server smbd[23959]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:47:48 server smbd[24105]: [2008/03/08 12:47:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:47:48 server smbd[24105]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:47:48 server smbd[24105]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:47:48 server smbd[24105]: [2008/03/08 12:47:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:47:48 server smbd[24105]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:48:04 server smbd[22315]: [2008/03/08 12:48:04, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:48:04 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24105 on port 42477 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:48:09 server smbd[22321]: [2008/03/08 12:48:09, 0] smbd/oplock.c:oplock_break(788) 
    Mar  8 12:48:09 server smbd[22321]:   oplock_break: no break received from client within 30 seconds. 
    Mar  8 12:48:09 server smbd[22321]:   oplock_break failed for file LIBRIWWS/WWS.EXE (dev = 901, inode = 35791, file_id = 4). 
    Mar  8 12:48:09 server smbd[22321]: [2008/03/08 12:48:09, 0] smbd/oplock.c:oplock_break(833) 
    Mar  8 12:48:09 server smbd[22321]:   oplock_break: client failure in oplock break in file LIBRIWWS/WWS.EXE 
    Mar  8 12:48:18 server smbd[24256]: [2008/03/08 12:48:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:48:18 server smbd[24256]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:48:18 server smbd[24256]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:48:18 server smbd[24256]: [2008/03/08 12:48:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:48:18 server smbd[24256]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:48:36 server smbd[22315]: [2008/03/08 12:48:36, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:48:36 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24256 on port 42477 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:48:44 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:48:44 server lpd[736]: connection from 127.0.0.1
    Mar  8 12:48:48 server smbd[24403]: [2008/03/08 12:48:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:48:48 server smbd[24403]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:48:48 server smbd[24403]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:48:48 server smbd[24403]: [2008/03/08 12:48:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:48:48 server smbd[24403]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:48:49 server smbd[24397]: [2008/03/08 12:48:49, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:48:49 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 24256 on port 42477 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:49:08 server smbd[22315]: [2008/03/08 12:49:08, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:49:08 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24403 on port 42480 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:49:18 server smbd[24580]: [2008/03/08 12:49:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:49:18 server smbd[24580]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:49:18 server smbd[24580]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:49:18 server smbd[24580]: [2008/03/08 12:49:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:49:18 server smbd[24580]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:49:21 server smbd[24397]: [2008/03/08 12:49:21, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:49:21 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 24580 on port 42480 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:49:34 server smbd[24646]: [2008/03/08 12:49:34, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:49:34 server smbd[24646]:   request_oplock_break: no response received to oplock break request to pid 24580 on port 42480 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:49:40 server smbd[22315]: [2008/03/08 12:49:40, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:49:40 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24580 on port 42480 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:49:48 server smbd[24727]: [2008/03/08 12:49:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:49:48 server smbd[24727]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:49:48 server smbd[24727]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:49:48 server smbd[24727]: [2008/03/08 12:49:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:49:48 server smbd[24727]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:49:53 server smbd[24397]: [2008/03/08 12:49:53, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:49:53 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 24727 on port 42482 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:06 server smbd[24646]: [2008/03/08 12:50:06, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:06 server smbd[24646]:   request_oplock_break: no response received to oplock break request to pid 24727 on port 42482 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:12 server smbd[22315]: [2008/03/08 12:50:12, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:12 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24727 on port 42482 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:18 server smbd[24877]: [2008/03/08 12:50:18, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:50:18 server smbd[24877]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:50:18 server smbd[24877]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:50:18 server smbd[24877]: [2008/03/08 12:50:18, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:50:18 server smbd[24877]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:50:19 server smbd[24871]: [2008/03/08 12:50:19, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:19 server smbd[24871]:   request_oplock_break: no response received to oplock break request to pid 24727 on port 42482 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:25 server smbd[24397]: [2008/03/08 12:50:25, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:25 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 24877 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:38 server smbd[24646]: [2008/03/08 12:50:38, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:38 server smbd[24646]:   request_oplock_break: no response received to oplock break request to pid 24877 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:44 server smbd[22315]: [2008/03/08 12:50:44, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:44 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 24877 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:48 server smbd[25024]: [2008/03/08 12:50:48, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:50:48 server smbd[25024]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:50:48 server smbd[25024]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:50:48 server smbd[25024]: [2008/03/08 12:50:48, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:50:48 server smbd[25024]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:50:51 server smbd[24871]: [2008/03/08 12:50:51, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:51 server smbd[24871]:   request_oplock_break: no response received to oplock break request to pid 25024 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:50:57 server smbd[24397]: [2008/03/08 12:50:57, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:50:57 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 25024 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:10 server smbd[24646]: [2008/03/08 12:51:10, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:10 server smbd[24646]:   request_oplock_break: no response received to oplock break request to pid 25024 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:16 server smbd[22315]: [2008/03/08 12:51:16, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:16 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 25024 on port 42484 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:21 server smbd[25171]: [2008/03/08 12:51:21, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:51:21 server smbd[25171]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:51:21 server smbd[25171]:   oplock_break failed for file Win-kv/bin/pcbis.exe (dev = 901, inode = 38130, file_id = 1). 
    Mar  8 12:51:21 server smbd[25171]: [2008/03/08 12:51:21, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:51:21 server smbd[25171]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:51:23 server smbd[24871]: [2008/03/08 12:51:23, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:23 server smbd[24871]:   request_oplock_break: no response received to oplock break request to pid 25171 on port 42486 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:29 server smbd[24397]: [2008/03/08 12:51:29, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:29 server smbd[24397]:   request_oplock_break: no response received to oplock break request to pid 25171 on port 42486 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:42 server smbd[24646]: [2008/03/08 12:51:42, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:42 server smbd[24646]:   request_oplock_break: no response received to oplock break request to pid 25171 on port 42486 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:51:48 server smbd[22315]: [2008/03/08 12:51:48, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 12:51:48 server smbd[22315]:   request_oplock_break: no response received to oplock break request to pid 25171 on port 42486 for dev = 901, inode = 38130, file_id = 1 
    Mar  8 12:52:29 server smbd[22362]: [2008/03/08 12:52:29, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:52:29 server smbd[22362]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:52:32 server smbd[22321]: [2008/03/08 12:52:32, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:52:32 server smbd[22321]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:53:29 server smbd[23106]: [2008/03/08 12:53:29, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:53:29 server smbd[23106]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 12:54:50 server smbd[25095]: [2008/03/08 12:54:50, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 12:54:50 server smbd[25095]:   oplock_break: receive_smb error (Success) 
    Mar  8 12:54:50 server smbd[25095]:   oplock_break failed for file LIBRIWWS/WWS.EXE (dev = 901, inode = 35791, file_id = 4). 
    Mar  8 12:54:50 server smbd[25095]: [2008/03/08 12:54:50, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 12:54:50 server smbd[25095]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 12:57:47 server smbd[6522]: [2008/03/08 12:57:47, 0] lib/util_sock.c:read_data(436) 
    Mar  8 12:57:47 server smbd[6522]:   read_data: read failure for 4. Error = No route to host 
    Mar  8 13:00:33 server smbd[26375]: [2008/03/08 13:00:33, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:00:33 server smbd[26375]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:00:33 server smbd[26375]:   oplock_break failed for file Public/BATCH/WWSSESS.BAT (dev = 902, inode = 449, file_id = 2). 
    Mar  8 13:00:33 server smbd[26375]: [2008/03/08 13:00:33, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:00:33 server smbd[26375]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:00:35 server smbd[25692]: [2008/03/08 13:00:35, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 13:00:35 server smbd[25692]:   request_oplock_break: no response received to oplock break request to pid 26375 on port 42488 for dev = 902, inode = 449, file_id = 2 
    Mar  8 13:02:53 server smbd[25692]: [2008/03/08 13:02:53, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:02:53 server smbd[25692]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:02:53 server smbd[25692]:   oplock_break failed for file Public/BATCH/WWSSESS.BAT (dev = 902, inode = 449, file_id = 8). 
    Mar  8 13:02:53 server smbd[25692]: [2008/03/08 13:02:53, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:02:53 server smbd[25692]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:02:55 server smbd[28591]: [2008/03/08 13:02:55, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 13:02:55 server smbd[28591]:   request_oplock_break: no response received to oplock break request to pid 25692 on port 42486 for dev = 902, inode = 449, file_id = 8 
    Mar  8 13:03:14 server smbd[26349]: [2008/03/08 13:03:14, 0] lib/util_sock.c:read_data(436) 
    Mar  8 13:03:14 server smbd[26349]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 13:05:56 server smbd[19411]: [2008/03/08 13:05:56, 0] lib/util_sock.c:read_data(436) 
    Mar  8 13:05:56 server smbd[19411]:   read_data: read failure for 4. Error = Connection reset by peer 
    Mar  8 13:06:08 server mingetty[8800]: tty4: too long login name
    Mar  8 13:06:23 server init: Switching to runlevel: 0
    Mar  8 13:06:31 server kernel: nfsd: last server has exited
    Mar  8 13:06:31 server kernel: nfsd: unexporting all filesystems
    Mar  8 13:06:31 server rpc.mountd: Caught signal 15, un-registering and exiting. 
    Mar  8 13:06:32 server rpc.statd[890]: Caught signal 15, un-registering and exiting.
    Mar  8 13:06:32 server kdm[999]: fatal IO error 104 (Connection reset by peer)
    Mar  8 13:06:33 server nmbd[781]: [2008/03/08 13:06:33, 0] nmbd/nmbd.c:sig_term(63) 
    Mar  8 13:06:34 server nmbd[781]:   Got SIGTERM: going down... 
    Mar  8 13:06:34 server sshd[643]: Received signal 15; terminating.
    Mar  8 13:06:34 server kernel: Kernel logging (proc) stopped.
    Mar  8 13:06:34 server kernel: Kernel log daemon terminating.
    Mar  8 13:06:35 server exiting on signal 15
    Mar  8 13:05:19 server syslogd 1.4.1: restart.
    Mar  8 13:05:20 server insmod: insmod: a module named sg already exists
    Mar  8 13:05:20 server insmod: insmod: insmod char-major-21 failed
    Mar  8 13:05:20 server insmod: insmod: a module named sg already exists
    Mar  8 13:05:20 server insmod: insmod: insmod char-major-21 failed
    Mar  8 13:05:20 server insmod: insmod: a module named st already exists
    Mar  8 13:05:20 server insmod: insmod: insmod char-major-9 failed
    Mar  8 13:05:24 server sshd[643]: Server listening on :: port 22.
    Mar  8 13:05:24 server kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Mar  8 13:05:24 server kernel: Inspecting /boot/System.map-2.4.18-64GB-SMP
    Mar  8 13:05:25 server kernel: Loaded 13537 symbols from /boot/System.map-2.4.18-64GB-SMP.
    Mar  8 13:05:25 server kernel: Symbols match kernel version 2.4.18.
    Mar  8 13:05:25 server kernel: Loaded 476 symbols from 15 modules.
    Mar  8 13:05:25 server kernel: via-rhine.c:v1.10-LK1.1.13  Nov-17-2001  Written by Donald Becker
    Mar  8 13:05:25 server kernel:   [url]http://www.scyld.com/network/via-rhine.html[/url]
    Mar  8 13:05:25 server kernel: PCI: Found IRQ 9 for device 02:0b.0
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 9 with 00:1f.4
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 9 with 02:04.2
    Mar  8 13:05:25 server kernel: eth0: VIA VT6102 Rhine-II at 0xd400, 00:05:5d:de:5b:ea, IRQ 9.
    Mar  8 13:05:25 server kernel: eth0: MII PHY found at address 8, status 0x7829 advertising 01e1 Link 45e1.
    Mar  8 13:05:25 server kernel: eth0: Setting full-duplex based on MII #8 link partner capability of 45e1.
    Mar  8 13:05:25 server kernel: usb.c: registered new driver usbdevfs
    Mar  8 13:05:25 server kernel: usb.c: registered new driver hub
    Mar  8 13:05:25 server kernel: usb-uhci.c: $Revision: 1.275 $ time 14:22:59 Mar 27 2002
    Mar  8 13:05:25 server kernel: usb-uhci.c: High bandwidth mode enabled
    Mar  8 13:05:25 server kernel: PCI: Found IRQ 10 for device 00:1f.2
    Mar  8 13:05:25 server kernel: PCI: Setting latency timer of device 00:1f.2 to 64
    Mar  8 13:05:25 server kernel: usb-uhci.c: USB UHCI at I/O 0x9400, IRQ 10
    Mar  8 13:05:25 server kernel: usb-uhci.c: Detected 2 ports
    Mar  8 13:05:25 server kernel: usb.c: new USB bus registered, assigned bus number 1
    Mar  8 13:05:25 server kernel: hub.c: USB hub found
    Mar  8 13:05:25 server kernel: hub.c: 2 ports detected
    Mar  8 13:05:25 server kernel: PCI: Found IRQ 9 for device 00:1f.4
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 9 with 02:04.2
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 9 with 02:0b.0
    Mar  8 13:05:25 server kernel: PCI: Setting latency timer of device 00:1f.4 to 64
    Mar  8 13:05:25 server kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 9
    Mar  8 13:05:25 server kernel: usb-uhci.c: Detected 2 ports
    Mar  8 13:05:25 server kernel: usb.c: new USB bus registered, assigned bus number 2
    Mar  8 13:05:25 server kernel: hub.c: USB hub found
    Mar  8 13:05:25 server kernel: hub.c: 2 ports detected
    Mar  8 13:05:25 server kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
    Mar  8 13:05:25 server kernel: VFS: Disk change detected on device sr(11,0)
    Mar  8 13:05:25 server kernel: VFS: Disk change detected on device sr(11,0)
    Mar  8 13:05:25 server kernel: isapnp: Scanning for PnP cards...
    Mar  8 13:05:25 server kernel: isapnp: No Plug & Play device found
    Mar  8 13:05:25 server kernel: IPv6 v0.8 for NET4.0
    Mar  8 13:05:25 server kernel: IPv6 over IPv4 tunneling driver
    Mar  8 13:05:25 server kernel: PCI: Found IRQ 12 for device 02:03.0
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 12 with 02:04.0
    Mar  8 13:05:25 server kernel: PCI: Sharing IRQ 12 with 02:0d.0
    Mar  8 13:05:25 server kernel: parport_pc: ITE8875 found (1P)
    Mar  8 13:05:25 server kernel: parport0: PC-style at 0xb000 [PCSPP,TRISTATE,EPP]
    Mar  8 13:05:25 server kernel: parport0: Printer, EPSON LQ-680
    Mar  8 13:05:25 server kernel: parport_pc: ITE 8872 parallel port: io=0xB000
    Mar  8 13:05:25 server kernel: parport1: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
    Mar  8 13:05:25 server kernel: parport1: irq 7 detected
    Mar  8 13:05:25 server kernel: lp0: using parport0 (polling).
    Mar  8 13:05:25 server kernel: lp1: using parport1 (polling).
    Mar  8 13:05:25 server kernel: lp0: compatibility mode
    Mar  8 13:05:26 server kernel: lp0: compatibility mode
    Mar  8 13:05:26 server kernel: lp1: compatibility mode
    Mar  8 13:05:26 server kernel: lp0: compatibility mode
    Mar  8 13:05:28 server rpc.statd[890]: Version 0.3.3 Starting
    Mar  8 13:05:28 server kernel: Installing knfsd (copyright (C) 1996 [email]okir@monad.swb.de[/email]).
    Mar  8 13:05:29 server /usr/sbin/cron[955]: (CRON) STARTUP (fork ok) 
    Mar  8 13:05:31 server nmbd[793]: [2008/03/08 13:05:31, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:05:31 server nmbd[793]:   find_response_record: response packet id 4364 received with no matching record. 
    Mar  8 13:05:31 server nmbd[793]: [2008/03/08 13:05:31, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:05:31 server nmbd[793]:   find_response_record: response packet id 4365 received with no matching record. 
    Mar  8 13:05:33 server /etc/hotplug/net.agent[664]: No HW description found ... exiting
    Mar  8 13:05:34 server su: (to psql) root on /dev/console
    Mar  8 13:05:34 server su: pam_unix2: session started for user psql, service su 
    Mar  8 13:05:34 server mkded: MKDE0095:   MicroKernel Database Engine 7.94.251.003 Copyright (C) Pervasive Software Inc. 2001               All Rights Reserved   
    Mar  8 13:05:34 server mkded: /etc/samba/smb.conf was loaded successfully
    Mar  8 13:05:34 server mkded: Cannot set file handle limit 1024, the current limit is 1024
    Mar  8 13:05:34 server su: pam_unix2: session finished for user psql, service su 
    Mar  8 13:05:34 server su: (to psql) root on /dev/console
    Mar  8 13:05:34 server su: pam_unix2: session started for user psql, service su 
    Mar  8 13:05:34 server su: pam_unix2: session finished for user psql, service su 
    Mar  8 13:05:35 server kernel: eth0: no IPv6 routers present
    Mar  8 13:06:46 server lpd[736]: connection from 127.0.0.1
    Mar  8 13:06:46 server last message repeated 3 times
    Mar  8 13:06:47 server smbd[1125]: [2008/03/08 13:06:47, 0] smbd/service.c:make_connection(249) 
    Mar  8 13:06:47 server smbd[1125]: [2008/03/08 13:06:47, 0] smbd/service.c:make_connection(249) 
    Mar  8 13:06:47 server lpd[736]: connection from 127.0.0.1
    Mar  8 13:11:10 server nmbd[793]: [2008/03/08 13:11:10, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) 
    Mar  8 13:11:10 server nmbd[793]:   ***** 
    Mar  8 13:11:10 server nmbd[793]:    
    Mar  8 13:11:10 server nmbd[793]:   Samba name server XYZ is now a local master browser for workgroup ABC on subnet 192.168.101.100 
    Mar  8 13:11:10 server nmbd[793]:    
    Mar  8 13:11:10 server nmbd[793]:   ***** 
    Mar  8 13:17:35 server smbd[1125]: [2008/03/08 13:17:35, 0] lib/util_sock.c:read_socket_with_timeout(298) 
    Mar  8 13:17:35 server smbd[1125]:   read_socket_with_timeout: timeout read. read error = Connection reset by peer. 
    Mar  8 13:17:35 server smbd[1125]: [2008/03/08 13:17:35, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:17:35 server smbd[1125]:   oplock_break: receive_smb error (Connection reset by peer) 
    Mar  8 13:17:35 server smbd[1125]:   oplock_break failed for file BibWin/bibwin_prog.exe (dev = 901, inode = 29521, file_id = 707). 
    Mar  8 13:17:35 server smbd[1125]: [2008/03/08 13:17:35, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:17:35 server smbd[1125]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:18:07 server smbd[1237]: [2008/03/08 13:18:07, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 13:18:07 server smbd[1237]:   request_oplock_break: no response received to oplock break request to pid 1125 on port 32773 for dev = 901, inode = 29521, file_id = 707 
    Mar  8 13:18:10 server nmbd[793]: [2008/03/08 13:18:10, 0] nmbd/nmbd_incomingdgrams.c:process_local_master_announce(314) 
    Mar  8 13:18:10 server nmbd[793]:   process_local_master_announce: Server WS05 at IP 192.168.101.5 is announcing itself as a local master browser for workgroup ABC and we think we are master. Forcing election. 
    Mar  8 13:18:10 server nmbd[793]: [2008/03/08 13:18:10, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(154) 
    Mar  8 13:18:10 server nmbd[793]:   ***** 
    Mar  8 13:18:10 server nmbd[793]:    
    Mar  8 13:18:10 server nmbd[793]:   Samba name server XYZ has stopped being a local master browser for workgroup ABC on subnet 192.168.101.100 
    Mar  8 13:18:10 server nmbd[793]:    
    Mar  8 13:18:10 server nmbd[793]:   ***** 
    Mar  8 13:18:27 server nmbd[793]: [2008/03/08 13:18:27, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) 
    Mar  8 13:18:27 server nmbd[793]:   ***** 
    Mar  8 13:18:27 server nmbd[793]:    
    Mar  8 13:18:27 server nmbd[793]:   Samba name server XYZ is now a local master browser for workgroup ABC on subnet 192.168.101.100 
    Mar  8 13:18:27 server nmbd[793]:    
    Mar  8 13:18:27 server nmbd[793]:   ***** 
    Mar  8 13:18:37 server smbd[1237]: [2008/03/08 13:18:37, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:18:37 server smbd[1237]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:18:37 server smbd[1237]:   oplock_break failed for file BibWin/bibwin_prog.exe (dev = 901, inode = 29521, file_id = 1). 
    Mar  8 13:18:37 server smbd[1237]: [2008/03/08 13:18:37, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:18:37 server smbd[1237]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:19:07 server smbd[1239]: [2008/03/08 13:19:07, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:19:07 server smbd[1239]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:19:07 server smbd[1239]:   oplock_break failed for file BibWin/bibwin_prog.exe (dev = 901, inode = 29521, file_id = 1). 
    Mar  8 13:19:07 server smbd[1239]: [2008/03/08 13:19:07, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:19:07 server smbd[1239]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:19:39 server smbd[1241]: [2008/03/08 13:19:39, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:19:39 server smbd[1241]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:19:39 server smbd[1241]:   oplock_break failed for file BibWin/bibwin_prog.exe (dev = 901, inode = 29521, file_id = 1). 
    Mar  8 13:19:39 server smbd[1241]: [2008/03/08 13:19:39, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:19:39 server smbd[1241]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:20:08 server nmbd[793]: [2008/03/08 13:20:08, 0] nmbd/nmbd.c:sig_term(63) 
    Mar  8 13:20:08 server nmbd[793]:   Got SIGTERM: going down... 
    Mar  8 13:20:12 server nmbd[1282]: [2008/03/08 13:20:12, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:20:12 server nmbd[1282]:   find_response_record: response packet id 5234 received with no matching record. 
    Mar  8 13:20:12 server nmbd[1282]: [2008/03/08 13:20:12, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:20:12 server nmbd[1282]:   find_response_record: response packet id 5235 received with no matching record. 
    Mar  8 13:20:38 server smbd[1287]: [2008/03/08 13:20:38, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:20:38 server smbd[1287]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:20:38 server smbd[1287]:   oplock_break failed for file BibWin/bibwin_prog.exe (dev = 901, inode = 29521, file_id = 1). 
    Mar  8 13:20:38 server smbd[1287]: [2008/03/08 13:20:38, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:20:38 server smbd[1287]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:21:55 server nmbd[1282]: [2008/03/08 13:21:55, 0] nmbd/nmbd.c:sig_term(63) 
    Mar  8 13:21:55 server nmbd[1282]:   Got SIGTERM: going down... 
    Mar  8 13:21:59 server nmbd[1330]: [2008/03/08 13:21:59, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:21:59 server nmbd[1330]:   find_response_record: response packet id 5289 received with no matching record. 
    Mar  8 13:21:59 server nmbd[1330]: [2008/03/08 13:21:59, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) 
    Mar  8 13:21:59 server nmbd[1330]:   find_response_record: response packet id 5290 received with no matching record. 
    Mar  8 13:22:27 server smbd[1335]: [2008/03/08 13:22:27, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:22:27 server smbd[1335]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:22:27 server smbd[1335]:   oplock_break failed for file LIBRIWWS/WWS.EXE (dev = 901, inode = 35791, file_id = 4). 
    Mar  8 13:22:27 server smbd[1335]: [2008/03/08 13:22:27, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:22:27 server smbd[1335]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:26:52 server smbd[1350]: [2008/03/08 13:26:52, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 13:26:52 server smbd[1350]:   request_oplock_break: no response received to oplock break request to pid 1337 on port 32780 for dev = 901, inode = 3301, file_id = 15 
    Mar  8 13:26:52 server smbd[1350]: [2008/03/08 13:26:52, 0] smbd/open.c:open_mode_check(552) 
    Mar  8 13:26:52 server smbd[1350]:   open_mode_check: exlusive oplock left by process 1337 after break ! For file LIBRICD/LIBRI.3, dev = 901, inode = 3301. Deleting it to continue... 
    Mar  8 13:26:52 server smbd[1350]: [2008/03/08 13:26:52, 0] smbd/open.c:open_mode_check(556) 
    Mar  8 13:26:52 server smbd[1350]:   open_mode_check: Existent process 1337 left active oplock. 
    Mar  8 13:27:13 server smbd[1337]: [2008/03/08 13:27:13, 0] smbd/oplock.c:oplock_break(758) 
    Mar  8 13:27:13 server smbd[1337]:   oplock_break: receive_smb error (Success) 
    Mar  8 13:27:13 server smbd[1337]:   oplock_break failed for file LIBRICD/LIBRI.3 (dev = 901, inode = 3301, file_id = 15). 
    Mar  8 13:27:13 server smbd[1337]: [2008/03/08 13:27:13, 0] smbd/oplock.c:oplock_break(843) 
    Mar  8 13:27:13 server smbd[1337]:   oplock_break: client failure in break - shutting down this smbd. 
    Mar  8 13:27:24 server smbd[1350]: [2008/03/08 13:27:24, 0] smbd/oplock.c:request_oplock_break(981) 
    Mar  8 13:27:24 server smbd[1350]:   request_oplock_break: no response received to oplock break request to pid 1337 on port 32780 for dev = 901, inode = 3349, file_id = 18 
    Mar  8 13:27:45 server nmbd[1330]: [2008/03/08 13:27:45, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) 
    Mar  8 13:27:45 server nmbd[1330]:   ***** 
    Mar  8 13:27:45 server nmbd[1330]:    
    Mar  8 13:27:45 server nmbd[1330]:   Samba name server XYZ is now a local master browser for workgroup ABC on subnet 192.168.101.100 
    Mar  8 13:27:45 server nmbd[1330]:    
    Mar  8 13:27:45 server nmbd[1330]:   *****
    
    ....... Und nun treten keine weiteren Fehler mehr auf.....
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. #2 codc, 10.03.2008
    Zuletzt bearbeitet: 10.03.2008
    codc

    codc /dev/null

    Dabei seit:
    12.01.2004
    Beiträge:
    607
    Zustimmungen:
    0
    Tut mir leid aber wer ein System seit Jahren ungewartet fährt hat es nicht besser verdient zumal auf einem produktiven System. Das erst was ich gemacht habe als ich bei uns in der Firma so eine Krücke übernommen habe war die Kiste neu aufzusetzen.
    Mein Samba läuft seit Dezember nach der Neuinstallation ohne ein Problem mit etwa 20 Usern und heftiger Netzlast zum Teil. Nur ein Mal die Tage ein reboot wegen Kernel-Update wg des lokalem Exploit im 2.6.er Kernel.
    Autsch - ein >10 Jahre altes OS was schon seit Jahren nicht mehr supportet wird
     
  4. #3 w-d-h-o, 10.03.2008
    w-d-h-o

    w-d-h-o Grünschnabel

    Dabei seit:
    28.02.2008
    Beiträge:
    4
    Zustimmungen:
    0
    Will mich hier nicht rechtfertigen, aber gänzlich ungewartet ist es nicht. Festplatten, Lüfter und ähnliche Verschleißteile werden getauscht. Die logs werden auf Fehlermeldungen beobachtet. Ich bin leider kein EDV-Experte. Habe schon mehrfach versucht welche für die Administration zu bekommen, aber da gibts hier nur Schrott.
    Und warum soll ich ein laufendes System neu aufsetzen? Unsere Anforderungen haben sich seit der Instalation nicht geändert. Linux ist nicht bekannt dafür, sich mit der Zeit selbst zu verschrotten. Neues OS=neue unbekannte Fehler.
    Na herzlichen Glückwunsch, da kann ich aber bessere Zeiten vorweisen. Letzter Reboot (und das auch nur zum Tausch von Verschleißteilen) September 2006. Seit dem kein Fehler - bis März 2008
    Na, den Support von Microsoft kann man doch wirklich vergessen.
    Aber im ernst, Win98SE läuft für unsere Anforderungen gut genug. Habe Images gezogen und setze alle 1-2 Jahre die zugemüllten Rechner flux neu auf. Bei der Instalation der meisten Clients war auch bereits XP auf dem Markt, aber zu unstabiel. Hatte genügend Ärger mit dem einen Client xp für die Buchhaltung, bis endlich Patches die gröbsten Fehler behoben haben. Aber natürlich werde ich neue Clients mit neuem OS installieren (Frage ist noch, mit welchem)
    Sorry codc, aber dein Kommetar hilft nicht weiter.

    Ich hätte gern gewußt, was alle 1-2 Jahre zu solchen Zusammenbrüchen führt, und wie ich möglichst schnell im Fehlerfall das System wieder zum laufen bekomme.
     
  5. #4 supersucker, 10.03.2008
    supersucker

    supersucker Foren Gott

    Dabei seit:
    21.02.2005
    Beiträge:
    3.873
    Zustimmungen:
    0
    Jetzt fühl dich mal nicht gleich so angegriffen.

    Das Problem bei Suse 8.0 ist, das es schon seit Jahren keine Security-Updates mehr gibt.

    Das heißt, jedes durchschnittlich begabte Script-Kiddie kann die Kiste knacken und damit machen was es will.

    Und das meinte codc mit "ungewartet".
     
  6. worker

    worker König

    Dabei seit:
    29.03.2007
    Beiträge:
    848
    Zustimmungen:
    0
    Hi,

    also mich wundert hier ein wenig warum man darauf "herumreitet", dass w-d-h-o eine ältere Linux-Version fährt. Ich nehme an, dass die Kiste eh nicht ans I-Net angeschlossen ist ...


    Ich bin bei Leibe kein Samba/Hardware/etc. - Experte, deshlab hier nur mal einen Gedankenanstoß...

    Da der Server in den Logs nichts ungewöhnliches bringt, würde ich vielleicht auf der Hardwareseite (MoBo/RAM) anfangen den Fehler zu suchen.
    Könnte vielleicht auch am Switch/Router/Kabel liegen.

    Beobachte mal auf der Serverseite (mit iptraf, etc.) den Netzwerkverkehr, wenn die Clients diesen Zusammenbruch "voraussagen".

    Ein Beispiel an "unerklärlichen Phänomenen": Meine OnBoard Netzwerkkarte (1 GB) spinnt mal öffter, mal überhaupt nicht. Ich nehme an, dass da irgend ein Bauteil (Kondensator?) immer "per Zufall funktioniert" (oder auch nicht).

    Gruß
    W.
     
Thema:

Samba bricht zusammen

Die Seite wird geladen...

Samba bricht zusammen - Ähnliche Themen

  1. Samba Datentransfer bricht ab

    Samba Datentransfer bricht ab: Hallo zusammen, ich suche seit 2 Tagen im Internet nach einer Lösung, aber ich finde einfach keine brauchbare. Folgendes Szenario: Ich vor einem...
  2. Samba bricht bei der Installation via Aptitude ab

    Samba bricht bei der Installation via Aptitude ab: Hallo zusammen Ich versuchte Samba via Aptitude zu installieren. Dieses jedoch hängt sich auf, nachdem Samba die Benutzer "importiert" hat....
  3. [Debian] Samba bricht Dateitransfer ab

    [Debian] Samba bricht Dateitransfer ab: [Debian] Samba bricht Dateitransfer ab [solved] hallo zusammen ich habe gröbere Probleme beim kopieren von Dateien von WinXP auf meinen...
  4. Samba bricht Datenübertragung ab!

    Samba bricht Datenübertragung ab!: Hallo zusammen! habe letzte Woche für unsere Studenten-WG einen neuen Server installiert! Es läuft Suse 10 mit Samba 3.0.20-4-SUSE. Leider...
  5. Samba4 AD DC

    Samba4 AD DC: Hey Forum, das ist mein erster Post ich hoffe ich bin in der Richtigen section [IMG] Ich habe mit OpenSuSe 42.1 probiert einen Samba4 AD DC...