Dec 07 08:42:27 Collin systemd[1]: Started cron.service - Regular background program processing daemon.
Dec 07 08:42:27 Collin cron[527]: (CRON) INFO (pidfile fd = 3)
Dec 07 08:42:27 Collin cron[527]: (CRON) INFO (Running @reboot jobs)
Dec 07 08:42:27 Collin CRON[529]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 07 08:42:27 Collin CRON[534]: (root) CMD (startx)
Dec 07 08:45:01 Collin CRON[1195]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 07 08:45:01 Collin CRON[1196]: (root) CMD (bash /root/heif-convert.sh)
Dec 07 08:45:01 Collin CRON[1195]: (CRON) info (No MTA installed, discarding output)
Dec 07 08:45:01 Collin CRON[1195]: pam_unix(cron:session): session closed for user root
Entries 6-9 repeat every five minutes. This is because the script /root/heif-convert.sh is executed every five minutes, so this would make sense.
Actually I don’t know, why the cron.service is started at 8:42, when the Nuc starts at 7:30 via wake on lan. Date and time are correct (checked via “date” command).
The entries above are the first ones in the log, so adding “-n 100” to the journalctl command does not show more / earlier entries.
In the logs I can see, that the Nuc restarted at 22:30 instead of shutting down. Do you have any idea, why the nuc restarts instead of staying off? Do you think wake on lan might be a problem?
In the BIOS I had activated, that the Nuc should start at 7:30 am. Since this did not work, I switched to the WOL solution. When I switched off the BIOS setting, the Nuc shuts down perfectly at 22:30 and stays off.