similar to: bind named fails after logrotate

Displaying 20 results from an estimated 5000 matches similar to: "bind named fails after logrotate"

2018 Jun 09
0
Problem with named.service
Good morning! I followed your instructions Rowland, but still showme the same error: I change this lines in smb.conf: smb.conf file [global]        netbios name = PC         realm = DOMAIN.LOCAL         server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate         workgroup = DOMAIN         server role = active directory DOMAIN controller        
2018 May 14
1
Logrotate
Am 14.05.2018 um 21:08 schrieb Reindl Harald via samba: > Am 14.05.2018 um 20:56 schrieb Carlos via samba: >> /opt/samba/var/log.samba >> >> { >>   rotate 10 >>         daily >>         compress >>         dateext >>         size 100M >>         nomail >>         missingok >>         notifempty >>         create 644 root
2018 Jun 09
3
Problem with named.service
Good morning! I followed your instructions Rowland, but still showme the same error: I change this lines in smb.conf: server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, > drepl, winbindd, ntp_signd, kcc, dnsupdate, dns For this one: server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, > drepl, winbindd, ntp_signd, kcc, dnsupdate [root at pc ~]# systemctl status named.service●
2018 Mar 13
1
Workaround for bind9 reload bug : samba_dlz Ignoring duplicate zone
Sorry, Louis, not all of us use systemd. > Almost Harry... > > For debian Stretch. # cat /etc/debian_version buster/sid # cat /proc/1/cmdline /sbin/init You see: good old init. Just a test machine for a scheduled upgrade. > systemctl cat bind9 > # /lib/systemd/system/bind9.service > [Unit] > Description=BIND Domain Name Server > Documentation=man:named(8) >
2018 Jun 08
0
Problem with named.service
Sorry, I forgot to attach the command line error: [root at pc ~]# systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS)    Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)    Active: active (running) since Thu 2018-06-07 21:15:06 AST; 20h ago   Process: 12495 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1
2016 Oct 16
0
bind9 won't run
On Sun, 16 Oct 2016 12:38:00 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with > Bind9_DLZ. > > I have one machine just like this one. Same hardware, same software > setup. First machine is working fine. > > At the moment this (second) machine is not joined to the other
2015 Apr 02
0
systemctl (again)
It might be SELinux. On a standard system; when we run things as a user from the command line SELinux rules do not apply. It would explain why it works manually but not via systemd. Rather than using an init.d script you might want to try using a systemd service. I haven't tested but something like this should work. [Unit] Description=timidity daemon [Service] PIDFile=/var/run/timidity.pid
2018 Mar 13
1
Workaround for bind9 reload bug : samba_dlz Ignoring duplicate zone
Hai Baptiste, You missed my first message but here it is again. . systemctl cat bind9 # /lib/systemd/system/bind9.service [Unit] Description=BIND Domain Name Server Documentation=man:named(8) After=network.target Wants=nss-lookup.target Before=nss-lookup.target [Service] EnvironmentFile=/etc/default/bind9 ExecStart=/usr/sbin/named -f $OPTIONS ExecReload=/usr/sbin/rndc reload
2016 Oct 16
1
bind9 won't run
On 2016-10-16 12:55, Rowland Penny via samba wrote: > On Sun, 16 Oct 2016 12:38:00 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with >> Bind9_DLZ. >> >> I have one machine just like this one. Same hardware, same software >> setup. First machine is
2015 Apr 04
2
systemctl (again)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks Andrew. One more problem solved, as I discovered last thing yesterday there was a missing "[Install]". Using your copy of the httpd service I cut-and-pasted it onto the end of the service file you'd given me earlier and at last was able to load the service. It wouldn't run, but at least it was some progress. I ran
2016 Oct 16
2
bind9 won't run
I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with Bind9_DLZ. I have one machine just like this one. Same hardware, same software setup. First machine is working fine. At the moment this (second) machine is not joined to the other (until I get Bind running.) I have searched log complaints. Compared settings between the two machines and despite bind running on the first one,
2019 Jun 19
0
DLZ Backend DNS Hosed
Hai, For bind, please to add this for bind if you use bind_DLZ. How : systemctl edit bind9, or create the file manualy and run systemctl daemon-reload after. The edit command already does the reload. # /etc/systemd/system/bind9.service.d/override.conf [Service] ExecReload= But same for you. ;-) as the other list message today. ([Samba] Reverse DNS) Can you run this for me on the
2018 Dec 21
1
Samba AD DC replication error - 2, 'WERR_BADFILE'
Ok, some more resolving things to fix.   On both DC's few things to edit. In resolv.conf, the order is important here and dont point to nameserver 127.0.0.1 for the DC's.   DC1. file: /etc/resolv.conf  search example.corp nameserver IP_DC1 nameserver IP_DC2 nameserver 8.8.4.4 /etc/hosts IP_DC1 hostname.internal.example.com hostname IP_DC2 hostname.internal.example.com hostname     
2018 Jun 08
1
Problem with named.service
Good Afternoon! First I'm sorry for my last mail, and my english is not good. What OS? Centos 7.5 Samba Version? Version 4.7.0pre1-GIT-1c4b15a Bind Version? Name        : bind Arch        : x86_64 Epoch       : 32 Version     : 9.9.4 Release     : 61.el7 Size        : 4.3 M
2016 Jul 12
1
Option configure
Am 12.07.2016 um 21:35 schrieb Rowland penny: > On 12/07/16 20:25, Achim Gottinger wrote: >> Just backported 4.4.5 from debian sid to jessie. samba.service is >> masked there. If running as an fileserver the services are started >> via smbd.service,nmbd.service, winbind.service. >> There is an samba-ad-dc script which is masked by default. >> To get the ad-dc up
2015 Apr 04
0
systemctl (again)
Thats wierd. I've never had any problem with systemctl or systemd like that. Do you have your service file in the right place with the right permissions. here is the httpd service file as a reference. [centos at ipa ~]$ ls /usr/lib/systemd/system/httpd.service -l -rw-r--r--. 1 root root 694 Mar 12 14:57 /usr/lib/systemd/system/httpd.service [centos at ipa ~]$ cat
2018 May 14
3
Logrotate
Hi! I have one problem with my logrotate. Samba version: Samba 4 7.7 (compilated) S.O.: Ubuntu 14.04 /16.04 Samba logs file: /opt/samba/var/ Logrotate File: cat /etc/logrotate.d/samba -- /opt/samba/var/log.samba {   rotate 10         daily         compress         dateext         size 100M         nomail         missingok         notifempty         create 644 root root
2018 Jun 08
4
Problem with named.service
Good evening People! I have a problem when I start the named service. Check this example: [root at pc ~]# systemctl status named.service● named.service - Berkeley Internet Name Domain (DNS)   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)   Active: active (running) since Thu 2018-06-07 21:15:06 AST; 10min ago  Process: 12495 ExecStop=/bin/sh -c
2015 Apr 04
0
systemctl (again)
On 4 April 2015 at 18:40, Jonathan Billings <billings at negate.org> wrote: > > > On April 4, 2015 12:14:08 PM EDT, Pete Travis <lists at petetravis.com> wrote: >>On Apr 4, 2015 7:55 AM, "J Martin Rushton" >><martinrushton56 at btinternet.com> >>wrote: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1
2018 Dec 20
0
Samba AD DC replication error - 2, 'WERR_BADFILE'
Hai,     > When running second command I recieve error: > root at location-000001:~# systemctl start bind9 samba > Failed to start samba.service: Unit samba.service is masked.   ah yes, sorry, that is offcourse samba-ad-dc   >and yep - replication is working then!! :) what i expected the old bug. ;-)   About the other start up for both DC's do the following.  type :   systemctl