similar to: PANIC outstanding aio + key does not exist

This turns out to be an SELinux issue. Does anyone know the proper commands to restorecon or otherwise to set the SELinux policy for persistent/volatile database files moved to a different directory? Martin or Amitay? On Wed, Nov 4, 2020 at 9:02 AM Robert Buck <robert.buck at som.com> wrote: > Running into problems configuring different locations for the volatile and > other

Running into problems configuring different locations for the volatile and other database directories. Can someone provide a quick sanity check on what I'm doing below? Thank you. Given [database] volatile database directory = /var/cache/dbdir/volatile persistent database directory = /var/cache/dbdir/persistent state database directory = /var/cache/dbdir/state And given, [root

Hi Bob, [CC: Amitay, who is better at SeLinux] On Wed, 4 Nov 2020 09:33:10 -0500, Robert Buck via samba <samba at lists.samba.org> wrote: > This turns out to be an SELinux issue. Does anyone know the proper commands > to restorecon or otherwise to set the SELinux policy for > persistent/volatile database files moved to a different directory? I'm not sure if you're asking

Hello Everyone! Here's what I'm trying to do. I'm working on generating occurrences of precipitation based upon precipitation occurrence for a station during the previous day and two stations that have already been generated by joint probablities and 1st order Markov chains or by the same generation process. This has to be done for each remaining stations for each month. > genmat

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

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

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

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

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

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

Hi, We come across a ScalarEvolution (SE) problem the other day. It seems to be a fundamental design problem. I don't think I have a clean and cheap fix to this problem. I talked with Andy in the phone yesterday, he told me it is a known fundamental problem. But I don't see any discussion on this problem on the list, so I post the problem here, soliciting your insightful comment.

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

Folks, thank you for being so helpful. I can't quite figure out the exact command line to get ctdb dbstatistics for the locking.tdb in CSV format. How do you do this? [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, dbstatistics locking.tdb --help Usage: [OPTION...] -d, --debug=STRING debug level -t, --timelimit=INT timelimit (in seconds) -n,

I could really need some help with this .... -> still problems here Am 2016-01-05 um 12:23 schrieb Stefan G. Weichinger: > 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]: >

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

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)

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