similar to: Crash after Update to 4.12.1 with vfs full_audit

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

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 shares). I have no problems with Windows clients, but several strange things are happening with Macs.

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]

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

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

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

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

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:

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]

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

Hi all! Is it possible to run smbd in an AD user's context? If not, is it possible to have smbd to tell a third-party function to not stray outside from logged on user's (AD user) context (home directory)? I'm programming a VFS module[1] which will be the bridge between Windows and iRODS[2]. iRODS depends on a configuration file, .irods/irods_environment.json, which resides in the

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