Bonjour la liste,
J'ai une machine en unstable depuis un certain temps (plusieurs années)
J'ai un souci avec le service systemd-random-seed (depuis plusieurs
mois)
root@salicyline:~# systemctl status --failed
× systemd-random-seed.service - Load/Save Random Seed
Loaded: loaded (/lib/systemd/system/systemd-random-seed.service;
static)
Active: failed (Result: exit-code) since Mon 2023-01-30 10:18:34
CET; 18min ago
Docs: man:systemd-random-seed.service(8)
man:random(4)
Main PID: 568 (code=exited, status=1/FAILURE)
CPU: 4ms
janv. 30 10:18:34 salicyline systemd[1]: Starting Load/Save Random
Seed...
janv. 30 10:18:34 salicyline systemd-random-seed[568]: Failed to create
directory /var/lib/systemd: No such file or directory
janv. 30 10:18:34 salicyline systemd[1]: systemd-random-seed.service:
Main process exited, code=exited, status=1/FAILURE
janv. 30 10:18:34 salicyline systemd[1]: systemd-random-seed.service:
Failed with result 'exit-code'.
janv. 30 10:18:34 salicyline systemd[1]: Failed to start Load/Save
Random Seed.
root@salicyline:~# systemctl start systemd-random-seed
root@salicyline:~# systemctl status --failed
root@salicyline:~#
Son démarrage échoue systematiquement au boot, mais tout se passe bien
ensuite...
Il semble qu'il y ait un problème d'accès au système de fichier.
Mon fstab ne présente pas de bizarerie
root@salicyline:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name
devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/salicyline--vg-root / ext4 errors=remount-
ro 0 1
# /boot was on /dev/sda1 during installation
UUID=90a03453-e990-418c-8dd6-92f7748e2f8c /boot ext2
defaults 0 2
# /lent was on /dev/sdb2 during installation
UUID=141168c4-7dc2-4d10-83ef-80dd68829111 /lent ext4
defaults 0 2
# swap was on /dev/sdb1 during installation
UUID=7558e382-d940-4e14-856d-7695f3c1d7db none swap sw
0 0
Et je ne maîtrise pas suffisemment systemd pour avoir toucher à
root@salicyline:/# cat
/usr/lib/systemd/system/sysinit.target.wants/systemd-random-
seed.service
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as
published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Load/Save Random Seed
Documentation=man:systemd-random-seed.service(8) man:random(4)
DefaultDependencies=no
RequiresMountsFor=/var/lib/systemd/random-seed
Conflicts=shutdown.target
After=systemd-remount-fs.service
Before=first-boot-complete.target shutdown.target
Wants=first-boot-complete.target
ConditionVirtualization=!container
ConditionPathExists=!/etc/initrd-release
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/systemd/systemd-random-seed load
ExecStop=/lib/systemd/systemd-random-seed save
# This service waits until the kernel's entropy pool is initialized,
and may be
# used as ordering barrier for service that require an initialized
entropy
# pool. Since initialization can take a while on entropy-starved
systems, let's
# increase the timeout substantially here.
TimeoutSec=10min
Bon, ce n'est pas bien grave, mais si quelqu'un a une idée...
Christophe
