Cron logs in CLI after move to another computer

Hi,
I just moved my home assistant (HAOS in VirtualBox) from one computer to another one (fresh install on the new machine followed by a full recovery from backup) and somehow I’m getting cron logs in the CLI now.

About 1-2 minutes after the “Welcome to the Home Assistant command line” message appears, the following message shows up:

crond[58] crond (busybox 1.35.0) started, log level 8

This is then followed on every cron execution with a message such as this one:

crond[58] USER root pid 148 cmd run-parts /etc/periodic/15min

I have made no manual changes to any cronjob settings. The crontab looks like this.

# do daily/weekly/monthly maintenance
# min   hour    day     month   weekday command
*/15    *       *       *       *       run-parts /etc/periodic/15min
0       *       *       *       *       run-parts /etc/periodic/hourly
0       2       *       *       *       run-parts /etc/periodic/daily
0       3       *       *       6       run-parts /etc/periodic/weekly
0       5       1       *       *       run-parts /etc/periodic/monthly

All the directories referenced (15min, hourly, etc.) are empty. Does anyone have an idea what could be causing these logs to appear in the CLI?

1 Like

Hi, for me it’s the same.

I just changed pc and use HA with Virtualbox
I hope someone can help us…

1 Like

@carspawn I’m wondering if the change of PC is unrelated and it’s actually caused by the update to HAOS 10.0. Unfortunately I’m not sure if the first occurrence came after the update or after the migration. Was your old system already running 10.0 or still 9.5?

I honestly don’t remember because on the same day I changed pc and upgraded to 10.0. It is strange that we both got the error as a result of the pc change. I will try to retrieve the old virtual machine from the bkp tomorrow and verify.

Hi, I restored the backup of 20/4. Already with OS 10 but with HA Core 2023.4.5.
So far I have not received any error messages.
I also show you the updates I should do, I will try to do them tomorrow.

Exactly the same issue for me too. I’m running v9.5 of the OS with v2023.3.3 of HA. My install hasn’t moved servers or device of any sort. I’m suspecting an add-on might have caused this, but if it has, I don’t know which one it would be!

I was doing something similar today, I am running supervised on a VM in proxmox. I added a new vm and installed os 10 on it, ( i was trying to get rid of over 200 dead entities !) I was switching between the to VM’s to get everything set up the same on the newer version when I started the new version and couldn’t get access as it showed an invalid response. I also got the cron notification on the console. I shut that down and went back to the original which is also on os 10 and that also has the cron notification , however I have changed nothing with this system but now it wont connect through DUCK Dns !

Hello the same problem at home, it’s been 5 days that it gives me the same message! If anyone finds where it came from, I’m a taker!! I couldn’t find the mod that does this!

Same here:
VirtualBox image. I did not move the server though.

If i leave it for too long it fills the screen with such messages. From the above screenshots i have the NGIX addon in common but i am not sure it is this that is causing the problem.

Anyone able to find a solution?

1 Like

I confirm, after restoring my addon NGINX to version 3.2 and rebooting, those crond messages are not present anymore.

I assume it would be best to open an issue on Github …

3 Likes

Definitely seems plausible. The commit to the commit on the nginx addon that pushed it to 3.3 contains a fair amount of stuff related to crond:

I’ve created an issue:

Please feel free to add any relevant info there, everyone :slight_smile:

1 Like

I can confirm after restoring to NGIX 3.2 that the messages have gone away. Apart from being unsightly my HA was running normally with no performance issues or no issues connecting internally or externally. unfortunately I have a little bit of OCD so having these message zig zag on your terminal was bothering me. I run HA on a dedicated laptop and keep looking at the screen ever so often. Thanks for helping keeping me sane :slight_smile:

NGINX 3.4.1 has just been released which fixes the issue :tada:

2 Likes

I just started getting this same message on the CLI out of the blue… And i dont even have NGINX installed (at least not that im aware of)… Is anyone having the same issue? I even tried a restore from a Proxmox backup… Didnt reverted this issue…

1 Like

Same here after a migration from “Home Assistant Blue” to “Generic hardware”

cmd run-parts /etc/periodic/15min
cmd s6-setuidgid abc php…