Daniel Carrasco Marín
2015-Dec-16 09:25 UTC
[Samba] domain authentication issue after rebooting Debian Jessie - need to restart samba each time
Hi again, i've restarted my server to check if fails and is working fine. My specifications are: - Debian 8u6 jessie 3.16.0-4-amd64 - Samba version 4.2.5-SerNet-Debian-8.jessie - DNS Backend Bind ¡Greetings! El 16/12/15 a las 09:44, L.P.H. van Belle escribió:> Devuan.. a thing im going to have a look into. > I do get why debian is swithching to systemd.. really much better control of the startup process, but yeah, lots harder to configure... > > > Besides that... > This is a samba using internal DNS? > > Can you also post the output of > systemctl list-dependencies samba-ad-dc > or > systemctl list-dependencies > > and post > systemctl show samba-ad-dc.service | egrep "After|ExecS" > > as already requested the content of smb.conf > > > > Greez, > > Louis > >> -----Oorspronkelijk bericht----- >> Van: gimili [mailto:gimili17 at gmail.com] >> Verzonden: dinsdag 15 december 2015 19:31 >> Aan: L.P.H. van Belle; samba at lists.samba.org >> Onderwerp: Re: [Samba] domain authentication issue after rebooting Debian >> Jessie - need to restart samba each time >> >> On 12/15/2015 12:13 PM, L.P.H. van Belle wrote: >>> Hai, >>> >>> If not, well, very stange, i have about 7 Jessie's here with samba and >>> i dont have any problems. >>> I think systemd is blocking your startup of samba due to multple errors >> on startups previously. >>> Few questions? >>> >>> Do you have samba with shares over nfs? >>> If so, create te following folder : >>> /etc/systemd/system/nfs-common.service.d/ >>> >>> Add the following file with content to the file : remote-fs-pre.conf >>> [Unit] >>> Before=remote-fs-pre.target >>> Wants=remote-fs-pre.target >>> >>> >>> What is the output of ? >>> systemctl status samba-ad-dc >>> >>> if its masked.. then type :' >>> systemctl unmask samba-ad-dc >>> and >>> systemctl restart samba-ad-dc >>> reboot and see if its all started. >>> Greetz, >>> >>> Louis >>> >> Still no luck. Maybe I am back to a delayed start using /etc/rc.local. >> Good to know it is working for someone. I must have done something >> wrong. Perhaps I will start from scratch. >> >> >systemctl status samba-ad-dc >> >> â samba-ad-dc.service - LSB: start Samba daemons for the AD DC >> Loaded: loaded (/etc/init.d/samba-ad-dc) >> Active: active (running) since Tue 2015-12-15 13:14:43 EST; 11min ago >> CGroup: /system.slice/samba-ad-dc.service >> ââ846 /usr/sbin/samba -D >> ââ900 /usr/sbin/samba -D >> ââ901 /usr/sbin/samba -D >> ââ902 /usr/sbin/samba -D >> ââ903 /usr/sbin/samba -D >> ââ904 /usr/sbin/samba -D >> ââ905 /usr/sbin/smbd -D --option=server role >> check:inhibit=yes --foreground >> ââ906 /usr/sbin/samba -D >> ââ907 /usr/sbin/samba -D >> ââ908 /usr/sbin/samba -D >> ââ909 /usr/sbin/samba -D >> ââ910 /usr/sbin/samba -D >> ââ911 /usr/sbin/samba -D >> ââ912 /usr/sbin/samba -D >> ââ913 /usr/sbin/samba -D >> ââ938 /usr/sbin/smbd -D --option=server role >> check:inhibit=yes --foreground >> >> Dec 15 13:14:43 bob.ad.test.org samba[841]: [2015/12/15 >> 13:14:43.398943, 0] ../source4/smbd/server.c:370(binary_smbd_main) >> Dec 15 13:14:43 bob.ad.test.org samba[841]: samba version 4.1.17-Debian >> started. >> Dec 15 13:14:43 bob.ad.test.org samba[841]: Copyright Andrew Tridgell >> and the Samba Team 1992-2013 >> Dec 15 13:14:43 bob.ad.test.org samba-ad-dc[471]: Starting Samba AD DC >> daemon: samba. >> Dec 15 13:14:43 bob.ad.test.org samba[846]: [2015/12/15 >> 13:14:43.782455, 0] ../source4/smbd/server.c:488(binary_smbd_main) >> Dec 15 13:14:43 bob.ad.test.org samba[846]: samba: using 'standard' >> process model >> Dec 15 13:14:43 bob.ad.test.org samba[846]: [2015/12/15 >> 13:14:43.829676, 0] ../lib/util/become_daemon.c:136(daemon_ready) >> Dec 15 13:14:44 bob.ad.test.org smbd[905]: [2015/12/15 13:14:44.332073, >> 0] ../lib/util/become_daemon.c:136(daemon_ready) >> Dec 15 13:25:03 bob.ad.test.org samba[912]: [2015/12/15 >> 13:25:03.932432, 0] >> ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) >> Dec 15 13:25:03 bob.ad.test.org samba[912]: >> ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - >> NT_STATUS_IO_TIMEOUT >> >> - >> gimili > >
gimili
2015-Dec-18 13:07 UTC
[Samba] domain authentication issue after rebooting Debian Jessie - need to restart samba each time
On 12/16/2015 4:25 AM, Daniel Carrasco Marín wrote:> Hi again, i've restarted my server to check if fails and is working > fine. My specifications are: > > - Debian 8u6 jessie 3.16.0-4-amd64 > - Samba version 4.2.5-SerNet-Debian-8.jessie > - DNS Backend BindThanks. Good to know. I may just start again from scratch. Probably I missed something. -- gimili
L.P.H. van Belle
2015-Dec-18 13:54 UTC
[Samba] domain authentication issue after rebooting Debian Jessie - need to restart samba each time
Gimili is using internal dns.. I use bind dns. Daniel used bind dns. So if you up to it gimili, upgrade your internal dns to bind. And test again. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens gimili > Verzonden: vrijdag 18 december 2015 14:07 > Aan: Daniel Carrasco Marín; samba at lists.samba.org > Onderwerp: Re: [Samba] domain authentication issue after rebooting Debian > Jessie - need to restart samba each time > > On 12/16/2015 4:25 AM, Daniel Carrasco Marín wrote: > > Hi again, i've restarted my server to check if fails and is working > > fine. My specifications are: > > > > - Debian 8u6 jessie 3.16.0-4-amd64 > > - Samba version 4.2.5-SerNet-Debian-8.jessie > > - DNS Backend Bind > > Thanks. Good to know. I may just start again from scratch. Probably I > missed something. > > -- > gimili > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
gimili
2016-Jan-04 19:42 UTC
[Samba] domain authentication issue after rebooting Debian Jessie - need to restart samba each time
I switched from an intel ssd hard drive to an old mechanical hard drive and now it works fine. Everything starts when I reboot (tested 3 times). I then copied mechanical back to the intel SSD and problem started again. On reboot things do not work. Could this be a bug? BTW: Thank you kindly for all the previous help and ideas. Much appreciated. -- gimili