infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (INFRA-16254) [mail-archives] loggy does not show errors
Date Thu, 12 Apr 2018 22:51:00 GMT


Sebb commented on INFRA-16254:

The syslog for the date in question is no longer present.
However a local test suggests that syslog only contains the command line for cron jobs.
Errors should be sent to the mail file for the user.
However that does not exist because the file got too big.

Unless a way can be found to ensure that failed cron jobs are recorded in syslog (or another
log file that loggy can handle) then it looks like loggy cannot be used to check for failed
cron jobs

> [mail-archives] loggy does not show errors
> ------------------------------------------
>                 Key: INFRA-16254
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Assignee: Chris Lambertus
>            Priority: Major
> The Kibana entry [1] shows an invalid command line caused by an error in init.pp (since
> /home/modmbox/scripts/ '/x1/
> When I tried this locally, the script failed with an error:
> Traceback (most recent call last):
>   File "/home/modmbox/scripts/", line 20, in <module>
>     BASEPATH=sys.argv[1]
> IndexError: list index out of range
> However AFAICT the error does not appear in Kibana.
> It would be useful to be able to access the raw log files to see where the error appears.
> [1],pause:!f,value:0),time:(from:now-24h,mode:quick,to:now))

This message was sent by Atlassian JIRA

View raw message