KeyHelp Community

I'm sure the cause of the problem is within KeyHelp
Well, I am not completly sure, but started to happen after upgrade to 24.04 (using KeyHelp instructions/script).

Server operating system + version
(e.g. Ubuntu 24.04)

KeyHelp version + build number
24.2

Problem description / error messages
Named fails to start; it tries but it fails:

2024-10-24T11:08:32.422075-03:00 server systemd[1]: named.service: Failed with result 'timeout'.
2024-10-24T11:08:32.422817-03:00 server systemd[1]: Failed to start named.service - BIND Domain Name Server.
2024-10-24T11:08:32.488251-03:00 server grafana[7598]: logger=cleanup t=2024-10-24T11:08:32.485705417-03:00 level=info msg="Completed cleanup jobs" duration=61.708861ms
2024-10-24T11:08:32.622916-03:00 server systemd[1]: named.service: Scheduled restart job, restart counter is at 1.
2024-10-24T11:08:32.682943-03:00 server systemd[1]: Starting named.service - BIND Domain Name Server..

Expected result
Thats starts correctly.

Actual result
It does fails with timeout

Steps to reproduce
Just trying to start named service with: sudo service named start

Additional information
After upgrade from Ubuntu 22.04 to 24.04 using KeyHelp Script.

Does

Code: Select all

named-checkconf

show any output?

What does systemctl status named show?

First, it thought the problem was caused by running systemd-resolve (which maybe was enabled during Ubuntu upgrade process?), but after stopped and disabled it, still I can´t manage named service to finish to start (it just time out and keeps trying).

named-checkconf gives no ouput.

EDIT:

Systemd journal:

...
oct 24 12:41:17 server.gdnet.ar systemd[1]: named.service: start operation timed out. Terminating.
oct 24 12:41:17 server.gdnet.ar systemd[1]: named.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit named.service has entered the 'failed' state with result 'timeout'.
oct 24 12:41:17 server.gdnet.ar systemd[1]: Failed to start named.service - BIND Domain Name Server.
░░ Subject: A start job for unit named.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit named.service has finished with a failure.
░░
░░ The job identifier is 30129 and the job result is failed.
oct 24 12:41:17 server.gdnet.ar systemd[1]: named.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit named.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
oct 24 12:41:17 server.gdnet.ar systemd[1]: Starting named.service - BIND Domain Name Server...
░░ Subject: A start job for unit named.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit named.service has begun execution.
░░
░░ The job identifier is 30417.
oct 24 12:41:17 server.gdnet.ar named[43821]: starting BIND 9.18.28-0ubuntu0.24.04.1-Ubuntu (Extended Support Version) <id:>
...

And keeps like that, trying and trying but always timeout.

Attaching systemd journal from named just in case.

Ok, seems I've resolved it. One for the files not replaced during the Ubuntu 24.04 (because in KeyHelp upgrade guide explicit says that files should not replaced during upgrade process) was causing the problem: /etc/apparmor.d/usr.sbin.named

So, I've replaced it for the upgraded file from Ubuntu 24.04 and now named is starting just fine.

KeyHelp Community

Named won't start after Upgrade to 24.04

Named won't start after Upgrade to 24.04

Re: Named won't start after Upgrade to 24.04

Re: Named won't start after Upgrade to 24.04

Re: Named won't start after Upgrade to 24.04

Re: Named won't start after Upgrade to 24.04 [SOLVED]