similar to: Samba 4.7.1 Generating Core Dumps

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

I just noticed that smbclient from Samba 4.9.4 /built by myself) on FreeBSD 11.2 coredumps when called like this: smbclient -L <hostname> > % /liu/pkg/samba/4.9.4-liu/bin/smbclient -L filur00 > Enter username at AD.LIU.SE's password: > Abort (core dumped) … if it is linked against /usr/local/lib/libmd5.so (which is part of “libwww”). If I remove libmd5.so and recompile

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in

Hello, I have one question about the ALU scheduler. If for example I have one UNIFY volume which is using ALU scheduler with the following config: volume unify type cluster/unify option namespace afr-ns option scheduler rr option scheduler alu # use the ALU scheduler option alu.limits.min-free-disk 3% # Don't create files one a volume with less than 5% free diskspace

This is in regards to: https://bugzilla.samba.org/show_bug.cgi?id=11451 https://bugzilla.samba.org/show_bug.cgi?id=13008 Would it be possible to find out the current state of AES-GCM mode for file shares? Outside of Samba, CCM is typically slower and considered inferior to GCM I apologize for formatting issues, I typically don’t use email lists. In /source3/smbd/smb2_negprot.c lines 494 to

Original the array was attach to an HP server via a Smart Array Controller.(which I didn't setup, I just inherited the problem) This controller no longer recognizes the array even though the front panel of the array indicates its intact. I then took the array and plugged it into my Centos server and it recognized it ... cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun:

Hello ! I decided to upgrade my fileservers from stretch/samba 4.9 to buster/samba 4.11 I just realized that smbd is not working anymore :-/ If someone has an idea It would be amazing... as an idiot, I upgraded my 20 servers.... without snapshot.... Thank you so much Here's some logs : root at ef113:~# tail /var/log/samba/log.smbd #1

Hi all, Running into a problem with my gluster here in a LAB env. Production is a slightly different build(distributed replicated with multiple arbiter bricks) and I don't see the same errors...yet. I only seem to have this problem on 2 client vm's that I ran "setfattr -n trusted.io-stats-dump -v output_file_id mount_point" on while trying to test for latency issues. Curious

Hello, Came across a crash on samba-server(4.4) RHEL-7.3. (gdb) bt #0 0x00007f8e1e4821d7 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f8e1e4838c8 in __GI_abort () at abort.c:90 #2 0x00007f8e1fde2c4b in dump_core () at ../source3/lib/dumpcore.c:322 #3 0x00007f8e1fdd6007 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:814 #4

======================================================== "It's better to be a lion for a day than a sheep all your life." Elizabeth Kenny ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.10 release series. Changes since 4.10.12 ---------------------- o Jeremy

I just picked up rsync 2.5.6 and installed it. I haven't actually _used_ it for anything yet; this is entirely about a handful of minor issues I noticed while building it. You may care or you may not; for simplicity of language (to avoid many repeated "in case you care" and such), the text below is written assuming you care about them all. On a (32-bit) SPARC system, I noticed:

Hi All, can anyone make any sense of the error below, please advise if I need to log this as a bug but I'm not sure how to further diagnose what is happening. This is from my winbindd log file, thanks Andy. [2003/11/07 17:47:59, 1] nsswitch/winbindd.c:main(832) winbindd version 3.0.0 started. Copyright The Samba Team 2000-2003 [2003/11/07 17:48:00, 1]