slacky.eu

Ragazzi ho un problema con samba vers 3.0.25a (aggiornata dalla dir patches), quando lo eseguo ottengo questo output:

root@sgserver:~# /etc/rc.d/rc.samba start
Starting Samba:  /usr/sbin/smbd -D
/etc/rc.d/rc.samba: line 11:  5012 Aborted                 (core dumped) /usr/sbin/smbd -D
                 /usr/sbin/nmbd -D
/etc/rc.d/rc.samba: line 11:  5013 Aborted                 (core dumped) /usr/sbin/nmbd -D

Nei file log.nmbd e log.smbd vi è riportato il BACKTRACE che vi posto di seguito:

Codice: Seleziona tutto

root@sgserver:/var/log/samba# cat log.smbd
[2007/06/27 14:27:49, 0] smbd/server.c:main(944)
  smbd version 3.0.25a started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/06/27 14:27:49, 0] param/loadparm.c:lp_do_parameter(3514)
  Global parameter guest account found in service section!
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 5018 (3.0.25a)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2007/06/27 14:27:49, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 5018): internal error
[2007/06/27 14:27:49, 0] lib/util.c:log_stack_trace(1736)
  BACKTRACE: 17 stack frames:
   #0 /usr/sbin/smbd(log_stack_trace+0x2e) [0x8023314e]
   #1 /usr/sbin/smbd(smb_panic+0x57) [0x80233267]
   #2 /usr/sbin/smbd [0x8021de9f]
   #3 [0xffffe420]
   #4 /lib/libc.so.6 [0xb7b93631]
   #5 /lib/libc.so.6(iconv+0x6c) [0xb7b92c4c]
   #6 /usr/sbin/smbd [0x80240c11]
   #7 /usr/sbin/smbd(smb_iconv+0x132) [0x80240da2]
   #8 /usr/sbin/smbd [0x8021a577]
   #9 /usr/sbin/smbd(convert_string+0x237) [0x8021abb7]
   #10 /usr/sbin/smbd(init_doschar_table+0x92) [0x8022dd62]
   #11 /usr/sbin/smbd(init_iconv+0x2ee) [0x8021a40e]
   #12 /usr/sbin/smbd(lp_load+0xdd3) [0x800527a3]
   #13 /usr/sbin/smbd(reload_services+0x7c) [0x802f346c]
   #14 /usr/sbin/smbd(main+0x2b0) [0x802f3c30]
   #15 /lib/libc.so.6(__libc_start_main+0xd8) [0xb7b91df8]
   #16 /usr/sbin/smbd [0x80047071]
[2007/06/27 14:27:49, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/samba/cores/smbd

e questo:

Codice: Seleziona tutto

 
root@sgserver:/var/log/samba# cat log.nmbd
[2007/06/27 14:27:49, 0] nmbd/nmbd.c:main(697)
  Netbios nameserver version 3.0.25a started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 5019 (3.0.25a)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/06/27 14:27:49, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2007/06/27 14:27:49, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 5019): internal error
[2007/06/27 14:27:49, 0] lib/util.c:log_stack_trace(1736)
  BACKTRACE: 17 stack frames:
   #0 /usr/sbin/nmbd(log_stack_trace+0x2e) [0x800a197e]
   #1 /usr/sbin/nmbd(smb_panic+0x57) [0x800a1a97]
   #2 /usr/sbin/nmbd [0x8008c6cf]
   #3 [0xffffe420]
   #4 /lib/libc.so.6 [0xb7d06631]
   #5 /lib/libc.so.6(iconv+0x6c) [0xb7d05c4c]
   #6 /usr/sbin/nmbd [0x800af441]
   #7 /usr/sbin/nmbd(smb_iconv+0x132) [0x800af5d2]
   #8 /usr/sbin/nmbd [0x80088da7]
   #9 /usr/sbin/nmbd(convert_string+0x237) [0x800893e7]
   #10 /usr/sbin/nmbd(init_doschar_table+0x92) [0x8009c592]
   #11 /usr/sbin/nmbd(init_iconv+0x2ee) [0x80088c3e]
   #12 /usr/sbin/nmbd(lp_load+0xdd3) [0x80047ff3]
   #13 /usr/sbin/nmbd [0x8001f490]
   #14 /usr/sbin/nmbd(main+0x23c) [0x8001fabc]
   #15 /lib/libc.so.6(__libc_start_main+0xd8) [0xb7d04df8]
   #16 /usr/sbin/nmbd [0x8001e471]
[2007/06/27 14:27:49, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/samba/cores/nmbd

Secondo voi cosa sia potuto accadere?

L'HOWTO dice che o Ã¨ un bug di samba o un problema hardware e di mandargli dettagliate informazioni

If you get the message â€œINTERNAL ERRORâ€ in your log files, it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless you have faulty hardware or system software).

If the message came from smbd, it will probably be accompanied by a message that details the last SMB message received by smbd. This information is often useful in tracking down the problem, so please include it in your bug report.

You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.

You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your Samba log files. This file is the most useful tool for tracking down the bug. To use it, you do this:

$ gdb smbd core

adding appropriate paths to smbd and core so gdb can find them. If you do not have gdb, try dbx. Then within the debugger, use the command where to give a stack trace of where the problem occurred. Include this in your report.

If you know any assembly language, do a disass of the routine where the problem occurred (if it's in a library routine, then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you do not know assembly, including this information in the bug report can be useful.

Il sistema di base era una slack 10.2 e tutto funzionava bene (samba compreso). Ebbi la necessità di installare CUPS e convinto di avere la slack 11 come ho a casa installai i pacchetti e una serie di librerie per la 11, ma nonostante ciò andò tutto a buon fine, sia samba che cups funzionavano egregiamente. Quando mi resi conto della cosa, povero me deficiente, pensai di fare gli aggiornamenti tramite swaret e nel casotto che mi sono ritrovai un miscuglio di librerie vecchie e nuove tra le quali le libglibc solibs etc... A questo punto mi domandai: e se riavviassi? I principali comandi non funzionavano piu, come logico che sia, quindi mi procurai il dvd di slack 11 ed effettuati l'upgrade totale. Il sistema riprese a funzionare tranne Samba che ora crasha e non so proprio come fare! La cosa positiva è che ho veramente capito ora cosa significa lasciar stare il cane che dorme!! E ora?? Io provo a fare il debuggin ma poi dovrei mandarlo a samba?

L'upgrade totale sei sicuro che sia andato tutto a buon fine, di non avere librerie ancora duplicate?

In tutta onestà non ho ricordi di crash simili in samba (magari ho solo fortuna).

Comunque controllerei che l'installazione rispetti fedelmente una 11 e dopo sì manderei i dati per segnalare il bug.

Nada l'aggiornamento a quanto pare è andato a buon fine, uffaaa ho anche provato a far partire samba con il file di esempio, ma va sempre in crash... che guaio!!

slacky.eu

Crash di Samba

Crash di Samba