Edouard Guigné
2020-Apr-30 14:11 UTC
[Samba] Service Winbind stopped, what could be the reason ?
Hello Rowland, I had a look on message log, when the winbind stopped. I found that an system update occured during the night, and then Winbind did not restart properly. ... /Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: samba-winbind-clients.x86_64 4.10.4-10.el7// //Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: samba-winbind-krb5-locator.x86_64 4.10.4-10.el7// //Apr 28 04:33:09 [localhost] yum[1232]: Mis ? jour?: samba.x86_64 4.10.4-10.el7/ ... /Apr 28 08:07:53 [localhost] systemd-logind: New session 79900 of user root.// //Apr 28 08:08:26 [localhost] systemd: Starting Samba SMB Daemon...// //Apr 28 08:08:26 [localhost] smbd[4611]: [2020/04/28 08:08:26.248346,? 0] ../../lib/util/become_daemon.c:136(daemon_ready)// //Apr 28 08:08:26 [localhost] smbd[4611]:? daemon_ready: daemon 'smbd' finished starting up and ready to serve connections// //Apr 28 08:08:26 [localhost] systemd: Started Samba SMB Daemon.// /*/Apr 28 08:08:51 [localhost] smbd[4625]: [2020/04/28 08:08:51.228010,? 0] ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ /**/Apr 28 08:08:51 [localhost] smbd[4625]: check_winbind_security: winbindd not running - but required as domain member: NT_STATUS_NO_LOGON_SERVERS/**/ /**/Apr 28 08:08:51 [localhost] smbd[4626]: [2020/04/28 08:08:51.251448,? 0] ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ /**/Apr 28 08:08:51 [localhost] smbd[4626]: check_winbind_security: winbindd not running - but required as domain member: NT_STATUS_NO_LOGON_SERVERS/* ... When I restarted Winbind : /Apr 28 08:15:01 [localhost] systemd: Started Session 79902 of user root.// //Apr 28 08:15:18 [localhost] systemd: Stopping Samba Winbind Daemon...// //Apr 28 08:15:18 [localhost] winbindd[3915]: [2020/04/28 08:15:18.356936,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[3915]:? Got sig[15] terminate (is_parent=1)// //Apr 28 08:15:18 [localhost] winbindd[4084]: [2020/04/28 08:15:18.357134,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[4084]:? Got sig[15] terminate (is_parent=0)// //Apr 28 08:15:18 [localhost] winbindd[4279]: [2020/04/28 08:15:18.357085,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[4279]:? Got sig[15] terminate (is_parent=0)// //Apr 28 08:15:18 [localhost] winbindd[4082]: [2020/04/28 08:15:18.368710,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[4082]:? Got sig[15] terminate (is_parent=0)// //Apr 28 08:15:18 [localhost] winbindd[4022]: [2020/04/28 08:15:18.357031,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[4022]:? Got sig[15] terminate (is_parent=0)// //Apr 28 08:15:18 [localhost] winbindd[4075]: [2020/04/28 08:15:18.371589,? 0] ../source3/winbindd/winbindd.c:239(winbindd_sig_term_handler)// //Apr 28 08:15:18 [localhost] winbindd[4075]:? Got sig[15] terminate (is_parent=0)// //Apr 28 08:15:18 [localhost] systemd: Stopped Samba Winbind Daemon.// //Apr 28 08:15:18 [localhost] systemd: Starting Samba Winbind Daemon...// //Apr 28 08:15:18 [localhost] winbindd[4731]: [2020/04/28 08:15:18.896997,? 0] ../../source3/winbindd/winbindd_cache.c:3166(initialize_winbindd_cache)// //Apr 28 08:15:18 [localhost] winbindd[4731]: initialize_winbindd_cache: clearing cache and re-creating with version number 2// //Apr 28 08:15:18 [localhost] winbindd[4731]: [2020/04/28 08:15:18.915444,? 0] ../../lib/util/become_daemon.c:136(daemon_ready)// //Apr 28 08:15:18 [localhost] winbindd[4731]:? daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections// //Apr 28 08:15:18 [localhost] systemd: Started Samba Winbind Daemon./ Can it sometimes happen that winbind do not restart properly after automatic system update ? Best regards, Ed Le 28/04/2020 ? 13:11, Rowland penny via samba a ?crit?:> On 28/04/2020 16:25, Edouard Guign? wrote: >> Dear Rowland, >> >> Please find a dump of smb.conf and resolv.conf of my centos 7 server : >> > Nothing really wrong in your smb.conf, except: > > ??????? winbind nss info = rfc2307 > > That isn't used any more. > > ?????? cups options = raw > > You have turned printing off > > ??????? valid users = "@MYAD\utilisateurs du domaine" > > Your workgroup is 'IPGAD' so 'MYAD' should be 'IPGAD', but even better > would be to set the permissions from windows. > > Your major problem is your resolv.conf, it should have a line: > > search myad.mydomain.fr > > I take it that your computer gets its dns info via DHCP, so you need > to find out how to ensure that network manager creates that line in > resolv.conf. > > Rowland > > >
Rowland penny
2020-Apr-30 14:30 UTC
[Samba] Service Winbind stopped, what could be the reason ?
On 30/04/2020 15:11, Edouard Guign? wrote:> > Hello Rowland, > > I had a look on message log, when the winbind stopped. > I found that an system update occured during the night, and then > Winbind did not restart properly. > > ... > /Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: > samba-winbind-clients.x86_64 4.10.4-10.el7// > //Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: > samba-winbind-krb5-locator.x86_64 4.10.4-10.el7// > //Apr 28 04:33:09 [localhost] yum[1232]: Mis ? jour?: samba.x86_64 > 4.10.4-10.el7/ > > ... > > /Apr 28 08:07:53 [localhost] systemd-logind: New session 79900 of user > root.// > //Apr 28 08:08:26 [localhost] systemd: Starting Samba SMB Daemon...// > //Apr 28 08:08:26 [localhost] smbd[4611]: [2020/04/28 > 08:08:26.248346,? 0] ../../lib/util/become_daemon.c:136(daemon_ready)// > //Apr 28 08:08:26 [localhost] smbd[4611]:? daemon_ready: daemon 'smbd' > finished starting up and ready to serve connections// > //Apr 28 08:08:26 [localhost] systemd: Started Samba SMB Daemon.// > /*/Apr 28 08:08:51 [localhost] smbd[4625]: [2020/04/28 > 08:08:51.228010,? 0] > ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ > /**/Apr 28 08:08:51 [localhost] smbd[4625]: check_winbind_security: > winbindd not running - but required as domain member: > NT_STATUS_NO_LOGON_SERVERS/**/ > /**/Apr 28 08:08:51 [localhost] smbd[4626]: [2020/04/28 > 08:08:51.251448,? 0] > ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ > /**/Apr 28 08:08:51 [localhost] smbd[4626]: check_winbind_security: > winbindd not running - but required as domain member: > NT_STATUS_NO_LOGON_SERVERS/* > > ... > > Can it sometimes happen that winbind do not restart properly after > automatic system update ? >It looks like you have found your problem, but I am the last person to provide an answer, I am one of the luddites who refuses to use systemd ;-) It looks like windbind needs to start before smbd, but how you would do this, I have no idea. Rowland
L.P.H. van Belle
2020-Apr-30 15:11 UTC
[Samba] Service Winbind stopped, what could be the reason ?
Apr 28 08:08:26 [localhost] << Servername is localhost ? Thats first error thats needs fixing.> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: donderdag 30 april 2020 16:31 > Aan: samba > Onderwerp: Re: [Samba] Service Winbind stopped, what could be > the reason ? > > On 30/04/2020 15:11, Edouard Guign? wrote: > > > > Hello Rowland, > > > > I had a look on message log, when the winbind stopped. > > I found that an system update occured during the night, and then > > Winbind did not restart properly. > > > > ... > > /Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: > > samba-winbind-clients.x86_64 4.10.4-10.el7// > > //Apr 28 04:33:08 [localhost] yum[1232]: Mis ? jour?: > > samba-winbind-krb5-locator.x86_64 4.10.4-10.el7// > > //Apr 28 04:33:09 [localhost] yum[1232]: Mis ? jour?: samba.x86_64 > > 4.10.4-10.el7/ > > > > ... > > > > /Apr 28 08:07:53 [localhost] systemd-logind: New session > 79900 of user > > root.// > > //Apr 28 08:08:26 [localhost] systemd: Starting Samba SMB > Daemon...// > > //Apr 28 08:08:26 [localhost] smbd[4611]: [2020/04/28 > > 08:08:26.248346,? 0] > ../../lib/util/become_daemon.c:136(daemon_ready)// > > //Apr 28 08:08:26 [localhost] smbd[4611]:? daemon_ready: > daemon 'smbd' > > finished starting up and ready to serve connections// > > //Apr 28 08:08:26 [localhost] systemd: Started Samba SMB Daemon.// > > /*/Apr 28 08:08:51 [localhost] smbd[4625]: [2020/04/28 > > 08:08:51.228010,? 0] > > ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ > > /**/Apr 28 08:08:51 [localhost] smbd[4625]: check_winbind_security: > > winbindd not running - but required as domain member: > > NT_STATUS_NO_LOGON_SERVERS/**/ > > /**/Apr 28 08:08:51 [localhost] smbd[4626]: [2020/04/28 > > 08:08:51.251448,? 0] > > ../../source3/auth/auth_winbind.c:122(check_winbind_security)/**/ > > /**/Apr 28 08:08:51 [localhost] smbd[4626]: check_winbind_security: > > winbindd not running - but required as domain member: > > NT_STATUS_NO_LOGON_SERVERS/* > > > > ... > > > > Can it sometimes happen that winbind do not restart properly after > > automatic system update ? > > > It looks like you have found your problem, but I am the last > person to > provide an answer, I am one of the luddites who refuses to > use systemd ;-) > > It looks like windbind needs to start before smbd, but how > you would do > this, I have no idea. > > Rowland > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
miguel medalha
2020-Apr-30 21:21 UTC
[Samba] Service Winbind stopped, what could be the reason ?
> It looks like windbind needs to start before smbd, but how you would do > this, I have no idea.The systemd service files included with the Samba source code (under 'packaging/systemd') contain the instructions needed: For winbindd: 'After=network.target nmb.service' For smbd: 'After=network.target network-online.target nmb.service winbind.service'