Buna Am un server (firewall, router, file-server) care a mers impecabil vreo un an si ceva (cu un RH 8.0beta 2 pe el) dupa care am facut un upgrade la Fedora Core. Ok, am inceput cu stangul, am pus tot un beta (FC 0.94 Severn) si a inceput sa cam ploua cu mesaje precum cel de mai jos. Dar acu mi-am reparat deja greseala si am pus un Fedora Core 1 curat, dar degeaba, mesajul nu a disparut doar i-a scazut frecventa de la >10 pe zi la doar o singura data, dar si asa e mult prea mult... In momentul in care pe server imi apare "bucuria", pe desktop-ul in cauza (Windows 98, Office XP) fisierul ba nu mai poate fi salvat, ba nu mai poate fi deschis pentru ca e raportat ca fiind utilizat de catre cineva, ba se blocheaza Office-ul cu totul, cand cum... dar intotdeauna iese urat... Intrebare de baraj: crapa Samba din cauza ca, crapa Office-ul, sau crapa Office-ul din cauza ca, crapa Samba...? Sau amandoua din alta cauza... Daca aveti idee ce se intampla, ce pot sa fac... v-as fi recunoscator.
Va multumesc anticipat, Alexandru P.S. sa dau totushi ceva versiuni, nu? :) - Fedora Core 1 Yarrow - glibc 2.3.2-101 - samba 3.0.0-15 - partitia de pe care sunt servite fisierele este ext3 - este vorba de o retea mica cu vreo 10 statii Windows98 toate conectate printr-un switch Surecom ------------------------------------------------------------------- Dec 12 13:08:56 consulting smbd[32303]: [2003/12/12 13:08:56, 0] lib/util_sock.c:read_socket_data(342) Dec 12 13:08:56 consulting smbd[32303]: read_socket_data: recv failure for 4. Error = Connection reset by peer Dec 12 14:42:16 consulting smbd[29408]: [2003/12/12 14:42:16, 0] lib/util_sock.c:read_socket_data(342) Dec 12 14:42:16 consulting smbd[29408]: read_socket_data: recv failure for 4. Error = No route to host Dec 12 14:44:06 consulting smbd[29287]: [2003/12/12 14:44:06, 0] lib/fault.c:fault_report(36) Dec 12 14:44:06 consulting smbd[29287]: =============================================================== Dec 12 14:44:06 consulting smbd[29287]: [2003/12/12 14:44:06, 0] lib/fault.c:fault_report(37) Dec 12 14:44:06 consulting smbd[29287]: INTERNAL ERROR: Signal 11 in pid 29287 (3.0.0-15) Dec 12 14:44:06 consulting smbd[29287]: Please read the appendix Bugs of the Samba HOWTO collection Dec 12 14:44:06 consulting smbd[29287]: [2003/12/12 14:44:06, 0] lib/fault.c:fault_report(39) Dec 12 14:44:06 consulting smbd[29287]: =============================================================== Dec 12 14:44:06 consulting smbd[29287]: [2003/12/12 14:44:06, 0] lib/util.c:smb_panic(1422) Dec 12 14:44:06 consulting smbd[29287]: PANIC: internal error Dec 12 14:44:06 consulting smbd[29287]: [2003/12/12 14:44:06, 0] lib/util.c:smb_panic(1429) Dec 12 14:44:06 consulting smbd[29287]: BACKTRACE: 17 stack frames: Dec 12 14:44:06 consulting smbd[29287]: #0 smbd(smb_panic+0x110) [0x6e4430] Dec 12 14:44:06 consulting smbd[29287]: #1 smbd [0x6d03e4] Dec 12 14:44:06 consulting smbd[29287]: #2 /lib/tls/libc.so.6 [0x420a18] Dec 12 14:44:06 consulting smbd[29287]: #3 /lib/tls/libc.so.6 [0x468d5a] Dec 12 14:44:06 consulting smbd[29287]: #4 /lib/tls/libc.so.6(malloc+0x8d) [0x46810d] Dec 12 14:44:06 consulting smbd[29287]: #5 smbd(tdb_store+0x111) [0x6f9dd1] Dec 12 14:44:06 consulting smbd[29287]: #6 smbd(claim_connection+0x2c5) [0x5877c5] Dec 12 14:44:06 consulting smbd[29287]: #7 smbd [0x5d5738] Dec 12 14:44:06 consulting smbd[29287]: #8 smbd(make_connection+0x16a) [0x5d6b4a] Dec 12 14:44:06 consulting smbd[29287]: #9 smbd(reply_tcon_and_X+0x1d9) [0x5a3339] Dec 12 14:44:06 consulting smbd[29287]: #10 smbd [0x5d31bf] Dec 12 14:44:06 consulting smbd[29287]: #11 smbd [0x5d3463] Dec 12 14:44:06 consulting smbd[29287]: #12 smbd(process_smb+0xa4) [0x5d36b4] Dec 12 14:44:06 consulting smbd[29287]: #13 smbd(smbd_process+0x19f) [0x5d440f] Dec 12 14:44:06 consulting smbd[29287]: #14 smbd(main+0x4fd) [0x757f4d] Dec 12 14:44:06 consulting smbd[29287]: #15 /lib/tls/libc.so.6(__libc_start_main+0xf0) [0x40e750] Dec 12 14:44:06 consulting smbd[29287]: #16 smbd [0x5792e2] Dec 12 14:44:06 consulting smbd[29287]: --- Detalii despre listele noastre de mail: http://www.lug.ro/
