[Eisfair] Bind startet nach update nicht
Martin Faderbauer
martin at fmit.at
Fr Dez 15 23:27:25 CET 2023
mit den rechten kannst die recht haben
da waren bei einigen Updates Warnungen mit
"root.root" "root:root"
die sind mit den bash update gekommen und nach einiger zeit verschwunden.
sv02 # ls -la /
insgesamt 13853
drwxr-xr-x 30 wwwrun root 4096 15. Dez 22:33 .
drwxr-xr-x 30 wwwrun root 4096 15. Dez 22:33 ..
drwxr-x--x 3 root root 4096 8. M▒r 2022 bacula-restore
drwxrwxr-x 2 root root 4096 15. Dez 20:40 bin
drwxr-xr-x 4 root root 1024 15. Dez 20:19 boot
drwxrwxrwt 3 root root 640 15. Dez 23:20 brute_force_blocking
drwxr-xr-x 4 root root 4096 16. Nov 2020 data
drwxr-xr-x 16 root root 3520 15. Dez 22:31 dev
drwxr-xr-x 61 root root 4096 15. Dez 22:32 etc
drwxr-xr-x 25 root root 4096 15. Dez 21:35 home
-rw-r--r-- 1 root root 1113 27. Okt 2021 include.txt
drwxr-xr-x 4 root root 4096 15. Dez 20:16 lib
drwxr-xr-x 3 root root 4096 15. Dez 20:36 lib64
drwx------ 2 root root 16384 9. Nov 2020 lost+found
drwxr-xr-x 5 root root 4096 3. M▒r 2014 media
drwxr-xr-x 2 root root 4096 9. Nov 2020 mnt
drwxrwxrwx 2 root root 4096 10. Nov 2020 mountpoint1
drwxrwxrwx 2 root root 4096 10. Nov 2020 mountpoint2
drwxr-xr-x 3 root root 4096 13. Nov 2020 opt
dr-xr-xr-x 260 root root 0 15. Dez 22:31 proc
drwxrwxrwx 25 root nogroup 4096 15. Dez 20:22 public
-rw------- 1 wwwrun nogroup 1024 3. Nov 17:50 .rnd
drwx------ 7 root root 4096 15. Dez 22:31 root
drwxr-xr-x 20 root root 720 15. Dez 22:32 run
drwxr-xr-x 11 root root 4096 9. Feb 2022 samba_printer_drivers
drwxr-xr-x 2 root root 4096 15. Dez 20:40 sbin
drwx------ 2 root root 4096 10. Nov 2020 .spamassassin
drwxr-xr-x 5 root root 4096 15. Dez 20:17 srv
dr-xr-xr-x 13 root root 0 15. Dez 22:31 sys
-rw-r--r-- 1 root root 3421323 28. Jun 2022
System.map-5.10.126-eisfair-64-VIRT
-rw-r--r-- 1 root root 3399057 3. Okt 2021
System.map-5.10.70-eisfair-64-VIRT
-rw-r--r-- 1 root root 3401808 22. J▒n 2022
System.map-5.10.93-eisfair-64-VIRT
-rw-r--r-- 1 root root 3535923 7. Nov 21:19
System.map-5.15.137-eisfair-64-VIRT
drwxrwxrwt 8 root root 299008 15. Dez 23:20 tmp
drwxr-xr-x 13 root root 4096 15. Dez 20:13 usr
drwxr-xr-x 17 root root 4096 15. Dez 20:42 var
sv02 #
Am 15.12.2023 um 22:52 schrieb Holger Bruenjes:
> 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.
>>>
>
Mehr Informationen über die Mailingliste Eisfair