Seite 3 von 3

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 12:50
von NorbertKoch
Hallo Herr Schneider,

leider nicht:
root@opsi:~#

Code: Alles auswählen

systemctl restart redis
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xeu redis-server.service" for details.
root@opsi:~#

Code: Alles auswählen

systemctl status redis-server.service
× redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-06-16 12:48:05 CEST; 1min 8s ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 15873 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf --supervised systemd --daemonize no (code=exited, status=1/FAILURE)
Main PID: 15873 (code=exited, status=1/FAILURE)
Status: "Redis is loading..."
CPU: 64ms

Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: Stopped Advanced key-value store.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: Failed to start Advanced key-value store.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: Failed to start Advanced key-value store.
root@opsi:~#

Code: Alles auswählen

journalctl -xeu redis-server.service
Jun 16 12:48:04 opsi.intern.zz systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
Jun 16 12:48:04 opsi.intern.zz systemd[1]: Failed to start Advanced key-value store.
░░ Subject: A start job for unit redis-server.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit redis-server.service has finished with a failure.
░░
░░ The job identifier is 48929 and the job result is failed.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit redis-server.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: Stopped Advanced key-value store.
░░ Subject: A stop job for unit redis-server.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit redis-server.service has finished.
░░
░░ The job identifier is 49011 and the job result is done.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
Jun 16 12:48:05 opsi.intern.zz systemd[1]: Failed to start Advanced key-value store.
░░ Subject: A start job for unit redis-server.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit redis-server.service has finished with a failure.
░░
░░ The job identifier is 49011 and the job result is failed.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: redis-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
Jun 16 12:48:11 opsi.intern.zz systemd[1]: Failed to start Advanced key-value store.
░░ Subject: A start job for unit redis-server.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit redis-server.service has finished with a failure.
░░
░░ The job identifier is 49093 and the job result is failed.

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 14:13
von j.schneider
Ist in der /etc/redis/redis.conf dieser Eintrag vorhanden?

Code: Alles auswählen

loadmodule /usr/lib/redis/modules/redistimeseries.so

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 14:14
von j.schneider
Was steht in der /var/log/redis/redis-server.log?

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 14:41
von NorbertKoch
Hallo Herr Schneider,

ich habe abgebrochen und bin zum letzten Snapshot zurückgekehrt. Nächste Woche versuche ich es wieder.

Aber da erstmal mit den Depots, da die nicht so häufig benötigt werden wie der Config-Server.

Bis hierhin aber allen ein herzliches Dankeschön und ein schönes Wochenende.

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 15:39
von wolfbardo
wurde denn nach dem Upgrade zunaechst die

Code: Alles auswählen

/etc/apt/sources.list.d/opsi.list
gemaess


https://download.uib.de/opsi_stable/doc ... arted.html

angepasst?

Code: Alles auswählen


apt install host pigz apt-transport-https software-properties-common curl gpg
mkdir -p /usr/local/share/keyrings

REPO_URL=https://download.opensuse.org/repositories/home:/uibmz:/opsi:/4.2:/stable/xUbuntu_22.04
REPO_KEY=/usr/local/share/keyrings/opsi.gpg
echo "deb [signed-by=${REPO_KEY}] ${REPO_URL}/ /" > /etc/apt/sources.list.d/opsi.list
curl -fsSL ${REPO_URL}/Release.key | gpg --dearmor | sudo tee ${REPO_KEY} > /dev/null

Dann

Code: Alles auswählen

apt update
apt dist-upgrade
sowie

Code: Alles auswählen

apt reinstall opsiconfd
?

Gruss
Bardo Wolf

Re: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 16 Jun 2023, 16:19
von NorbertKoch
Hallo Bardo,

danke. Zumindest das erste Depot habe ich damit updaten können.

Nächste Woche dann die weiteren 3 Depots und den Config-Server.

Supi: Das Wochenende ist (stimmungsmäßig) gerettet. :D

Re: Solved: Probleme nach Upgrade des opsi-Servers auf Ubuntu 22.04

Verfasst: 19 Jun 2023, 10:20
von NorbertKoch
Hallo Bardo,

tausend Dank nochmal: Der Konfigurationsserver und alle 4 Depots sind jetzt auf 22.04 und laufen.