* bug#36510: confusing mcron logging
@ 2019-07-05 13:35 Robert Vollmert
2019-07-05 20:37 ` Ludovic Courtès
2022-01-04 13:21 ` bug#36510: [PATCH v3] base: Annotate output with job information Dale Mellor
0 siblings, 2 replies; 9+ messages in thread
From: Robert Vollmert @ 2019-07-05 13:35 UTC (permalink / raw)
To: 36510
I have two mcron jobs on my system, certbot renewal and
a handwritten and currently buggy guile job. This is an
excerpt from /var/log/mcron.log:
>>>>>
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert not yet due for renewal
Keeping the existing certificate
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal; no action taken.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Acquiring or renewing certificate: garp.vllmrt.net
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert not yet due for renewal
Keeping the existing certificate
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal; no action taken.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Acquiring or renewing certificate: garp.vllmrt.net
Backtrace:
9 (apply-smob/1 #<catch-closure 5cf300>)
In ice-9/boot-9.scm:
829:9 8 (catch mcron-error #<procedure 7fe67c318d28 at mcron/s?> ?)
In mcron/scripts/mcron.scm:
99:7 7 (_)
In mcron/base.scm:
234:12 6 (_ #<continuation 5ad660>)
In srfi/srfi-1.scm:
640:9 5 (for-each #<procedure run-job (job)> (#<<job> user: #(?>))
In mcron/base.scm:
186:10 4 (run-job #<<job> user: #("root" "x" 0 0 "System adminis?>)
In ice-9/eval.scm:
293:34 3 (_ #(#(#<directory (mcron scripts mcron) 6a9c80>)))
182:19 2 (proc #(#(#<directory (mcron scripts mcron) 6a9c80>)))
142:16 1 (compile-top-call _ (7 . get-string-all) ((10 (# . #) ?)))
In unknown file:
0 (%resolve-variable (7 . get-string-all) #<directory (mc?>)
ERROR: In procedure %resolve-variable:
Unbound variable: get-string-all
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert not yet due for renewal
Keeping the existing certificate
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal; no action taken.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Acquiring or renewing certificate: garp.vllmrt.net
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert not yet due for renewal
Keeping the existing certificate
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal; no action taken.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Acquiring or renewing certificate: garp.vllmrt.net
<<<<<
It’s impossible to tell what output is from which job; which jobs succeeded or
didn’t; when they ran.
Suggestions:
- mcron should log the timestamp and a job id of every job when it starts
- mcron should log the timestamp and status and job id of every job when it finishes
- job output should be prefixed by some job id
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2019-07-05 13:35 bug#36510: confusing mcron logging Robert Vollmert @ 2019-07-05 20:37 ` Ludovic Courtès 2019-07-05 20:48 ` Robert Vollmert 2021-08-18 0:53 ` Maxim Cournoyer 2022-01-04 13:21 ` bug#36510: [PATCH v3] base: Annotate output with job information Dale Mellor 1 sibling, 2 replies; 9+ messages in thread From: Ludovic Courtès @ 2019-07-05 20:37 UTC (permalink / raw) To: Robert Vollmert; +Cc: 36510 Hi, Robert Vollmert <rob@vllmrt.net> skribis: > Suggestions: > - mcron should log the timestamp and a job id of every job when it starts > - mcron should log the timestamp and status and job id of every job when it finishes > - job output should be prefixed by some job id +1! +3 even. :-) Something that can help debugging to some extent (but is definitely no substitute for what you suggest above!) is ‘sudo herd schedule mcron’. I use that to manually run jobs that appear not to work as expected. Ludo’. ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2019-07-05 20:37 ` Ludovic Courtès @ 2019-07-05 20:48 ` Robert Vollmert 2021-08-18 0:53 ` Maxim Cournoyer 1 sibling, 0 replies; 9+ messages in thread From: Robert Vollmert @ 2019-07-05 20:48 UTC (permalink / raw) To: Ludovic Courtès; +Cc: 36510 > On 5. Jul 2019, at 22:37, Ludovic Courtès <ludo@gnu.org> wrote: > Something that can help debugging to some extent (but is definitely no > substitute for what you suggest above!) is ‘sudo herd schedule mcron’. > I use that to manually run jobs that appear not to work as expected. That only works for non-guile jobs though as far as I understand, where 'herd schedule mcron' prints a store path. https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36430 ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2019-07-05 20:37 ` Ludovic Courtès 2019-07-05 20:48 ` Robert Vollmert @ 2021-08-18 0:53 ` Maxim Cournoyer 2021-08-24 12:32 ` Maxim Cournoyer 2021-08-30 9:49 ` Ludovic Courtès 1 sibling, 2 replies; 9+ messages in thread From: Maxim Cournoyer @ 2021-08-18 0:53 UTC (permalink / raw) To: Ludovic Courtès; +Cc: 36510, Robert Vollmert Hello Robert and Ludovic, Ludovic Courtès <ludo@gnu.org> writes: > Hi, > > Robert Vollmert <rob@vllmrt.net> skribis: > >> Suggestions: >> - mcron should log the timestamp and a job id of every job when it starts >> - mcron should log the timestamp and status and job id of every job when it finishes >> - job output should be prefixed by some job id > > +1! +3 even. :-) I've sent a patch upstream that implements all of the above [0]. I've been using it on my system, it works well so far! I'm also keeping this work in a public Notabug git repo [1]. Hopefully it gets merged and Guix System can reap the benefits :-). Thanks for the suggestions! Maxim [0] https://lists.gnu.org/archive/html/bug-mcron/2021-08/msg00005.html [1] https://notabug.org/apteryx/mcron ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2021-08-18 0:53 ` Maxim Cournoyer @ 2021-08-24 12:32 ` Maxim Cournoyer 2021-08-30 9:49 ` Ludovic Courtès 1 sibling, 0 replies; 9+ messages in thread From: Maxim Cournoyer @ 2021-08-24 12:32 UTC (permalink / raw) To: Ludovic Courtès; +Cc: 36510, Robert Vollmert Hello, I sent a v3 of the output annotation patch [0], which no longer blocks reading the output of long-running child processes. I've reconfigured my system with it, so far so good. [0] https://lists.gnu.org/archive/html/bug-mcron/2021-08/msg00008.html ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2021-08-18 0:53 ` Maxim Cournoyer 2021-08-24 12:32 ` Maxim Cournoyer @ 2021-08-30 9:49 ` Ludovic Courtès 1 sibling, 0 replies; 9+ messages in thread From: Ludovic Courtès @ 2021-08-30 9:49 UTC (permalink / raw) To: Maxim Cournoyer; +Cc: 36510, Robert Vollmert Hello Maxim, Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis: > Ludovic Courtès <ludo@gnu.org> writes: > >> Hi, >> >> Robert Vollmert <rob@vllmrt.net> skribis: >> >>> Suggestions: >>> - mcron should log the timestamp and a job id of every job when it starts >>> - mcron should log the timestamp and status and job id of every job when it finishes >>> - job output should be prefixed by some job id >> >> +1! +3 even. :-) > > I've sent a patch upstream that implements all of the above [0]. I've > been using it on my system, it works well so far! I'm also keeping this > work in a public Notabug git repo [1]. That’s a much welcome improvement, thank you! Ludo’. ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: [PATCH v3] base: Annotate output with job information. 2019-07-05 13:35 bug#36510: confusing mcron logging Robert Vollmert 2019-07-05 20:37 ` Ludovic Courtès @ 2022-01-04 13:21 ` Dale Mellor 2022-11-21 1:22 ` bug#36510: confusing mcron logging Maxim Cournoyer 1 sibling, 1 reply; 9+ messages in thread From: Dale Mellor @ 2022-01-04 13:21 UTC (permalink / raw) To: 36510, Maxim Cournoyer Hi, sorry for the delay but I've had a bit of time over Christmas to look things over. I've given this a lot of consideration. I am happy to drop compatibility with guile-2.2 and older; I think we can make a minor version bump for this break with legacy. Does this belong in mcron? The mcron source code is currently 3,000 lines, to which you are bringing over 500 new ones to make a facility which is geared towards debugging in the GUIX system (I am all-in on GUIX myself, but mcron is a generic GNU program with use-cases outside of this system). I wonder if this is the best place: perhaps it is shepherd, which is responsible for the /var/log/mcron.log file, to be responsible for the amended logging messages? And then again, isn't this exactly what syslogd does anyway? Most likely timings will be more accurate if they are generated in mcron. In your use-case, of debugging the system, I would think that more specialized messages placed directly in the cron jobs themselves would be a better aid to your work, as you can target them to the problem at hand. And you could send those to syslogd if you wanted. The output is a little unpredictable. The script (which is admittedly somewhat pathological) (job '(next-second '(0 30)) '(begin (display "test: ") (system "date"))) produces 2022-01-04T11:24:00 (...): running... 2022-01-04T11:24:00 (...): Tue 4 Jan 11:24:00 GMT 2022 2022-01-04T11:24:00 (...): test: completed in 0.022s 2022-01-04T11:24:30 (...): running... 2022-01-04T11:24:30 (...): Tue 4 Jan 11:24:30 GMT 2022 2022-01-04T11:25:00 (...): running... 2022-01-04T11:25:00 (...): Tue 4 Jan 11:25:00 GMT 2022 ... But all things considered your changes are generally useful to have, including outside of the GUIX system, and I would very much like to have them there. But to be sure not to break any existing applications, I would like the changes to be opt-in via a command-line switch -l; the --log-format option can remain to customize this (please also make -L a short option alternative; also -D as short for --date-format). I am willing and able to do this work myself in a reasonable time-frame if you would like me to. Best wishes, Dale ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2022-01-04 13:21 ` bug#36510: [PATCH v3] base: Annotate output with job information Dale Mellor @ 2022-11-21 1:22 ` Maxim Cournoyer 2022-11-29 3:31 ` Maxim Cournoyer 0 siblings, 1 reply; 9+ messages in thread From: Maxim Cournoyer @ 2022-11-21 1:22 UTC (permalink / raw) To: Dale Mellor; +Cc: 36510-done Hello Dale, Dale Mellor <mcron-lsfnyl@rdmp.org> writes: > Hi, sorry for the delay but I've had a bit of time over Christmas > to look things over. I've given this a lot of consideration. Apologies for my lack of reply thus far, it seems your mail had fallen in cracks. > > I am happy to drop compatibility with guile-2.2 and older; I think we > can make a minor version bump for this break with legacy. > > > > Does this belong in mcron? The mcron source code is currently > 3,000 lines, to which you are bringing over 500 new ones to > make a facility which is geared towards debugging in the GUIX > system (I am all-in on GUIX myself, but mcron is a generic GNU > program with use-cases outside of this system). I wonder if > this is the best place: perhaps it is shepherd, which is > responsible for the /var/log/mcron.log file, to be responsible > for the amended logging messages? And then again, isn't this > exactly what syslogd does anyway? Most likely timings will be > more accurate if they are generated in mcron. Since Shepherd 0.9+, it now appends logging information to every output it handles, so this feature has indeed become less important, but still useful: I've recently bumped our package of mcron in Guix and I'm using its annotation facility to prepend the process ID to its output. I think the grunt of new lines added must be as documentation and test code, so that's not so bad as it seems I think. > In your use-case, of debugging the system, I would think that > more specialized messages placed directly in the cron jobs > themselves would be a better aid to your work, as you can > target them to the problem at hand. And you could send those > to syslogd if you wanted. Here's a sample output from the Guix build farm: --8<---------------cut here---------------start------------->8--- 2022-11-21 01:56:15 84005 /gnu/store/ypyz886hd7qaw0g8ba5a595dc0qgnj3q-update-guix.gnu.org: running... 2022-11-21 01:59:24 84005 /gnu/store/ypyz886hd7qaw0g8ba5a595dc0qgnj3q-update-guix.gnu.org: Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... 2022-11-21 01:59:24 84005 /gnu/store/ypyz886hd7qaw0g8ba5a595dc0qgnj3q-update-guix.gnu.org: Computing Guix derivation for 'x86_64-linux'... 2022-11-21 01:59:24 84005 /gnu/store/ypyz886hd7qaw0g8ba5a595dc0qgnj3q-update-guix.gnu.org: [2022-11-21T01:56:18+0100] building web site from 'https://git.savannah.gnu.org/git/guix/guix-artwork.git'... 2022-11-21 01:59:24 84005 /gnu/store/ypyz886hd7qaw0g8ba5a595dc0qgnj3q-update-guix.gnu.org: completed in 189.325s 2022-11-21 02:00:00 91665 /gnu/store/xsc4x68avp8nmrf3hgvhd26yl3k90jqz-check-disk-space: running... 2022-11-21 02:00:00 91665 /gnu/store/xsc4x68avp8nmrf3hgvhd26yl3k90jqz-check-disk-space: completed in 0.046s --8<---------------cut here---------------end--------------->8--- The timestamp is now generated by Shepherd, and mcron adds the PID of the job, such as 84005 above. To have some indication of how long the job ran available at a quick glance is very useful for admin purposes. > > > The output is a little unpredictable. The script (which is > admittedly somewhat pathological) > > (job '(next-second '(0 30)) '(begin (display "test: ") > (system "date"))) > > produces > > 2022-01-04T11:24:00 (...): running... > 2022-01-04T11:24:00 (...): Tue 4 Jan 11:24:00 GMT 2022 > 2022-01-04T11:24:00 (...): test: completed in 0.022s > 2022-01-04T11:24:30 (...): running... > 2022-01-04T11:24:30 (...): Tue 4 Jan 11:24:30 GMT 2022 > 2022-01-04T11:25:00 (...): running... > 2022-01-04T11:25:00 (...): Tue 4 Jan 11:25:00 GMT 2022 > ... I've noticed that too, that some jobs somehow escape producing the "completed in x..." message. I'll try looking into that, it's probably a subtle bug. > But all things considered your changes are generally useful to > have, including outside of the GUIX system, and I would very > much like to have them there. But to be sure not to break any > existing applications, I would like the changes to be opt-in > via a command-line switch -l; the --log-format option can > remain to customize this (please also make -L a short option > alternative; also -D as short for --date-format). > > I am willing and able to do this work myself in a reasonable > time-frame if you would like me to. Thank you for taking on yourself the above work, Dale! I was happily surprise to see this change had landed with your improvement on top. I think this Guix issue can now be closed :-). -- Thanks, Maxim ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#36510: confusing mcron logging 2022-11-21 1:22 ` bug#36510: confusing mcron logging Maxim Cournoyer @ 2022-11-29 3:31 ` Maxim Cournoyer 0 siblings, 0 replies; 9+ messages in thread From: Maxim Cournoyer @ 2022-11-29 3:31 UTC (permalink / raw) To: Dale Mellor; +Cc: 36510 Hi, Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: > Dale Mellor <mcron-lsfnyl@rdmp.org> writes: [...] >> The output is a little unpredictable. The script (which is >> admittedly somewhat pathological) >> >> (job '(next-second '(0 30)) '(begin (display "test: ") >> (system "date"))) >> >> produces >> >> 2022-01-04T11:24:00 (...): running... >> 2022-01-04T11:24:00 (...): Tue 4 Jan 11:24:00 GMT 2022 >> 2022-01-04T11:24:00 (...): test: completed in 0.022s >> 2022-01-04T11:24:30 (...): running... >> 2022-01-04T11:24:30 (...): Tue 4 Jan 11:24:30 GMT 2022 >> 2022-01-04T11:25:00 (...): running... >> 2022-01-04T11:25:00 (...): Tue 4 Jan 11:25:00 GMT 2022 >> ... I tried reproducing this, but couldn't, using the latest GNU Shepherd as shipped in Guix. > I've noticed that too, that some jobs somehow escape producing the > "completed in x..." message. I'll try looking into that, it's probably > a subtle bug. I took some time looking at the issue, and it was more straightforward than I had hoped: I was using exec in my job, which was basically hijacking the mcron's forked job process and loosing what it would have normally done upon completion (print status). Turning the 'execl' calls into 'system*' fixed it: --8<---------------cut here---------------start------------->8--- modified guix/hurd.scm @@ -36,14 +36,14 @@ ;; Run 'updatedb' at 3AM every day. #~(job '(next-hour '(3)) (lambda () - (execl #$(file-append findutils "/bin/updatedb") "updatedb" - (string-append "--prunepaths=" - "/gnu/store " - "/media " - "/mnt " - "/tmp " - "/var/tmp " - "/var/lib "))) + (system* #$(file-append findutils "/bin/updatedb") + (string-append "--prunepaths=" + "/gnu/store " + "/media " + "/mnt " + "/tmp " + "/var/tmp " + "/var/lib "))) "updatedb")) (define btrfs-balance-job @@ -52,15 +52,15 @@ ;; low (5%) to minimize wear on the SSD. Runs at 5 AM every 3 days. #~(job '(next-hour-from (next-day (range 1 31 3)) '(5)) (lambda () - (execl #$(file-append btrfs-progs "/bin/btrfs") "btrfs" - "balance" "start" "-dusage=5" "/")) + (system* #$(file-append btrfs-progs "/bin/btrfs") + "balance" "start" "-dusage=5" "/")) "btrfs-balance")) (define btrbk-job #~(job '(next-hour) (lambda () - (execl #$(file-append btrbk "/bin/btrbk") "btrbk" - "-q" "-c" #$(local-file "btrbk.conf") "run")) + (system* #$(file-append btrbk "/bin/btrbk") + "-q" "-c" #$(local-file "btrbk.conf") "run")) "btrbk")) --8<---------------cut here---------------end--------------->8--- -- Thanks, Maxim ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-11-29 3:32 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-07-05 13:35 bug#36510: confusing mcron logging Robert Vollmert 2019-07-05 20:37 ` Ludovic Courtès 2019-07-05 20:48 ` Robert Vollmert 2021-08-18 0:53 ` Maxim Cournoyer 2021-08-24 12:32 ` Maxim Cournoyer 2021-08-30 9:49 ` Ludovic Courtès 2022-01-04 13:21 ` bug#36510: [PATCH v3] base: Annotate output with job information Dale Mellor 2022-11-21 1:22 ` bug#36510: confusing mcron logging Maxim Cournoyer 2022-11-29 3:31 ` Maxim Cournoyer
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/guix.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).