similar to: Samba-ad-dc service stops with segfault error

Hi, Bartlett I decided to cut some subsystem by myself, So I spent several days to study the SAMBA 4 WAF build system and now know the base steps of build. but which subsystem can be removed for snmd/nmbd/smbpasswd ? followings are the full dependencies of these 3 binary ldd bin/smbpasswd libpthread.so.0 => /lib/libpthread.so.0 (0xf7139000) libsamba-util.so.0 =>

On 10/5/2020 12:16 PM, Rowland penny via samba wrote: > On 05/10/2020 17:01, Jason Keltz via samba wrote: >> 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

I recently patched my Solaris server and suddenly my Samba service is not working correctly. When Anyone accesses a samba share the samba daemon panics and shuts down. Solaris than restarts the system, unless there are multiple panics simultaneously than the service is placed in maintenance mode. The SAMBA server is a stand alone supporting a dozen end users for a large file store behind the

I recently patched my Solaris server and suddenly my Samba service is not working correctly. When Anyone accesses a samba share the samba daemon panics and shuts down. Solaris than restarts the system, unless there are multiple panics simultaneously than the service is placed in maintenance mode. The SAMBA server is a stand alone supporting a dozen end users for a large file store behind the

Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when

Forgot to mention that this is on Centos 8. So maybe something different than this: https://www.spinics.net/lists/samba/msg163085.html Regards Christian Am 16.04.20 um 13:45 schrieb Christian Naumer via samba: > Hello alAl, > after update of our test server to 4.12.1 from 4.11 it crashes. If the > vfs module is removed from the config everthing works as before. Logs > from the

Dear all, I've an issue with my samba installation with a version of samba 4.9.2 that I’ve compiled for Ubuntu 16.04. Samba works without any particular issues until I try to use the sharing for Time Machine backup. In fact, after starting the Time Machine backup after a while, random time like 2-3 hours of backup, I got the following panic error and the backup stops and I need to reboot

Hello alAl, after update of our test server to 4.12.1 from 4.11 it crashes. If the vfs module is removed from the config everthing works as before. Logs from the crash see here: .0.31:445] Apr 16 13:36:47 lx-sv-03 smbd_audit[6263]: [2020/04/16 13:36:47.546559, 0] ../../source3/lib/util.c:830(smb_panic_s3) Apr 16 13:36:47 lx-sv-03 smbd_audit[6263]: PANIC (pid 6263): vfs_full_audit.c: name table

Hello, I've encountered recurring issue with samba crashes when creating initial Time Machine backup on samba share from Mac. Whole scenario, details about software and logs are below. On Mac client: connected to smb share with "valid user" account; added smb share as Time Machine disk. Time machine has been set for automatic backup, I've selected Back Up Now. Connection dies

On 10/12/2019 14:04, Andrea Venturoli via samba wrote: > Hello. > > At a customer's site I had: > _ Windows 2008 DC; > _ Samba 4.8 fileserver on FreeBSD 11.3/amd64 on UFS; > _ several Windows and Mac clients. > > Recently, having to move to Samba 4.10, I decided to bring up a new > fileserver in a jail (and let the base 4.8 one die after transferring > all

Hi, everybody. I can't understand the nature of the exact error on my samba-server. I'd be very thanksfull for some help... Here's situation: One Linux-server (CentOS 7.2) with Samba and a network of 14 noteboks (win 10). At some point, during working day, smb starts dumping core and syslog giving us the following: 2016-01-16 18:45:15 err infoclinik daemon smbd 2016-01-16

Hello, I'm receiving repeated cores with the captioned environment. Here's a snippet from log.smbd: ======================== [2018/07/08 03:01:55.936275, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 91640 (4.7.1) Please read the Trouble-Shooting section of the Samba HOWTO [2018/07/08 03:01:55.936307, 0] ../lib/util/fault.c:81(fault_report)

Am 2015-12-30 um 10:40 schrieb Stefan G. Weichinger: > Thanks a lot for that explanation. > I read it after it started working here yesterday so excuse my late > reply. I never understood it the way you described it above, this would > have helped me with other servers earlier as well. Maybe off topic or another issue, but I add it to this thread as it affects the same server. The

Our samba server in ap-east-1 is running very slow today I noticed three things in log.smb, and I don't understand any of them ---------- #1 roughly every 80 seconds what appears to be a reconnect loop [2020/11/19 17:35:46.283315, 2] ../../source3/lib/tallocmsg.c:87(register_msg_pool_usage) Registered MSG_REQ_POOL_USAGE [2020/11/19 17:35:46.287132, 1]

On 8/04/23 14:13, Anantha Raghava via samba wrote: > 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

Dear all, we updated to 4.12.10-10 using the sernet packages. After approx. 30 minutes I obtainted the following messages in syslog: root at ctdb-ho-2:~# journalctl -f -- Logs begin at Wed 2020-11-11 08:53:27 CET. -- Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.616823, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory:

Hello. Today a box I manage throwed a lot of these (Samba 4.3.3 working as an ADS member on FreeBSD 10.1/amd64): > Mar 7 15:18:54 xxxxxx smbd_audit[51710]: connect to service xxxxxxxxx by user XXXXXXXX\xxxxxxxx > Mar 7 15:18:54 xxxxxx smbd_audit[51710]: open XXXXXXXXX/XXXXXXXXX.ods (fd 9) > Mar 7 15:18:54 xxxxxx smbd_audit[51710]: [2016/03/07 15:18:54.364808, 0]

Hi everyone I have a four node samba/CTDB cluster exporting CIFS shares from a GPFS 3.5 cluster. Samba/CTDB is at 4.2.3: [root at hostname ~]# rpm -qa | grep sernet sernet-samba-ad-4.2.3-18.el6.x86_64 sernet-samba-libs-4.2.3-18.el6.x86_64 sernet-samba-common-4.2.3-18.el6.x86_64 sernet-samba-4.2.3-18.el6.x86_64 sernet-samba-ctdb-4.2.3-18.el6.x86_64 sernet-samba-client-4.2.3-18.el6.x86_64

On Mon, Nov 09, 2020 at 04:01:47PM +0100, Benedikt Kale? via samba wrote: > Dear List, > > I updated to samba 4.12.10-SerNet-Debian-9.buster from 4.12.9 > and did a > > gluster volume set volume performance.write-behind off > > Now I get this in /var/log/syslog and randomly people don't get access > to a shae. Can you load the debug symbols please ? That should

pls see this logs as well : Jän 05 12:08:21 samba01.customer.at smbd[18809]: [2016/01/05 12:08:21.401618, 0] ../lib/util/fault.c:78(fault_report) Jän 05 12:08:21 samba01.customer.at smbd[18809]: =============================================================== Jän 05 12:08:21 samba01.customer.at smbd[18809]: [2016/01/05 12:08:21.401904, 0] ../lib/util/fault.c:79(fault_report) Jän 05 12:08:21