similar to: Crash on samba-server(4.4) .. Some Queries

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

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 have successfully compiled and installed Samba 4.0.0rc2 on Debian Squeeze as described in the Wiki. In order to support Win XP and Win 7 clients, I have created GPOs for folders redirection. The problem I am facing is with random PANIC messages in the logs and logon/logoff/file access process gets hung on the client. Here are the logs: Oct 18 13:42:32 pdc smbd[27384]: [2012/10/18

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

I've got a CTDB 2.5.2 Samba 4.1.5 cluster where I'm seeing smbd processes using too much CPU after the client connection is closed. Doing a truss against the smbd processes shows nothing during this time, so no syscalls seem to be involved. I rebuilt with debug enabled and took stack traces from an offending process spaces about 1 minute apart. Can anyone from the team tell me if

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

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

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

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

> 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

Hi, when I don't want to switch to Active Directory, but don't want to be stuck on version 3.6 either, can I simply give samba 4 a copy of the old smb.conf file? Will it be able to store all windows acl's in extended attributes, or is this improvement only available in combination with letting it run as active directory domain controller? thanks, Klaus

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]

Hi Team, Trying to upgrade samba 4.9.3 on debian wheezy. while building facing the following error. Build phase! ` Configuring Samba 4 - x86_64 Checking for program gcc or cc : /usr/bin/gcc Checking for program cpp : not found Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for gcc