[Samba] smbd Crash
Bruno MACADRE
bruno.macadre at univ-rouen.fr
Fri Oct 2 06:54:24 MDT 2009
Bruno MACADRE a écrit :
> Hi,
>
> I don't stop to have problems with samba :s ...
>
> Now after having workaround the bug of scanning all LDAP users for each
> connexion... smbd crash very often.
>
> In some workstation log files i can see something like this :
>
> ...
> [2009/10/01 16:28:12, 2] smbd/open.c:580(open_file)
> baala opened file .profiles/firefox/cookies.sqlite-journal read=No
> write=No (numopen=20)
> [2009/10/01 16:28:12, 2] smbd/close.c:612(close_normal_file)
> baala closed file .profiles/firefox/cookies.sqlite-journal
> (numopen=19) NT_STATUS_OK
> *** glibc detected *** /usr/sbin/smbd: realloc(): invalid next size:
> 0x0955c5c8 ***
> ======= Backtrace: =========
> /lib/tls/i686/cmov/libc.so.6[0xb7cca604]
> /lib/tls/i686/cmov/libc.so.6[0xb7cce1b1]
> /lib/tls/i686/cmov/libc.so.6(realloc+0x106)[0xb7cceee6]
> /usr/sbin/smbd(Realloc+0x7d)[0x834326d]
> /usr/sbin/smbd(brl_lock+0x4a3)[0x82d1f23]
> /usr/sbin/smbd(do_lock+0x147)[0x82cc517]
> /usr/sbin/smbd[0x8120467]
> /usr/sbin/smbd[0x8121e7a]
> /usr/sbin/smbd(reply_trans2+0x6ef)[0x8123b5f]
> /usr/sbin/smbd[0x8145848]
> /usr/sbin/smbd[0x81481ad]
> /usr/sbin/smbd[0x8148bd2]
> /usr/sbin/smbd(run_events+0x13c)[0x8353cac]
> /usr/sbin/smbd(smbd_process+0x791)[0x8147cd1]
> /usr/sbin/smbd[0x8623a25]
> /usr/sbin/smbd(run_events+0x13c)[0x8353cac]
> /usr/sbin/smbd[0x8353f4e]
> /usr/sbin/smbd(_tevent_loop_once+0x9b)[0x835458b]
> /usr/sbin/smbd(main+0xc12)[0x8624732]
> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7c71775]
> /usr/sbin/smbd[0x80c3e91]
> ======= Memory map: ========
> ...
>
> The problem is when this event appear, the smbd of the user crash and
> put the smbd service in a unusable state... All users already connected
> can continue to work but no more connexion are allowed, and i see lot of
> "smbd <defunct>" process apprearing.
>
> At this time the samba 3.4.1 (and 3.4.2) are unusable at all beacause
> this behavior appears many dozens time per day... I've tested all the
> hardware of the server and no problem. The server was equiped with 2
> QuadCore E5430 @ 2.66 and 4Gb of memory. I've got 64 Workstations into
> the domain (all workstation have dual-boot WinXP Pro / Ubuntu 9.04), and
> about 600 users.
>
> Any idea ?
>
> Regards,
> Bruno
>
So,
I've recompiled my samba 3.4.2 and ran through valgrind to show what
happening :
- First thing, through valgrind i don't see any crash with memory dump
(see my previous message) during last 2 hours
- When i analyse de valgrind logfile produced i see a lot of error
messages like these :
==12818== Invalid read of size 1
==12818== at 0x53C93F0: _nss_files_setnetgrent (in
/lib/tls/i686/cmov/libnss_files-2.9.so)
==12818== ...
==12818== ...
==12818== by 0x41975B: run_events (events.c:126)
==12818== Address 0x4f0f887 is 1 bytes before a block of size 120 alloc'd
==12818== at 0x4826FDE: malloc (vg_replace_malloc.c:207)
==12818== by 0x4B92737: getdelim (in /lib/tls/i686/cmov/libc-2.9.so)
==12818== ...
==12818== ...
==12818== by 0x20FE37: switch_message (process.c:1377)
==12818== by 0x2127EC: process_smb (process.c:1408)
I don't know if this kind of allocation errors is normal (if any samba
developper team read this ^^), but i think it's a clue for the crash of
smbd (with the "realloc" errors like in my previous message).
see you later for further informations... i return checking memory
leaks of samba ^^
Regards,
Bruno
--
Bruno MACADRE
-------------------------------------------------------------------
Ingénieur Systèmes et Réseau | Systems and Network Engineer
Département Informatique | Department of computer science
Responsable Réseau et Téléphonie | Telecom and Network Manager
Université de Rouen | University of Rouen
-------------------------------------------------------------------
Coordonnées / Contact :
Université de Rouen
Faculté des Sciences et Techniques - Madrillet
Avenue de l'Université - BP12
76801 St Etienne du Rouvray CEDEX
Tél : +33 (0)2-32-95-51-86
Fax : +33 (0)2-32-95-51-87
-------------------------------------------------------------------
More information about the samba
mailing list