[Eisfair] Bind startet nach update nicht

Fr Dez 15 22:52:52 CET 2023

Hallo Martin

da sind irgendwelche Rechte verbogen, es ist nur schwer zu sagen 
welche das sind

kann es /var sein?

ls -la /

Holger

Am 15/12/2023 um 21.47 schrieb Martin Faderbauer:
> sv02 # systemctl status named.service
> x named.service - Berkeley Internet Name Domain (DNS)
>       Loaded: loaded (/usr/lib/systemd/system/named.service; enabled;
> preset: disabled)
>       Active: failed (Result: exit-code) since Fri 2023-12-15 21:41:07
> CET; 27s ago
>      Process: 9057 ExecStartPre=/usr/libexec/bind/named.prep
> (code=exited, status=226/NAMESPACE)
>          CPU: 4ms
> 
> Dez 15 21:41:07 sv02 systemd[1]: Starting Berkeley Internet Name Domain
> (DNS)...
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed to set up
> mount namespacing: /run/systemd/unit-root/run/named: No such file or
> directory
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed at step
> NAMESPACE spawning /usr/libexec/bind/named.prep: No such file or directory
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Control process exited,
> code=exited, status=226/NAMESPACE
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Failed with result
> 'exit-code'.
> Dez 15 21:41:07 sv02 systemd[1]: Failed to start Berkeley Internet Name
> Domain (DNS).
> sv02 #
> 
> 
> sv02 # journalctl -xeu named.service
> -- An ExecStartPre= process belonging to unit named.service has exited.
> --
> -- The process' exit code is 'exited' and its exit status is 226.
> Dez 15 21:41:06 sv02 systemd[1]: named.service: Failed with result
> 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The unit named.service has entered the 'failed' state with result
> 'exit-code'.
> Dez 15 21:41:06 sv02 systemd[1]: Failed to start Berkeley Internet Name
> Domain (DNS).
> -- Subject: A start job for unit named.service has failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has finished with a failure.
> --
> -- The job identifier is 2829 and the job result is failed.
> Dez 15 21:41:07 sv02 systemd[1]: Starting Berkeley Internet Name Domain
> (DNS)...
> -- Subject: A start job for unit named.service has begun execution
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has begun execution.
> --
> -- The job identifier is 2912.
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed to set up
> mount namespacing: /run/systemd/unit-root/run/named: No such file or
> directory
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed at step
> NAMESPACE spawning /usr/libexec/bind/named.prep: No such file or directory
> -- Subject: Process /usr/libexec/bind/named.prep could not be executed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The process /usr/libexec/bind/named.prep could not be executed and
> failed.
> --
> -- The error number returned by this process is ERRNO.
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Control process exited,
> code=exited, status=226/NAMESPACE
> -- Subject: Unit process exited
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- An ExecStartPre= process belonging to unit named.service has exited.
> --
> -- The process' exit code is 'exited' and its exit status is 226.
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Failed with result
> 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The unit named.service has entered the 'failed' state with result
> 'exit-code'.
> Dez 15 21:41:07 sv02 systemd[1]: Failed to start Berkeley Internet Name
> Domain (DNS).
> -- Subject: A start job for unit named.service has failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has finished with a failure.
> --
> -- The job identifier is 2912 and the job result is failed.
> lines 179-234/234 (END)
> -- An ExecStartPre= process belonging to unit named.service has exited.
> --
> -- The process' exit code is 'exited' and its exit status is 226.
> Dez 15 21:41:06 sv02 systemd[1]: named.service: Failed with result
> 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The unit named.service has entered the 'failed' state with result
> 'exit-code'.
> Dez 15 21:41:06 sv02 systemd[1]: Failed to start Berkeley Internet Name
> Domain (DNS).
> -- Subject: A start job for unit named.service has failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has finished with a failure.
> --
> -- The job identifier is 2829 and the job result is failed.
> Dez 15 21:41:07 sv02 systemd[1]: Starting Berkeley Internet Name Domain
> (DNS)...
> -- Subject: A start job for unit named.service has begun execution
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has begun execution.
> --
> -- The job identifier is 2912.
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed to set up
> mount namespacing: /run/systemd/unit-root/run/named: No such file or
> directory
> Dez 15 21:41:07 sv02 (med.prep)[9057]: named.service: Failed at step
> NAMESPACE spawning /usr/libexec/bind/named.prep: No such file or directory
> -- Subject: Process /usr/libexec/bind/named.prep could not be executed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The process /usr/libexec/bind/named.prep could not be executed and
> failed.
> --
> -- The error number returned by this process is ERRNO.
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Control process exited,
> code=exited, status=226/NAMESPACE
> -- Subject: Unit process exited
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- An ExecStartPre= process belonging to unit named.service has exited.
> --
> -- The process' exit code is 'exited' and its exit status is 226.
> Dez 15 21:41:07 sv02 systemd[1]: named.service: Failed with result
> 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The unit named.service has entered the 'failed' state with result
> 'exit-code'.
> Dez 15 21:41:07 sv02 systemd[1]: Failed to start Berkeley Internet Name
> Domain (DNS).
> -- Subject: A start job for unit named.service has failed
> -- Defined-By: systemd
> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- A start job for unit named.service has finished with a failure.
> --
> -- The job identifier is 2912 and the job result is failed.
> 
> 
> Am 15.12.2023 um 21:11 schrieb Marcus Röckrath:
>> Hallo Martin,
>>
>> Martin Faderbauer wrote:
>>
>>> nach dem Update lauft leider BIND nicht mehr
>>>
>>> See "systemctl status named.service" and "journalctl -xeu named.service"
>>> for details.
>>
>> Bitte die angegebenen Befehle ausführen und die Ausgabe posten.
>>