[Samba] Debugging Samba is a total PITA and this needs to improve

[L.P.H. van Belle]

Hai Sven, 

I do agree on somepoint here, but not all. 

First off all, samba does produce usefull reporting info. 
Depending on log levels you have set. ( man smb.conf /log level ). 

And then again we always have to ask, can you show the smb.conf. 
Not that i dont believe you have wrong setting but because i must see you have good setttings.

And the problem is not always/only samba, keep in mind that the current windows updates are not as stable as years ago. 
My personal opinion here, current windows updates are really bad in quality, but why is this... 
This is because MS is testing on users computers, that simple. 
You dont believe this.. 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\System 
The key used: (AllowExperimentation) 

About, client authentication failed... 
Windows 10, and are use useing SMB1 then disable the autoremove of smb1 in windows10. 
Dont forget, i use windows since windows 2.1, i've seen enough with windows. 

The current changes pointing at NTLM V1/V2 a lot has been done by MS and Samba.

Simple things changed.. For example 
https://support.microsoft.com/nl-nl/help/3181029/smb-file-server-share-access-is-unsuccessful-through-dns-cname-alias

I would preffer also to see a clear difference in settings in manuals for 
samba-AD-DC
samba-AD-Member-file server
samba-AD-Member-Print server
samba-AD-Member-authonly server 

Samba-NT4-PDC
Samba-NT4-BDC
Samba-NT4-Member

Samba-Standalone

Now, add to this the problem Rowland and i are looking into, found recently. 
A "renamed" computer, might have or is missing or has wrong settings in AD. 
A common problem we found yesterday, that also exists in windows itself and caused by windows clients.
And these found bugs found in windows are inherreted in samba, not always.. But in this case it is. 

Sorry if you feel bad about this but we are here to help, in such cases. 

So if you have ideas to improve the debugging.

This is on github.
https://github.com/thctlo/samba4/blob/master/samba-collect-debug-info.sh 
Fork/add you parts. 

And yes, the script really helps in quicker finding the problems. 
You can ask that here at list users.. 

So far.. Time to lunch.. 

Greetz, 

Louis







> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Sven 
> Schwedas via samba
> Verzonden: dinsdag 21 mei 2019 11:44
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] Debugging Samba is a total PITA and this 
> needs to improve
> 
> Once again, something with Samba thirty bazillion components broke. Once
> again, my choices for logging are "nothing" or "15 MB/s spread of ten
> different files, because 'client authentication failed' totally needs to
> be lower priority than malloc debug info". Once again, none of these
> messages is actually able to convey what broke, where, why. Why is it
> impossible for Samba to provide useful error reporting? How is anyone
> supposed to use this in production? Why is the only way we have to
> troubleshoot is having Rowland and LPH bike shedding over smb.conf
> formatting styles for two weeks until the problem randomly 
> solves itself?
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>