[Samba] CentOS update broke Samba

Sat Oct 19 20:46:41 UTC 2019

On 19/10/2019 21:28, Alex Moen via samba wrote:
>
>
> On 10/19/19 2:57 PM, Rowland penny via samba wrote:
>
> Guest account: There isn't a Unix user per se, but there is an LDAP 
> user named guest that I created for this purpose...  I don't really 
> want guest access.  Again, something legacy?
No, the guest user is usually a Unix user (usually 'nobody')
>
> As far as I can tell, winbind is running:
>
> [root at ndtc-fs ~]# systemctl status winbind
> ● winbind.service - Samba Winbind Daemon
>    Loaded: loaded (/usr/lib/systemd/system/winbind.service; enabled; 
> vendor preset: disabled)
>    Active: active (running) since Sat 2019-10-19 15:19:55 CDT; 2min 
> 17s ago
>      Docs: man:winbindd(8)
>            man:samba(7)
>            man:smb.conf(5)
>  Main PID: 7460 (winbindd)
>    Status: "winbindd: ready to serve connections..."
>    CGroup: /system.slice/winbind.service
>            ├─7460 /usr/sbin/winbindd --foreground --no-process-group
>            ├─7498 /usr/sbin/winbindd --foreground --no-process-group
>            ├─7499 /usr/sbin/winbindd --foreground --no-process-group
>            └─7547 /usr/sbin/winbindd --foreground --no-process-group
>
> Oct 19 15:19:54 ndtc-fs systemd[1]: Stopped Samba Winbind Daemon.
> Oct 19 15:19:54 ndtc-fs systemd[1]: Starting Samba Winbind Daemon...
> Oct 19 15:19:55 ndtc-fs winbindd[7460]: [2019/10/19 15:19:55.019096,  
> 0] ../source3/winbindd/winbindd_cache.c:3160(init...cache)
> Oct 19 15:19:55 ndtc-fs winbindd[7460]: initialize_winbindd_cache: 
> clearing cache and re-creating with version number 2
> Oct 19 15:19:55 ndtc-fs winbindd[7460]: [2019/10/19 15:19:55.024290,  
> 0] ../lib/util/become_daemon.c:138(daemon_ready)
> Oct 19 15:19:55 ndtc-fs systemd[1]: Started Samba Winbind Daemon.
> Oct 19 15:19:55 ndtc-fs winbindd[7460]:   daemon_ready: STATUS=daemon 
> 'winbindd' finished starting up and ready to serv...ctions
> Oct 19 15:20:23 ndtc-fs winbindd[7499]: [2019/10/19 15:20:23.939396,  
> 0] ../source3/winbindd/idmap_autorid.c:822(idmap_...alize)
> Oct 19 15:20:23 ndtc-fs winbindd[7499]: idmap_autorid_initialize: 
> Error: autorid configured for domain 'a36561'. But ...ation.
> Hint: Some lines were ellipsized, use -l to show in full.
>
> As well as SMB and NMB:
>
> [root at ndtc-fs ~]# systemctl status nmb
> ● nmb.service - Samba NMB Daemon
>    Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled; 
> vendor preset: disabled)
>    Active: active (running) since Sat 2019-10-19 15:20:19 CDT; 2min 3s 
> ago
>      Docs: man:nmbd(8)
>            man:samba(7)
>            man:smb.conf(5)
>  Main PID: 7483 (nmbd)
>    Status: "nmbd: ready to serve connections..."
>    CGroup: /system.slice/nmb.service
>            ├─7483 /usr/sbin/nmbd --foreground --no-process-group
>            └─7484 /usr/sbin/nmbd --foreground --no-process-group
>
> Oct 19 15:20:27 ndtc-fs nmbd[7483]:
> Oct 19 15:20:27 ndtc-fs nmbd[7483]:   Samba server NDTC-FS is now a 
> domain master browser for workgroup A36561 on subne...8.255.5
> Oct 19 15:20:27 ndtc-fs nmbd[7483]:
> Oct 19 15:20:27 ndtc-fs nmbd[7483]:   *****
> Oct 19 15:20:42 ndtc-fs nmbd[7483]: [2019/10/19 15:20:42.367309, 0] 
> ../source3/nmbd/nmbd_become_lmb.c:397(become_local...stage2)
> Oct 19 15:20:42 ndtc-fs nmbd[7483]:   *****
> Oct 19 15:20:42 ndtc-fs nmbd[7483]:
> Oct 19 15:20:42 ndtc-fs nmbd[7483]:   Samba name server NDTC-FS is now 
> a local master browser for workgroup A36561 on s...8.255.5
> Oct 19 15:20:42 ndtc-fs nmbd[7483]:
> Oct 19 15:20:42 ndtc-fs nmbd[7483]:   *****
> Hint: Some lines were ellipsized, use -l to show in full.
>
> [root at ndtc-fs ~]# systemctl status sm
> ● smb.service - Samba SMB Daemon
>    Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; 
> vendor preset: disabled)
>    Active: active (running) since Sat 2019-10-19 15:20:23 CDT; 2min 4s 
> ago
>      Docs: man:smbd(8)
>            man:samba(7)
>            man:smb.conf(5)
>  Main PID: 7493 (smbd)
>    Status: "smbd: ready to serve connections..."
>    CGroup: /system.slice/smb.service
>            ├─7493 /usr/sbin/smbd --foreground --no-process-group
>            ├─7495 /usr/sbin/smbd --foreground --no-process-group
>            ├─7496 /usr/sbin/smbd --foreground --no-process-group
>            ├─7500 /usr/sbin/smbd --foreground --no-process-group
>            ├─7502 /usr/sbin/smbd --foreground --no-process-group
>            ├─7508 /usr/sbin/smbd --foreground --no-process-group
>            ├─7510 /usr/sbin/smbd --foreground --no-process-group
>            └─7512 /usr/sbin/smbd --foreground --no-process-group
>
> Oct 19 15:20:23 ndtc-fs systemd[1]: Stopped Samba SMB Daemon.
> Oct 19 15:20:23 ndtc-fs systemd[1]: Starting Samba SMB Daemon...
> Oct 19 15:20:23 ndtc-fs smbd[7493]: [2019/10/19 15:20:23.953291, 0] 
> ../lib/util/become_daemon.c:138(daemon_ready)
> Oct 19 15:20:23 ndtc-fs systemd[1]: Started Samba SMB Daemon.
> Oct 19 15:20:23 ndtc-fs smbd[7493]:   daemon_ready: STATUS=daemon 
> 'smbd' finished starting up and ready to serve connections
>
> I still cannot connect with Linux machines.  It's really not that big 
> of a deal (since I can use SSH/SFTP), but I just am concerned that 
> there may be other issues if it isn't "fully functional", and that 
> other clients may be affected.

I think you are running into this bug:

https://bugzilla.samba.org/show_bug.cgi?id=13697

However, can I strongly urge you to upgrade your NT4-style domain to an 
AD domain, Microsoft has broken these twice (and repaired them) to my 
knowledge, perhaps next time they will not fix them. Microsoft is also 
moving away from the protocols that NT4-style domains rely on.

Rowland