similar to: Help with Possible Bug in Samba 4.1.5 on Connection Close

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

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

I have had a problem for a couple of weeks now. I get very regular crashes on two of my three Domain Controllers. I just updated to 4.1.0 and I am still getting the same problem. I have added panic action = /bin/sleep 99999 to my config. Here is a back trace for the crash. (gdb) bt #0 0x003c3424 in __kernel_vsyscall () #1 0xb76fa363 in __waitpid_nocancel () at

> 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

Hello, This is a problem with both samba 4.3.3 and 4.3.4. I have a crash that seems triggered after a NT_STATUS_DENIED on a chdir operation. After that the server begins to shutdown itself with the message "Server exit (failed to receive smb request)", to close all the connections and when closing it crashes due a talloc error. I cannot reproduce myself this error and it occurs

Since upgrading to 3.6.1 in Debian testing, I receive a panic/segfault message with each print job. Printing succeeds and continues to work, but an email with the info below is sent each time. The system is standalone. Kernel is 3.1.0-1-686-pae, and the system is fully updated. testparm returns no errors. Does this mean anything to anyone? Dale [Thread debugging using libthread_db

Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O

Hi Amir, this is a known and fixed issue in Samba 3.6.6. It was known as Bug 9004 https://bugzilla.samba.org/show_bug.cgi?id=9004 and has been fixed by o Andreas Schneider <asn at samba.org> * BUG 8944 and 8567: Don't lookup the system user in pdb. Do you need a patch for 3.6.1? As far as I know (I would need to test it) with this patch Samba logs that the configured guest user

Samba has been running great but now I'm seeing a problem. Been compiling from git 4-4-test, but even 4-4.stable (4.4.5) has the same issue. I've tried to follow the troubleshooting guide and this is what I come up with: # nmbd -FS nmbd version 4.4.6-GIT-1305ba6 started. Copyright Andrew Tridgell and the Samba Team 1992-2016 STATUS=daemon 'nmbd' finished starting up and ready to

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

Hi, I'm trying to use the samba4 registry tools for server-side editing of HKCU (ntuser.dat) on a Debian Etch samba 3 server. I was very pleased to see that backporting Debian experimental's samba4 package was very easy, so now I have a backported-to-Etch registry-tools package to start experiments : - regshell -F ntuser.dat works, one can manually add, remove, modify keys and

We've a Samba 4 domain (no AD, just DC) with LDAP backend on Ubuntu 14.04. This server has been migrated from files backend to LDAP by the previous maintainer, I know the version is pretty old but we cannot update at the moment. The domain works fine with some W7 and W10 (updated from 7) computers, but we have purchased a new Lenovo laptop with Win10 which joined the domain seamlessly but

Hello, I'm faced with an issue that I tried to solve myself for some time, but i'm now totally clueless, hence requesting your help. I have a Samba4 running on a CentOS 7 server. >From Windows 10 client, it's working great (except I'm seeing some core dumps from time to time), I can authenticate and access to the server and browse the shared folder. The problem appears when

Hi, We are having issues with our samba server running on CentOS 7. It's generating core dumps and dumping them in the / (root filesystem) directory in the form of core.##### where the # is a series of numbers. Snippets of log files and some troubleshooting commands are below. Hope someone can have a look and see if I should file this as a bug, as there were similar posts in the samba

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, can't seem to login to Samba Server using notebook. OS is FreeBSD 10.3. Samba Version is 4.6.6 Connect to the remote Samba server using L2TP/IPSec connection. When trying to login it's not accepting the correct credentials. When ssh'ing to the server can login without any issue: # smbclient -Uusername //server/share Enter SERVERNAME\username's password: Domain=[DOMAINNAME]

Hello, I had been running Samba 4.8 for a few years without any problems, and then upgraded to 4.10. Since then I?ve been having problems with some accounts connecting, while some connect fine still. I haven?t been able to figure out why. My server is a relatively simple standalone server, using the LDAP password backend. A failing user authenticates OK and ends up like this in the logs:

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

> On Fri, Aug 26, 2016 at 12:19:30PM -0400, Thomas Schulz via samba wrote: > > I am testing Samba 4.5.0rc2 on a Solaris 10 i386 box. log.smbd contains > > a new message/error that does not show up on Samba 4.4.5. The error is: > > > > [2016/08/26 11:45:54.886237, 0] > > ../source3/rpc_server/rpc_service_setup.c:539(dcesrv_ep_setup) > > dcesrv_ep_setup:

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