Named failing the whole time

[Francis Augusto Medeiros-Logeay]

Hi,

I know this mail has very few info - will add them later - but are there common causes for named to crash randomly?

My FreeIPA réplica has been so unstable. actually, named crashes.

Any hints on where to look? Once I had the replica to blame, it lost contact with the other replicas and had to be rejoined.

Thanks in advance for any clues.

Best,

__
Francis Augusto Medeiros-Logeay
Oslo, Norway
Sent from a mobile device / Enviado a partir de dispositivo móvel

[Sam Morris]

On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users 
wrote:
> I know this mail has very few info - will add them later - but are there 
> common causes for named to crash randomly?
>
> My FreeIPA réplica has been so unstable. actually, named crashes.
>
> Any hints on where to look? Once I had the replica to blame, it lost 
> contact with the other replicas and had to be rejoined.

I've been seeing this occasionally for quite some time. I just put in 
place a systemd unit override file to automatically restart named if it 
ever exits.

$ cat /etc/systemd/system/named.service.d/override.conf
# https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
[Service]
Restart=always

[Florence Blanc-Renaud]

Hi,
there are a few BZ opened against bind-dyndb-ldap related to named crashing
when the logs are rotating.
A customer also reported that most of his issues were fixed when he updated
named configuration so that all his DNS clients are allowed to perform
queries (see https://bugzilla.redhat.com/show_bug.cgi?id=1854473#c25 )

flo

On Mon, Dec 12, 2022 at 2:50 PM Sam Morris via FreeIPA-users <
[e-mail]> wrote:
> On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users
> wrote:
> > I know this mail has very few info - will add them later - but are there
> > common causes for named to crash randomly?
> >
> > My FreeIPA réplica has been so unstable. actually, named crashes.
> >
> > Any hints on where to look? Once I had the replica to blame, it lost
> > contact with the other replicas and had to be rejoined.
>
> I've been seeing this occasionally for quite some time. I just put in
> place a systemd unit override file to automatically restart named if it
> ever exits.
>
> $ cat /etc/systemd/system/named.service.d/override.conf
> # https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
> [Service]
> Restart=always
>
> --
> Sam Morris https://robots.org.uk/
> PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9
> _______________________________________________
> FreeIPA-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/[e-mail]...
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Francis Augusto Medeiros-Logeay]

> On 12 Dec 2022, at 13:33, Sam Morris via FreeIPA-users  wrote:
>
> On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:
> > I know this mail has very few info - will add them later - but are there common causes for named to crash randomly?
> > My FreeIPA réplica has been so unstable. actually, named crashes.
> > Any hints on where to look? Once I had the replica to blame, it lost contact with the other replicas and had to be rejoined.
>
> I've been seeing this occasionally for quite some time. I just put in place a systemd unit override file to automatically restart named if it ever exits.
>
> $ cat /etc/systemd/system/named.service.d/override.conf
> # https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
> [Service]
> Restart=always

Thanks a lot, Sam. This is a very good tip. 
I remember having that with my first FreeIPA install. It never happened again. Never happened to my first replica. But on my third replica it happens a lot. I thought it was related to a replication issue I had before, but after it was fixed it was stable for two weeks until it crashed again yesterday.

I’ve set up a Zabbix alarm, but your tip takes better care of the problem.

Unfortunately when it happened last time I was afk and thus could just restart it without seeing anything on the logs (besides a core dump error).

Best,

Francis
> -- 
> Sam Morris https://robots.org.uk/
> PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9
> _______________________________________________
> FreeIPA-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedorahosted.org/archives/list/[e-mail]...
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Rob Crittenden]

Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:
> > On 12 Dec 2022, at 13:33, Sam Morris via FreeIPA-users  wrote:
> >
> > On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:
> > > I know this mail has very few info - will add them later - but are there common causes for named to crash randomly?
> > > My FreeIPA réplica has been so unstable. actually, named crashes.
> > > Any hints on where to look? Once I had the replica to blame, it lost contact with the other replicas and had to be rejoined.
> >
> > I've been seeing this occasionally for quite some time. I just put in place a systemd unit override file to automatically restart named if it ever exits.
> >
> > $ cat /etc/systemd/system/named.service.d/override.conf
> > # https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
> > [Service]
> > Restart=always
>
> Thanks a lot, Sam. This is a very good tip. 
> I remember having that with my first FreeIPA install. It never happened again. Never happened to my first replica. But on my third replica it happens a lot. I thought it was related to a replication issue I had before, but after it was fixed it was stable for two weeks until it crashed again yesterday.
>
> I’ve set up a Zabbix alarm, but your tip takes better care of the problem.
>
> Unfortunately when it happened last time I was afk and thus could just restart it without seeing anything on the logs (besides a core dump error).

If you are getting a core dump then filing a BZ and/or attaching to an
existing one is the best approach.

rob
> Best,
>
> Francis
> > -- 
> > Sam Morris https://robots.org.uk/
> > PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9
> > _______________________________________________
> > FreeIPA-users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedorahosted.org/archives/list/[e-mail]...
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> FreeIPA-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedorahosted.org/archives/list/[e-mail]...
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Francis Augusto Medeiros-Logeay]

> On 12 Dec 2022, at 10:33, Sam Morris via FreeIPA-users  wrote:
>
> On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:
> > I know this mail has very few info - will add them later - but are there common causes for named to crash randomly?
> > My FreeIPA réplica has been so unstable. actually, named crashes.
> > Any hints on where to look? Once I had the replica to blame, it lost contact with the other replicas and had to be rejoined.
>
> I've been seeing this occasionally for quite some time. I just put in place a systemd unit override file to automatically restart named if it ever exits.
>
> $ cat /etc/systemd/system/named.service.d/override.conf
> # https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
> [Service]
> Restart=always

Hi Sam,

I am on Fedora 35 and can’t find the names.service nor the named.service.d directory. So weird!
Can I still create it and the override file?

Best,

Francis

[Sam Morris]

On 13/12/2022 08:49, Francis Augusto Medeiros-Logeay wrote:
> > On 12 Dec 2022, at 10:33, Sam Morris via FreeIPA-users  wrote:
> >
> > On 11/12/2022 12:22, Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:
> > > I know this mail has very few info - will add them later - but are there common causes for named to crash randomly?
> > > My FreeIPA réplica has been so unstable. actually, named crashes.
> > > Any hints on where to look? Once I had the replica to blame, it lost contact with the other replicas and had to be rejoined.
> >
> > I've been seeing this occasionally for quite some time. I just put in place a systemd unit override file to automatically restart named if it ever exits.
> >
> > $ cat /etc/systemd/system/named.service.d/override.conf
> > # https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36
> > [Service]
> > Restart=always
>
> Hi Sam,
>
> I am on Fedora 35 and can’t find the names.service nor the named.service.d directory. So weird!
> Can I still create it and the override file?

Yes, if you run 'systemctl edit named.service' then systemd will create 
the directory & file for you and open it in your $EDITOR.