similar to: The memory maybe leak in samba 4.3.11

On Tue, May 09, 2017 at 02:59:51AM +0000, Zhangxiaoxu via samba-technical wrote: > Hi, > Thanks a lot. > > Use the valgrind, we found the stack of the malloc as below, so, maybe it is not memory leak. > ==2796353== 36,334,440 bytes in 100,929 blocks are still reachable in loss record 774 of 774 > ==2796353== at 0x4C2AB80: malloc (in

Hi, Thanks a lot. Use the valgrind, we found the stack of the malloc as below, so, maybe it is not memory leak. ==2796353== 36,334,440 bytes in 100,929 blocks are still reachable in loss record 774 of 774 ==2796353== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2796353== by 0x953B88F: ??? (in

On 10/5/2020 11:58 AM, Rowland penny via samba wrote: > On 05/10/2020 16:30, Jason Keltz via samba wrote: >> Hi. >> >> Using MIT5 backend with Samba.. > I hope you mean on the clients, the use of MIT as the kdc on a Samba > DC is experimental and shouldn't be used in production Hi Roland, our environment uses CentOS 7.? I don't have much choice but to use this

> Is this an exist problem? Yes Fixed https://wiki.samba.org/index.php/Samba_4.3_Features_added/changed In 4.3.13 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba-technical > [mailto:samba-technical-bounces at lists.samba.org] Namens > Zhangxiaoxu via samba-technical > Verzonden: donderdag 4 mei 2017 14:42 > Aan: 'bugzilla-maintenance at

Hello, i upgraded my ctdb cluster (3 nodes) from samba 4.7.7 to 4.8.3. Followed the steps under "policy" in this wikipage https://wiki.samba.org/index.php/Upgrading_a_CTDB_cluster. I shutdown all CTDB nodes and upgraded them. After the upgrade i started all nodes and ctdb status shows: Number of nodes:3 pnn:0 192.168.199.52   OK (THIS NODE) pnn:1 192.168.199.53   OK pnn:2

Hi all, I'm setting up a clustered environment on CentOS 7.6.1810 with Samba 4.8.3-6.el7_6 and the corresponding ctdb package. I'm using FreeIPA 4.6.4 as my auth backend. Currently I'm running into this bug https://bugzilla.samba.org/show_bug.cgi?id=13465 however I would assume that it is fixed in the latest release (dated 29July 2019). It crashed once CTDB runs testparm to check the

Please CC as I''m not subscribed to valgrind-developers. Under Xen the toolstack is responsible for managing the domains in the system, e.g. creating, destroying, and otherwise manipulating them. To do this it uses a number of ioctls on the /proc/xen/privcmd device. Most of these (the MMAPBATCH ones) simply set things up such that a subsequenct mmap call will map the desired guest

Hello, I switched the first member server in production from 3.6 to 4.1. But since that, several times per day, smbd processes are crashing on that machine. Has anybody encountered this, too? [2013/11/05 04:14:43.532768, 0, pid=91892] ../source3/lib/popt_common.c:67(popt_s3_talloc_log_fn) talloc: access after free error - first free may be at ../source3/smbd/open.c:1529 [2013/11/05

Hai, This looks like tevent tdb or ldb has an incorrect version. Can you post more about the os and installed packages. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Jacek Fefli?ski via samba > Verzonden: maandag 18 december 2017 13:49 > Aan: samba at lists.samba.org > Onderwerp: [Samba] Winbind crash

Hi! We're running Samba4 (Version 4.0.0beta4) and are experiencing problems with smb_panic actions which result in loads of sleep processes in the end taking down the entire machine. This problem did not exist in prior builds for us (upgraded from alpha17 to beta3 and then beta4). Are there any specific log extracts I can supply that can help someone pinpoint the problem? log.smbd seems to

Can someone point me at how the machine account plays into permitting access here? [it] path = /mnt/data/samba/data/it valid users = CUSTOMER\sgw CUSTOMER\fhäu @CUSTOMER\edv read only = No browseable = No A user out of the group "edv" uses the PC "p10013". Sometimes he gets access, sometimes not. Logs show: (a) check_ntlm_password: authentication for user [P10013$]

Hello, Just yesterday, we installed the new samba version - 4.18.1 - and configured AD domain controllers. Samba service started without any issues. But with in 10 minutes of starting the service entered failed state. Restarting the service is also resulting in the same issue. Service enters failed state with in 15-20 minutes I have deployed samba on RHEL 8. When the service enters the

Dear list, I keep getting strange "internal error"s from smbd. I increased the log level to 3 and pasted the relevant log snippet. Does anyone know (or guess) what's going on? What should I check? Any direction to investigate? Thanks a lot, Sascha ? =============================================================== [2014/03/24 13:28:49.787910, ?0, pid=13041, effective(3000026, 20),

My stock CentOS 5.4 box won't come up after a reboot as reported from my office. Error is: "duplicate or bad block in use" Before rebooting xm dmsg had printk suppressed messages. The box is remote, 2 hour drive. Some advice on what hardware to bring with me and how to approach this via fsck would be welcome. Its an nvidia dmraid boot on WD Velocirapters. And Happy New Year to

Hello, My envirronement: Debian 7.5 Samba version 4.1.7 from backport Cups 1.5.3-5 I have upgrade from samba 3 to samba4 this morning. Since, I have some very strange error when I try to print or list the shared printer from a windows Server: Here is my syslog log file when I try to refresh the printers list from a Windws 2008 server. Jun 4 17:00:24 daisy2k11 smbd[22133]: [2014/06/04

Am 2015-12-29 um 18:59 schrieb Rowland penny: > NO! This will give you precisely 0 users > > config * == the range the 'builtin' users will be mapped to. > config customer == the range for all the domain users that have a > uidNumber attribute. If a user doesn't have a uidNumber attribute > containing a number inside the range set in smb.conf (in your case >

I have Samba 4.0.9 installed on three Centos servers. On my primary DC I am getting faults and core dumps. Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.083800, 0] ../lib/util/fault.c:72(fault_report) Oct 2 06:10:37 dc1 smbd[1195]: =============================================================== Oct 2 06:10:37 dc1 smbd[1195]: [2013/10/02 06:10:37.084493, 0]

Dear all, since a few days I have a panic error in my logfiles on my second joined DC, Samba version 4.3.4. Can anyone help? PANIC (pid 24120): assert failed: VALID_STAT(smb_fname->st) May 16 10:01:43 s4slave smbd[24120]: [2019/05/16 10:01:43.333006, 0] ../source3/lib/util.c:900(log_stack_trace) May 16 10:01:43 s4slave smbd[24120]: BACKTRACE: 30 stack frames: May 16 10:01:43 s4slave

Hi all, We recently upgrade from CentOS 5.8 to CentOS 5.9 on kernel-xen-2.6.18-348.3.1.el5, and after booting into the new kernel, noted large amounts of these messages every second or so in the logs: Mar 30 21:38:35 atlas2 kernel: Warning Timer ISR/0: Time went backwards: delta=-1393683849 delta_cpu=22316151 shadow=225003685197135 off=129240997 processed=225005208029053

Hi, I thought I should share this unusual behaiviour of samba 4.1.11. All of a sudden while I tried to delete a Folder via samba on a share it crashed. I was using Mac OSx's V 10.9.4 internal samba client (regular "CMD+K" mount via Finder). Server: [...] FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC