Monit error on fresh install of OMV5 on a Raspberry Pi

Hidduh · 2. Februar 2020

I've been following the OMV guide to install OMV5 on my Raspberry Pi (link) and followed every single step up to fetching the actual image and installing it (wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash). After about 15 minutes, the installation cancels and returns the following error:

Zitat

Processing triggers for initramfs-tools (0.133+deb10u1) ...

Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for systemd (241-7~deb10u2+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Errors were encountered while processing:
monit
openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)
failed to install openmediavault package.

Alles anzeigen

I tried a manual install of monit but this didn't seem to fix the issue.

Zitat

Reading package lists... Done
Building dependency tree
Reading state information... Done
monit is already the newest version (1:5.26.0-1).
monit set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up monit (1:5.26.0-1) ...
Job for monit.service failed because the control process exited with error code.
See "systemctl status monit.service" and "journalctl -xe" for details.
invoke-rc.d: initscript monit, action "start" failed.
● monit.service - LSB: service and resource monitoring daemon
Loaded: loaded (/etc/init.d/monit; generated)
Active: failed (Result: exit-code) since Fri 2020-01-31 15:32:03 GMT; 179ms ago
Docs: man:systemd-sysv-generator(8)
Process: 20369 ExecStart=/etc/init.d/monit start (code=exited, status=1/FAILURE)

Jan 31 15:32:03 raspberrypi systemd[1]: Starting LSB: service and resource monitoring daemon...
Jan 31 15:32:03 raspberrypi monit[20369]: Starting daemon monitor: monitSegmentation fault
Jan 31 15:32:03 raspberrypi monit[20369]: failed!
Jan 31 15:32:03 raspberrypi systemd[1]: monit.service: Control process exited, code=exited, status=1/FAILURE
Jan 31 15:32:03 raspberrypi systemd[1]: monit.service: Failed with result 'exit-code'.
Jan 31 15:32:03 raspberrypi systemd[1]: Failed to start LSB: service and resource monitoring daemon.
dpkg: error processing package monit (--configure):
installed monit package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of openmediavault:
openmediavault depends on monit; however:
Package monit is not configured yet.

dpkg: error processing package openmediavault (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
monit
openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)

Alles anzeigen

Checking if monit functions properly returns a 'segmentation fault'. Removing monit also uninstalls OMV.
I've been looking on the internet ever since and I can't seem to figure it out (also posted this in the OMV subreddit, one person experiences the exact same issue but is unable to figure it out also) - does anyone have a clue on how to fix this?

Vallekano · 9. Februar 2020

I got the same error un my Pi 2 B

I have tried several times following the manual.

Also, tried to skip "sudo apt.get upgrade" with same luck.

Bash

Unpacking ssh (1:7.9p1-10+deb10u2) over (1:7.9p1-10+deb10u1) ...
Preparing to unpack .../7-libgnutls30_3.6.7-4+deb10u2_armhf.deb ...
Unpacking libgnutls30:armhf (3.6.7-4+deb10u2) over (3.6.7-4) ...
Setting up libgnutls30:armhf (3.6.7-4+deb10u2) ...
(Reading database ... 58354 files and directories currently installed.)
Preparing to unpack .../libss2_1.44.5-1+deb10u3_armhf.deb ...
Unpacking libss2:armhf (1.44.5-1+deb10u3) over (1.44.5-1+deb10u2) ...
Preparing to unpack .../raspi-config_20200207_all.deb ...
Unpacking raspi-config (20200207) over (20200205) ...
Setting up monit (1:5.26.0-1) ...
Job for monit.service failed because the control process exited with error code.
See "systemctl status monit.service" and "journalctl -xe" for details.
invoke-rc.d: initscript monit, action "start" failed.
● monit.service - LSB: service and resource monitoring daemon
   Loaded: loaded (/etc/init.d/monit; generated)
   Active: failed (Result: exit-code) since Sun 2020-02-09 20:08:59 GMT; 234ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 22348 ExecStart=/etc/init.d/monit start (code=exited, status=1/FAILURE)


