Web lists-archives.com

Re: [Samba] Troubleshooting help?




Thank you Rowland!  I guess that's part of my confusion, I'm not sure how to best debug where Centrify ends and Samba begins.  But if these log.smbd errors indicate Centrify vice Samba, I'm good with that.  My global smb.conf is (didn't bother with the commented out stuff):
[global]
security = ADS
realm = <our domain name>
workgroup = <our workgroup name>
netbios name = <the server name>
machine password timeout = 0
passdb backend = tdbsam:/var/lib/samba/private/passdb.tdb
kerberos method = secrets and keytab
server signing = auto
client ntlmv2 auth = yes
ntlm auth = yes
client use spnego = yes
template shell = /bin/bash
winbind use default domain = Yes
winbind enum users = No
winbind enum groups = No
winbind nested groups = Yes
idmap cache time = 0
idmap config * : backend = tdb
idmap config * : range = 1000 - 200000000
idmap config * : base_tdb = 0
enable core files = false
log level = 2
Scott

________________________________
From: samba <samba-bounces@xxxxxxxxxxxxxxx> on behalf of Rowland Penny via samba <samba@xxxxxxxxxxxxxxx>
Sent: Friday, January 25, 2019 10:49 PM
To: samba@xxxxxxxxxxxxxxx
Subject: Re: [Samba] Troubleshooting help?

On Fri, 25 Jan 2019 23:42:57 +0000
"Scott Z. via samba" <samba@xxxxxxxxxxxxxxx> wrote:

> I'm terribly sorry if this isn't the proper place/method by which to
> get help with troubleshooting Samba errors/issues, but it's the best
> one I could find.  I have an instance of Samba 4.8.3 running on a
> Centos 7.6 VM server (kernel 3.10.0-957.1.3), along with Centrify
> 5.5.2-578, that will allow folks to map a shared drive from their
> Windows 10 machines generally fine, but quite regularly throws a
> bunch of errors to the log.smbd file with stuff like the following:
>
> *** stack smashing detected ***; /usr/sbin/smbd terminated
> ../lib/util/fault.c:79(fault report)
> INTERNAL ERROR: singal 11 in pid .....
> Please read the Trouble-Shooting section of the Samba HOWTO
>
> These error messages have not proven to be very helpful, and I
> regularly get called in off-hours because users suddenly lose the
> ability to map to said share.  I've tried googling the heck out of
> the various cryptic error messages but haven't had much luck.
> Typically a quick restart of the centrifydc-samba service fixes it,
> bit this seems to happen every few weeks.  I don't know if there's an
> issue in my smb.conf or something else entirely happening, but if
> anyone has any troubleshooting tips or hints please let me know!
> Thanks! Scott
>
> p.s. - on same service I did a quick "systemctl status
> centrifydc-samba", and it shows a couple dozen pids
> with /usr/sbin/smbd next to them.  I have no idea what these are,
> aside from the obvious, but why are there so many?

Whilst this may be a Samba fault, it might not be, it might be an
interaction between Samba and Centrify. We do not provide Centrify and
therefore cannot provide support for it.

Having said that, Samba shouldn't crash, so can you provide us with a
bit more info, lets start with your smb.conf

Rowland

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba