[opensuse] logwatch and logdigest both fail
openSUSE Leap 42.2 server logwatch and logdigest both fail since 09 Nov 17 with: running daily cronjob scripts Terminated SCRIPT: logdigest exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate and running daily cronjob scripts Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate /etc/logrotate.conf weekly rotate 4 create dateext compresscmd /usr/bin/xz uncompresscmd /usr/bin/xzdec compressext .xz include /etc/logrotate.d wtf help pls :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-11-19 18:42, Patrick Shanahan wrote:
openSUSE Leap 42.2 server
logwatch and logdigest both fail since 09 Nov 17 with:
running daily cronjob scripts
Terminated SCRIPT: logdigest exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate
and
running daily cronjob scripts
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate
/etc/logrotate.conf
weekly rotate 4 create dateext compresscmd /usr/bin/xz uncompresscmd /usr/bin/xzdec compressext .xz include /etc/logrotate.d
wtf
help pls :)
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-? I don't understand. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R.
On 2017-11-19 18:42, Patrick Shanahan wrote:
openSUSE Leap 42.2 server
logwatch and logdigest both fail since 09 Nov 17 with:
running daily cronjob scripts
Terminated SCRIPT: logdigest exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate
and
running daily cronjob scripts
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate
/etc/logrotate.conf
weekly rotate 4 create dateext compresscmd /usr/bin/xz uncompresscmd /usr/bin/xzdec compressext .xz include /etc/logrotate.d
wtf
help pls :)
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-?
I don't understand.
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
So somehow your logrotate job involves logwatch and/or logdigest? I'm not sure what those are. -- Per Jessen, Zürich (2.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2017-11-19 at 13:55 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 13:07]:
On 2017-11-19 18:42, Patrick Shanahan wrote:
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-?
I don't understand.
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
Yes, I see the word logrotate there. What does it have to do with logdigest/logwatch? I assume those work on the live log, not on the dead one being rotated out. Nor do I see entries for logdigest/logwatch in the logrotate config. You have to explain more :-) - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloR5fMACgkQtTMYHG2NR9WjjgCcD283vGqTWa5E5QvFQwZzSrIb TocAn3Ye1rYDAi1K/rN4CV20Ix9cmvxf =Ox/W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
On Sunday, 2017-11-19 at 13:55 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 13:07]:
On 2017-11-19 18:42, Patrick Shanahan wrote:
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-?
I don't understand.
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
Yes, I see the word logrotate there. What does it have to do with logdigest/logwatch? I assume those work on the live log, not on the dead one being rotated out. Nor do I see entries for logdigest/logwatch in the logrotate config.
nor do I.
You have to explain more :-)
that line was included because it was in the error notice email from cron: Subject: cronjob@wahoo - daily - FAILURE logdigest is a bash script, /etc/cron.daily/logdigest logwatch is a perl invocation with many "rules"/subscripts afaikc both stopped working at the same time, 10 Nov seems quite possible a system reason rather than cron/logdigest/logwatch. but ... removed both packages and config files, reinstalled ran with default config logwatch does not complete and logdigest shows no output other than the cron mail edited the configs to match my desires with same result, failure no changes to logdigest, logwatch (or logrotate) in the last year (by me and only I have access). tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2017-11-20 at 08:35 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 15:25]:
On Sunday, 2017-11-19 at 13:55 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 13:07]:
On 2017-11-19 18:42, Patrick Shanahan wrote:
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-?
I don't understand.
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
Yes, I see the word logrotate there. What does it have to do with logdigest/logwatch? I assume those work on the live log, not on the dead one being rotated out. Nor do I see entries for logdigest/logwatch in the logrotate config.
nor do I.
You have to explain more :-)
that line was included because it was in the error notice email from cron: Subject: cronjob@wahoo - daily - FAILURE
Ah, you did not say that before. That email often includes, when there is an error in one job, output of other cronjobs that are not in error. Thus logrotate is not involved, don't even look at it. You will have to look at the documentation to find out what the "RETURNCODE = 143" means :-( Notice that the text you have is only this: running daily cronjob scripts Terminated SCRIPT: logdigest exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows not this, IMO: compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate Ie, IMO there is no "output" at all from logdigest, only the error code. I suggest you try running it in a terminal instead, if possible. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloS29gACgkQtTMYHG2NR9UtYwCfQELLyKRoQ3X6KIEwFvfptPp4 +KUAn1DiwTrhi7dRs+qkKapfxWEBmT3h =hvV8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2017-11-20 at 08:35 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 15:25]:
On Sunday, 2017-11-19 at 13:55 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 13:07]:
On 2017-11-19 18:42, Patrick Shanahan wrote:
Why are you looking at logrotate, then state a problem with logwatch/logdigest? :-?
I don't understand.
Terminated SCRIPT: 0logwatch exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate ^^^^^^^^^^^
Yes, I see the word logrotate there. What does it have to do with logdigest/logwatch? I assume those work on the live log, not on the dead one being rotated out. Nor do I see entries for logdigest/logwatch in the logrotate config.
nor do I.
You have to explain more :-)
that line was included because it was in the error notice email from cron: Subject: cronjob@wahoo - daily - FAILURE
Ah, you did not say that before.
That email often includes, when there is an error in one job, output of other cronjobs that are not in error. Thus logrotate is not involved, don't even look at it.
You will have to look at the documentation to find out what the "RETURNCODE = 143" means :-(
Notice that the text you have is only this:
running daily cronjob scripts
Terminated SCRIPT: logdigest exited with RETURNCODE = 143. SCRIPT: output (stdout && stderr) follows
not this, IMO:
compress_ext is /usr/bin/xz compress_ext was changed to .xz SCRIPT: logrotate
Ie, IMO there is no "output" at all from logdigest, only the error code.
I suggest you try running it in a terminal instead, if possible.
yes, that is what I did and got no output. did not run debug. cron return code 143 indicates sigterm which probably results from me killing the inactive process (after several hours). I have been holding off rebooting the server but it has an updated kernel. it is headless and if I encounter problems requires effort I don't look forward to. guess I need to bite the bullettttt. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2017-11-20 at 10:07 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-20-17 08:45]:
On Monday, 2017-11-20 at 08:35 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 15:25]:
Ie, IMO there is no "output" at all from logdigest, only the error code.
I suggest you try running it in a terminal instead, if possible.
yes, that is what I did and got no output. did not run debug.
You probably need strace or ltrace.
cron return code 143 indicates sigterm which probably results from me killing the inactive process (after several hours).
Oh :-(
I have been holding off rebooting the server but it has an updated kernel. it is headless and if I encounter problems requires effort I don't look forward to. guess I need to bite the bullettttt.
Sorry. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloTPZ0ACgkQtTMYHG2NR9URoACeLWzG4o1qiJfZjvDCRs18CEBy M6AAn3VwsIvvP5mZ0INSX0qtk2A8jWpi =eAdz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2017-11-20 at 10:07 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-20-17 08:45]:
On Monday, 2017-11-20 at 08:35 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [11-19-17 15:25]:
Ie, IMO there is no "output" at all from logdigest, only the error code.
I suggest you try running it in a terminal instead, if possible.
yes, that is what I did and got no output. did not run debug.
You probably need strace or ltrace.
cron return code 143 indicates sigterm which probably results from me killing the inactive process (after several hours).
Oh :-(
I have been holding off rebooting the server but it has an updated kernel. it is headless and if I encounter problems requires effort I don't look forward to. guess I need to bite the bullettttt.
Sorry.
ok, reboot headless 42.2 server w/o problem and logdigest and logwatch now function perfectly, afaics. must have been a perl change ???, but logdigest is bash...... I don't have a kluee -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R.
-
Patrick Shanahan
-
Per Jessen