Feb 09 20:08:59 raspberrypi systemd[1]: Starting LSB: service and resource monitoring daemon...
Feb 09 20:08:59 raspberrypi monit[22348]: Starting daemon monitor: monitSegmentation fault
Feb 09 20:08:59 raspberrypi monit[22348]:  failed!
Feb 09 20:08:59 raspberrypi systemd[1]: monit.service: Control process exited, code=exited, status=1/FAILURE
Feb 09 20:08:59 raspberrypi systemd[1]: monit.service: Failed with result 'exit-code'.
Feb 09 20:08:59 raspberrypi systemd[1]: Failed to start LSB: service and resource monitoring daemon.
dpkg: error processing package monit (--configure):
 installed monit package post-installation script subprocess returned error exit status 1
Setting up openssh-client (1:7.9p1-10+deb10u2) ...
dpkg: dependency problems prevent configuration of openmediavault:
 openmediavault depends on monit; however:
  Package monit is not configured yet.


dpkg: error processing package openmediavault (--configure):
 dependency problems - leaving unconfigured
Setting up libpython3.7-minimal:armhf (3.7.3-2+deb10u1) ...
Setting up libss2:armhf (1.44.5-1+deb10u3) ...
Setting up sudo (1.8.27-1+deb10u2) ...
Setting up python3.7-minimal (3.7.3-2+deb10u1) ...
Setting up raspi-config (20200207) ...
Setting up openssh-sftp-server (1:7.9p1-10+deb10u2) ...
Setting up libpython3.7-stdlib:armhf (3.7.3-2+deb10u1) ...
Setting up openssh-server (1:7.9p1-10+deb10u2) ...
rescue-ssh.target is a disabled or a static unit, not starting it.
Setting up libpython3.7:armhf (3.7.3-2+deb10u1) ...
Setting up e2fsprogs (1.44.5-1+deb10u3) ...
update-initramfs: deferring update (trigger activated)
Setting up python3.7 (3.7.3-2+deb10u1) ...
Setting up ssh (1:7.9p1-10+deb10u2) ...
Processing triggers for systemd (241-7~deb10u2+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
Errors were encountered while processing:
 monit
 openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@raspberrypi:~ $

Alles anzeigen

ryecoaaron · 10. Februar 2020

This is a bug in the monit package (nothing to do with omv or install script) that I have never been able to reproduce. So, not sure how to fix it.

Vallekano · 10. Februar 2020

Any idea with this additional info? Do you think this is the issue?

Bash

pi@raspberrypi:~ $ journalctl -xe
Feb 10 05:34:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:34:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:34:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:35:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:35:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:35:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:35:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:36:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:36:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:36:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:36:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:37:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:37:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:37:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:37:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:38:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:38:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:38:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:38:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:39:01 raspberrypi CRON[5455]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 10 05:39:01 raspberrypi CRON[5459]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Feb 10 05:39:02 raspberrypi CRON[5455]: pam_unix(cron:session): session closed for user root
Feb 10 05:39:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:39:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:39:35 raspberrypi systemd[1]: Starting Clean php session files...
-- Subject: A start job for unit phpsessionclean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has begun execution.
--
-- The job identifier is 1939.
Feb 10 05:39:35 raspberrypi sessionclean[5463]: Illegal instruction
Feb 10 05:39:35 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit phpsessionclean.service has successfully entered the 'dead' state.
Feb 10 05:39:35 raspberrypi systemd[1]: Started Clean php session files.
-- Subject: A start job for unit phpsessionclean.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has finished successfully.
--
-- The job identifier is 1939.
Feb 10 05:39:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:39:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:40:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:40:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:40:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:40:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:41:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:41:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:41:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:41:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:42:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:42:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:42:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:42:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:43:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:43:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
pi@raspberrypi:~ $

Alles anzeigen

ryecoaaron · 10. Februar 2020

Zitat von Vallekano

Any idea with this additional info? Do you think this is the issue?

Salt should run masterless. The output of cat /etc/salt/minion.d/openmediavault.conf should say file_client: local. Not sure why it is looking for a master. @votdev?

And unless salt isn't configuring monit because it is looking for a master, I don't think this is a problem. What is the output of (as root): omv-salt deploy run monit

votdev · 10. Februar 2020

Zitat von Vallekano

Any idea with this additional info? Do you think this is the issue?

Bash

pi@raspberrypi:~ $ journalctl -xe
Feb 10 05:34:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:34:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:34:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:35:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:35:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:35:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:35:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:36:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:36:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:36:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:36:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:37:10 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:37:10 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:37:40 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:37:40 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:38:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:38:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:38:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:38:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:39:01 raspberrypi CRON[5455]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 10 05:39:01 raspberrypi CRON[5459]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Feb 10 05:39:02 raspberrypi CRON[5455]: pam_unix(cron:session): session closed for user root
Feb 10 05:39:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:39:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:39:35 raspberrypi systemd[1]: Starting Clean php session files...
-- Subject: A start job for unit phpsessionclean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has begun execution.
--
-- The job identifier is 1939.
Feb 10 05:39:35 raspberrypi sessionclean[5463]: Illegal instruction
Feb 10 05:39:35 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit phpsessionclean.service has successfully entered the 'dead' state.
Feb 10 05:39:35 raspberrypi systemd[1]: Started Clean php session files.
-- Subject: A start job for unit phpsessionclean.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has finished successfully.
--
-- The job identifier is 1939.
Feb 10 05:39:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:39:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:40:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:40:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:40:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:40:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:41:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:41:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:41:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:41:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:42:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:42:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:42:41 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:42:41 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
Feb 10 05:43:11 raspberrypi salt-minion[335]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
Feb 10 05:43:11 raspberrypi salt-minion[335]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
pi@raspberrypi:~ $

Alles anzeigen

Configuration of the minion was not successful. OMV runs Salt in masterless mode.

Someone or something has modified /etc/salt/minion. There default config should not be touched, thus one of the first lines MUST be #master: salt.

faabiosr · 22. März 2020

I fixed the problem installing an old version of monit

Code

apt-get install monit=1:5.25.2-3

Legellan · 23. Juni 2020

Zitat von faabiosr
I fixed the problem installing an old version of monit
Code
apt-get install monit=1:5.25.2-3

I got farther in the install but OMW is still not configured.

After installing the above version of monit, It looks to have complete the install and advised me that OMV is installed. however after a reboot and going to the Ip address of my RPi, I get a 502 bad Gateway. Previously I had just the nginx landing page.

Legellan · 23. Juni 2020

Here is the

Code

pi@raspberrypi:~ $ journalctl -xe
-- The process' exit code is 'exited' and its exit status is 1.
Jun 22 15:28:26 raspberrypi systemd[1]: monit.service: Failed with result 'exit-code
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit monit.service has entered the 'failed' state with result 'exit-code'.
Jun 22 15:28:26 raspberrypi systemd[1]: Failed to start LSB: service and resource mo
-- Subject: A start job for unit monit.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit monit.service has finished with a failure.
--
-- The job identifier is 1805 and the job result is failed.
Jun 22 15:28:30 raspberrypi systemd[1]: Reloading.
Jun 22 15:28:33 raspberrypi systemd[1]: /lib/systemd/system/rpc-statd.service:13: PI
Jun 22 15:29:48 raspberrypi sudo[866]: pam_unix(sudo:session): session closed for us
Jun 22 15:30:01 raspberrypi CRON[1360]: pam_unix(cron:session): session opened for u
Jun 22 15:30:01 raspberrypi CRON[1359]: pam_unix(cron:session): session opened for u
Jun 22 15:30:01 raspberrypi CRON[1367]: (root) CMD ([ -x /etc/init.d/anacron ] && if
Jun 22 15:30:01 raspberrypi CRON[1368]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/n
Jun 22 15:30:01 raspberrypi CRON[1360]: pam_unix(cron:session): session closed for u
Jun 22 15:30:27 raspberrypi CRON[1359]: pam_unix(cron:session): session closed for u
Jun 22 15:30:28 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-tmpfiles-clean.service has begun execution.
--
-- The job identifier is 1867.
Jun 22 15:30:28 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state
Jun 22 15:30:28 raspberrypi systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: A start job for unit systemd-tmpfiles-clean.service has finished success
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-tmpfiles-clean.service has finished successfully.
--
-- The job identifier is 1867.
Jun 22 15:31:24 raspberrypi systemd[1]: Started Run anacron jobs.
-- Subject: A start job for unit anacron.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit anacron.service has finished successfully.
--
-- The job identifier is 1871.
Jun 22 15:31:24 raspberrypi anacron[1453]: Anacron 2.3 started on 2020-06-22
Jun 22 15:31:24 raspberrypi anacron[1453]: Normal exit (0 jobs run)
Jun 22 15:31:24 raspberrypi systemd[1]: anacron.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit anacron.service has successfully entered the 'dead' state.

Alles anzeigen

Jetzt mitmachen!