similar to: Troubles with Mac clients

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

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

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. Nov? 9 15:56:14 ctdb-host smbd[16832]: [2020/11/09 15:56:14.078120,? 0] ../../source3/lib/popt_common.c:68(popt_s3_talloc_log_fn) Nov? 9 15:56:14 ctdb-host smbd[16832]:??

Dear Jeremy, thanks for your reply. I assume I load the the debug symbols by passing something in the [global] section? I now changed back to a fuse_mount to get my colleagues back to work again. Tomorrow at 17 CEST I can add a test share with vfs_glusterfs to test it. Best Bene Am 09.11.20 um 17:55 schrieb Jeremy Allison: > On Mon, Nov 09, 2020 at 04:01:47PM +0100, Benedikt Kale? via

Hi, I had issues using"vfs objects = acl_xattr" (possibly too old version [Version 4.13.13-Debian] for the needed "acl_xattr:security_acl_name = user.samba" option needed if running in a non-priv container). So I tried "vfs objects = acl_tdb" and found it working. In https://wiki.samba.org/index.php/File_System_Support I found: File systems without xattr support

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

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]

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 Samba fellows, I try to install samba on my notebook in order to get it into my samba based domain. It was a bit picky to get everything assembled on the notebook - but that last issue is hard. :-( I installed it from the sources on Debian Jessie - exactly in the same manner I used for my servers. I got sssd and kerberos working... > root at alecto:/usr/src/samba4/samba-4.2.0#

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, 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 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:

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

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 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

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, 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

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-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 >

Hi all, I have a problem when I try to compil samba 4.0.6 on my test machine (suse linux enterprise server 11 SP2 32-bits). output of compilation : [3353/3781] Linking default/lib/param/libsamba-hostconfig.so [3354/3781] Linking default/lib/tdb_wrap/libtdb-wrap.so [3355/3781] Linking default/libcli/security/libsamba-security.so [3356/3781] Linking default/lib/util/libutil_tdb.so