Hi!

anyone having seen crond running, but only sporadic executing commands?

Nov 23 15:00:00 nbsd7-64 cron[739]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 23 15:10:00 nbsd7-64 cron[360]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:10:00 nbsd7-64 cron[354]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 23 15:20:00 nbsd7-64 cron[433]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:20:00 nbsd7-64 cron[1145]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 23 15:30:00 nbsd7-64 cron[1272]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:30:00 nbsd7-64 cron[911]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 23 15:40:01 nbsd7-64 cron[1100]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:40:01 nbsd7-64 cron[529]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 23 15:50:00 nbsd7-64 cron[555]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:50:00 nbsd7-64 cron[899]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 28 17:40:00 nbsd7-64 cron[559]: (root) CMD START (/usr/libexec/atrun)
Nov 28 17:40:00 nbsd7-64 cron[72]: (root) CMD FINISH (/usr/libexec/atrun)
Nov 28 17:50:16 nbsd7-64 cron[625]: (root) CMD START (/usr/libexec/atrun)
Nov 28 17:50:16 nbsd7-64 cron[1235]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 10:30:03 nbsd7-64 cron[1617]: (root) CMD START (/usr/libexec/atrun)
Dec 15 10:30:03 nbsd7-64 cron[2243]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 10:40:00 nbsd7-64 cron[334]: (root) CMD START (/usr/libexec/atrun)
Dec 15 10:40:00 nbsd7-64 cron[73]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 10:50:00 nbsd7-64 cron[537]: (root) CMD START (/usr/libexec/atrun)
Dec 15 10:50:00 nbsd7-64 cron[891]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 11:00:00 nbsd7-64 cron[162]: (root) CMD START (/usr/bin/newsyslog)
Dec 15 11:00:00 nbsd7-64 cron[562]: (root) CMD START (/usr/libexec/atrun)
Dec 15 11:00:00 nbsd7-64 cron[580]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 11:00:20 nbsd7-64 cron[869]: (root) CMD FINISH (/usr/bin/newsyslog)
Dec 15 11:10:00 nbsd7-64 cron[201]: (root) CMD START (/usr/libexec/atrun)
Dec 15 11:10:00 nbsd7-64 cron[209]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 15 11:20:00 nbsd7-64 cron[626]: (root) CMD START (/usr/libexec/atrun)
Dec 15 11:20:00 nbsd7-64 cron[665]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 23 10:00:00 nbsd7-64 cron[927]: (root) CMD START (/usr/bin/newsyslog)
Dec 23 10:00:00 nbsd7-64 cron[967]: (root) CMD START (/usr/libexec/atrun)
Dec 23 10:00:00 nbsd7-64 cron[354]: (root) CMD FINISH (/usr/libexec/atrun)
Dec 23 10:00:09 nbsd7-64 cron[975]: (root) CMD FINISH (/usr/bin/newsyslog)
Dec 28 15:40:03 nbsd8-64 cron[1936]: (root) CMD START (/usr/libexec/atrun)
Dec 28 15:40:04 nbsd8-64 cron[14238]: (root) CMD FINISH (/usr/libexec/atrun) Dec 28 15:50:01 nbsd8-64 cron[3133]: (root) CMD START (/usr/libexec/atrun)
Dec 28 15:50:01 nbsd8-64 cron[2765]: (root) CMD FINISH (/usr/libexec/atrun)

--
Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thomas Schweikle <[email protected]> wrote:

Hi!

anyone having seen crond running, but only sporadic executing commands?

In NetBSD, I have not, but my cronlog does not contain this
string 'nbsd7-64 cron[....]'. But what is the issue ? Your
log has similar entries to mine.

Nov 23 15:00:00 nbsd7-64 cron[739]: (root) CMD FINISH (/usr/libexec/atrun) Nov 23 15:10:00 nbsd7-64 cron[360]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:10:00 nbsd7-64 cron[354]: (root) CMD FINISH (/usr/libexec/atrun) Nov 23 15:20:00 nbsd7-64 cron[433]: (root) CMD START (/usr/libexec/atrun)
Nov 23 15:20:00 nbsd7-64 cron[1145]: (root) CMD FINISH (/usr/libexec/atrun)

<snit>

John

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2017-01-03, Thomas Schweikle <[email protected]> wrote:

Hi!

anyone having seen crond running, but only sporadic executing commands?

[...]

Nov 28 17:50:16 nbsd7-64 cron[625]: (root) CMD START (/usr/libexec/atrun)
Nov 28 17:50:16 nbsd7-64 cron[1235]: (root) CMD FINISH (/usr/libexec/atrun) Dec 15 10:30:03 nbsd7-64 cron[1617]: (root) CMD START (/usr/libexec/atrun) Dec 15 10:30:03 nbsd7-64 cron[2243]: (root) CMD FINISH (/usr/libexec/atrun)

If that is the whole log then that is indeed unusual and never seen
anything like that. I would expect to see atrun every 10 minutes, not
skipping 2 weeks between run.

Apart from that I get similar entries (only difference being of course
the hostname), so when it runs it looks like it does what it's supposed
to do.

Has cron been stopped at some point? If you see the system when there
are no cron log entries for 1 hour, what does "ps" say about the running
cron daemon?

C

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2017-01-03, Thomas Schweikle <[email protected]> wrote:

anyone having seen crond running, but only sporadic executing commands? >[...]
Nov 28 17:50:16 nbsd7-64 cron[625]: (root) CMD START (/usr/libexec/atrun)
Nov 28 17:50:16 nbsd7-64 cron[1235]: (root) CMD FINISH (/usr/libexec/atrun) >> Dec 15 10:30:03 nbsd7-64 cron[1617]: (root) CMD START (/usr/libexec/atrun) >> Dec 15 10:30:03 nbsd7-64 cron[2243]: (root) CMD FINISH (/usr/libexec/atrun)

If that is the whole log then that is indeed unusual and never seen
anything like that. I would expect to see atrun every 10 minutes, not >skipping 2 weeks between run.

Oddly enough I recently have the same experience; crond running and jobs
get logged but the scripts aren't actually running, or not running
correctly. I ended up doing a 'crontab -r' and recreating the cron file
and things are again working as expected. Maybe I somehow introduced a non-printing character into the cron file? Don't know but things are
working again - yay.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)