after update of Tumbleweed, I suddenly see following error:
Starting libvirt QEMU daemon...
[ OK ] Finished Permit User Sessions.
Starting X Display Manager...
Starting Hold until boot process finishes up...
[FAILED] Failed to start Valkey Sentinel instance: basename.
See 'systemctl status valkey-sentinel@basename.service' for details.
[FAILED] Failed to start Valkey instance: basename.
See 'systemctl status valkey@basename.service' for details.
Starting Valkey Sentinel instance: basename...
Starting Valkey instance: basename...
[FAILED] Failed to start Valkey Sentinel instance: basename.
See 'systemctl status valkey-sentinel@basename.service' for details.
[FAILED] Failed to start Valkey instance: basename.
See 'systemctl status valkey@basename.service' for details.
[ OK ] Started NTP client/server.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Backup of RPM database.
[ OK ] Started Backup of /etc/sysconfig.
[ OK ] Started Balance block groups on a btrfs filesystem.
[ OK ] Started Scrub btrfs filesystem, verify block checksums.
[ OK ] Started Check if mainboard battery is Ok.
[ OK ] Started Discard unused filesystem blocks once a week.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Timeline of Snapper Snapshots.
[ OK ] Started daily update of the root trust anchor for DNSSEC.
[ OK ] Reached target Timer Units.
[ OK ] Started Command Scheduler.
Starting Valkey Sentinel instance: basename...
Starting Valkey instance: basename...
[ OK ] Started OpenSSH Daemon.zaoliang@dell-5320:/var/log> systemctl status
valkey-sentinel@basename.service
× valkey-sentinel@basename.service - Valkey Sentinel instance: basename
Loaded: loaded (/usr/lib/systemd/system/valkey-sentinel@.service; enabled;
preset: disabled)
Active: failed (Result: exit-code) since Mon 2024-07-08 18:53:01 CEST;
1min 13s ago
Process: 1449 ExecStart=/usr/bin/valkey-sentinel
/etc/valkey/sentinel-basename.conf (code=exited, status=1/FAILURE)
Main PID: 1449 (code=exited, status=1/FAILURE)
CPU: 50ms
Warning: some journal files were not opened due to insufficient permissions.
zaoliang@dell-5320:/var/log> sudo systemctl status
valkey-sentinel@basename.service
× valkey-sentinel@basename.service - Valkey Sentinel instance: basename
Loaded: loaded (/usr/lib/systemd/system/valkey-sentinel@.service; enabled;
preset: disabled)
Active: failed (Result: exit-code) since Mon 2024-07-08 18:53:01 CEST;
1min 32s ago
Process: 1449 ExecStart=/usr/bin/valkey-sentinel
/etc/valkey/sentinel-basename.conf (code=exited, status=1/FAILURE)
Main PID: 1449 (code=exited, status=1/FAILURE)
CPU: 50ms
Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel@basename.service:
Scheduled restart job, restart counter is at 5.
Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel@basename.service: Start
request repeated too quickly.
Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel@basename.service: Failed
with result 'exit-code'.
Jul 08 18:53:01 dell-5320 systemd[1]: Failed to start Valkey Sentinel instance:
basename.
zaoliang@dell-5320:/var/log> sudo systemctl restart
valkey-sentinel@basename.service
Job for valkey-sentinel@basename.service failed because the control process
exited with error code.
See "systemctl status valkey-sentinel@basename.service" and "journalctl -xeu
valkey-sentinel@basename.service" for details.
[FAILED] Failed to start Valkey Sentinel instance: basename.
--
zaoliang@dell-5320:/var/log> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20240704"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240704"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240704:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240704"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"