Cron jobs not working: "cron.err crond"

[lleachii]

I didn't see an issue in your first post.

You stated:

@Fridolin

Hello, my cron job is not working:
in http://192.168.1.1/cgi-bin/luci/admin/status/logs (syslog):

Tue Aug 15 15:23:00 2023 cron.err crond[1510]: USER root pid 4568 cmd /usr/bin/wireguard_watchdog
Tue Aug 15 15:24:00 2023 cron.err crond[1510]: USER root pid 4587 cmd /usr/bin/wireguard_watchdog
Tue Aug 15 15:25:00 2023 cron.err crond[1510]: USER root pid 4605 cmd /usr/bin/wireguard_watchdog
Tue Aug 15 15:26:00 2023 cron.err crond[1510]: USER root pid 4623 cmd /usr/bin/wireguard_watchdog
Tue Aug 15 15:27:00 2023 cron.err crond[1510]: USER root pid 4641 cmd /usr/bin/wireguard_watchdog

This shows that your cron job is running every minute, as it seems you discussed here: Wireguard on a Router - never ending reboots after adding "watchdog" in Crontab

@Fridolin

running multiple times
root@wdr3500:~# /usr/bin/wireguard_watchdog
does not create any entrys in syslog

Running this on the command line would not make a log entry. It's not clear why you're under the impression that it should make a log entry - can you explain?

@Fridolin

I have searched in this forum but still not be able to understand what the problem is. Expected behavior: cron gives not such errors in syslog. There are much threads about such an error. I could not figure out, what this means and how to solve. So I ask u directly.

It means your cron job ran successfully.

@Fridolin

I have added a own logger command into the wireguard_watchdog file:

@Fridolin

Now get this every minute:

It's not clear why you're doing this and what the issue is that you're solving by doing so.

@Fridolin

I did this:
root@wdr3500:~# nano /etc/config/system

#       option conloglevel '8'
#       option cronloglevel '5'
        option conloglevel '4'
        option cronloglevel '9'

and saved, then:
root@wdr3500:~# /etc/init.d/cron restart

Not sure how those configs are related to the cron job you configured - or how it relates to running the the wireguard watchdog command. Perhaps there's some confusion on your part?