I have a Debian 11.3, all up to date, running Samba to provide shares.
It authenticates against Windows AD using security=ADS
smbd -V reports 4.13.13-Debian
The problems with our shares vary.
With one user, mounting the share to their Windows system
produces segfaults on smbd. They can do small
transfers, but larger ones, say over 200MB, would fail.
It seems those transfer failures align with segfaults on smbd.
I see emails from root with tread debugging info for segfaults in smbd.
With myself, the mount works better. I can transfer the Debian ISO
back and forth over it. However, the progress meter goes to 100%
then says "an unspecified network error has occurred". If I click Try
Again
the transfer is redone, the file is over written and the second attempt is
perfect.
If I use smbclient on another Linux system, I see no errors at all.
I'm thinking, if I submitted a bug report, this isn't going to be
reproducible.
Also in many bug reports, people pick apart the config file and
say there was something wrong with it. So maybe I should begin there?
The system in question was upgraded from Debian 9 to 10 to 11 and we
had no issues with the older versions, while using a similar configuration.
Here is what we have from testparam output. I have replaced our domain name
as "example" or "EXAMPLE".
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_DOMAIN_MEMBER
Press enter to see a dump of your service definitions
# Global parameters
[global]
bind interfaces only = Yes
disable spoolss = Yes
dns proxy = No
interfaces = eth0
load printers = No
local master = No
log file = /var/log/samba/%m.log
max log size = 100
nt pipe support = No
obey pam restrictions = Yes
panic action = /usr/share/samba/panic-action %d
preferred master = No
printcap name = /dev/null
realm = AD.EXAMPLE.NET
security = ADS
server string = %h server
template shell = /bin/bash
winbind enum groups = Yes
winbind enum users = Yes
winbind refresh tickets = Yes
winbind use default domain = Yes
workgroup = EXAMPLE
idmap config * : range = 69998-69999
idmap config example : range = 70000-9999999999
idmap config example : backend = rid
idmap config * : backend = tdb
force create mode = 0744
force directory mode = 0755
hosts allow = 111.222.
nt acl support = No
[series]
force group = www
force user = www
path = /usr/local/series
read only = No
valid users = teddy dave ronald
[cms]
force group = www
force user = teddy
path = /usr/local/www/cms
read only = No
valid users = EXAMPLE\teddy EXAMPLE\ronald
On Wed, 2022-05-04 at 09:30 -0300, frank picabia via samba wrote:> I have a Debian 11.3, all up to date, running Samba to provide > shares. > It authenticates against Windows AD using security=ADS > smbd -V reports 4.13.13-Debian > > The problems with our shares vary. > > With one user, mounting the share to their Windows system > produces segfaults on smbd. They can do small > transfers, but larger ones, say over 200MB, would fail. > It seems those transfer failures align with segfaults on smbd. > > I see emails from root with tread debugging info for segfaults in > smbd. > > With myself, the mount works better. I can transfer the Debian ISO > back and forth over it. However, the progress meter goes to 100% > then says "an unspecified network error has occurred". If I click > Try Again > the transfer is redone, the file is over written and the second > attempt is > perfect. > > If I use smbclient on another Linux system, I see no errors at all. > > I'm thinking, if I submitted a bug report, this isn't going to be > reproducible. > Also in many bug reports, people pick apart the config file and > say there was something wrong with it. So maybe I should begin > there? > > The system in question was upgraded from Debian 9 to 10 to 11 and we > had no issues with the older versions, while using a similar > configuration. > > Here is what we have from testparam output. I have replaced our > domain name > as "example" or "EXAMPLE".Try the '[global]' section like this: [global] workgroup = EXAMPLE realm = AD.EXAMPLE.NET security = ADS server string = %h server bind interfaces only = Yes interfaces = eth0 hosts allow = 111.222. dns proxy = No winbind use default domain = yes winbind expand groups = 2 winbind refresh tickets = Yes idmap config * : backend = tdb idmap config * : range = 69998-69999 idmap config example : backend = rid idmap config example : range = 70000-9999999999 template shell = /bin/bash # user Administrator workaround, without it you are unable to set privileges username map = /etc/samba/user.map vfs objects = acl_xattr map acl inherit = Yes # Comment the following 4 lines to act as a print server printcap name = /dev/null load printers = no disable spoolss = yes printing = bsd # logging log file = /var/log/samba/%m.log logging = file max log size = 100 panic action = /usr/share/samba/panic-action %d Create /etc/samba/user.map containing this: !root = EXAMPLE\Administrator Change the shares to this: [series] path = /usr/local/series read only = No [cms] path = /usr/local/www/cms read only = No Then set the permissions from Windows or with setfacl (preferably Windows), see here for more info: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs https://wiki.samba.org/index.php/Setting_up_a_Share_Using_POSIX_ACLs While Samba shouldn't segfault, this may be a Windows problem. Rowland
If this still happens after the suggested changes from Rowland. Then I suggest to try the 4.15.7 packages of my repo. I seen this also but some time ago. I think this was something with locking.. greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba Namens Rowland Penny via samba > Verzonden: woensdag 4 mei 2022 15:22 > Aan: samba at lists.samba.org > CC: Rowland Penny <rpenny at samba.org> > Onderwerp: Re: [Samba] Best way to get to bottom of odd failures? > > On Wed, 2022-05-04 at 09:30 -0300, frank picabia via samba wrote: > > I have a Debian 11.3, all up to date, running Samba to provide > > shares. > > It authenticates against Windows AD using security=ADS > > smbd -V reports 4.13.13-Debian > > > > The problems with our shares vary. > > > > With one user, mounting the share to their Windows system > > produces segfaults on smbd. They can do small > > transfers, but larger ones, say over 200MB, would fail. > > It seems those transfer failures align with segfaults on smbd. > > > > I see emails from root with tread debugging info for segfaults in > > smbd. > > > > With myself, the mount works better. I can transfer the Debian ISO > > back and forth over it. However, the progress meter goes to 100% > > then says "an unspecified network error has occurred". If I click > > Try Again > > the transfer is redone, the file is over written and the second > > attempt is > > perfect. > > > > If I use smbclient on another Linux system, I see no errors at all. > > > > I'm thinking, if I submitted a bug report, this isn't going to be > > reproducible. > > Also in many bug reports, people pick apart the config file and > > say there was something wrong with it. So maybe I should begin > > there? > > > > The system in question was upgraded from Debian 9 to 10 to 11 and we > > had no issues with the older versions, while using a similar > > configuration. > > > > Here is what we have from testparam output. I have replaced our > > domain name > > as "example" or "EXAMPLE". > > Try the '[global]' section like this: > [global] > workgroup = EXAMPLE > realm = AD.EXAMPLE.NET > security = ADS > server string = %h server > > bind interfaces only = Yes > interfaces = eth0 > hosts allow = 111.222. > dns proxy = No > > winbind use default domain = yes > winbind expand groups = 2 > winbind refresh tickets = Yes > > idmap config * : backend = tdb > idmap config * : range = 69998-69999 > idmap config example : backend = rid > idmap config example : range = 70000-9999999999 > template shell = /bin/bash > > # user Administrator workaround, without it you are unable to > set privileges > username map = /etc/samba/user.map > > vfs objects = acl_xattr > map acl inherit = Yes > > # Comment the following 4 lines to act as a print server > printcap name = /dev/null > load printers = no > disable spoolss = yes > printing = bsd > > # logging > log file = /var/log/samba/%m.log > logging = file > max log size = 100 > > panic action = /usr/share/samba/panic-action %d > > Create /etc/samba/user.map containing this: > > !root = EXAMPLE\Administrator > > Change the shares to this: > > [series] > path = /usr/local/series > read only = No > > [cms] > path = /usr/local/www/cms > read only = No > > Then set the permissions from Windows or with setfacl (preferably > Windows), see here for more info: > > https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_A > CLs > https://wiki.samba.org/index.php/Setting_up_a_Share_Using_POSIX_ACLs > > While Samba shouldn't segfault, this may be a Windows problem. > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba