Sun Feb 16 07:36:00 2025 cron.err crond[1894]: file root:
Sun Feb 16 07:36:00 2025 cron.err crond[1894]: line fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt
Sun Feb 16 07:37:00 2025 cron.err crond[1894]: wakeup dt=60
Sun Feb 16 07:37:00 2025 cron.err crond[1894]: file root:
Sun Feb 16 07:37:00 2025 cron.err crond[1894]: line fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt
Sun Feb 16 07:38:00 2025 cron.err crond[1894]: wakeup dt=60
Sun Feb 16 07:38:00 2025 cron.err crond[1894]: file root:
Sun Feb 16 07:38:00 2025 cron.err crond[1894]: line fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt
Sun Feb 16 07:39:00 2025 cron.err crond[1894]: wakeup dt=60
Sun Feb 16 07:39:00 2025 cron.err crond[1894]: file root:
Sun Feb 16 07:39:00 2025 cron.err crond[1894]: line fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt
Sun Feb 16 07:40:00 2025 cron.err crond[1894]: wakeup dt=60
Sun Feb 16 07:40:00 2025 cron.err crond[1894]: file root:
Sun Feb 16 07:40:00 2025 cron.err crond[1894]: line fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt
Sun Feb 16 07:41:00 2025 cron.err crond[1894]: wakeup dt=60
``
``root@OpenWrt_AX3000T:~# crontab -l
0 */12 * * * fping -s -g -q -a -n -A 10.20.20.1/24 > fping.txt'`
I have this cron job runing at minute 0 every 12 hours but after installing latest
snapshot it fills the log with the above messages. This cron job runs smoothly
for 6 months always on snapshot firmware.cat etc/crontab
I deleted it with crontab -r.
Maybe its the new BusyBox 1.37.0 . This was running flawlessly with the old 1.36.1
It is about busybox 1.37.0 reaction to your cronloglevel setting in /etc/config/system.
You likely have 5 there as the value.
Make sure that you have 7 or 9 there.
History is that earlier busybox mishandled level 5 and crond was not as verbose as it should had been. Now in 1.37.0 upstream fixed their bug and the logging at 5 got more verbose. We need to set cronloglevel accordingly.
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.