action #169690
closedlogwarn repeatedly sending openssl related problems. Is the state file stuck?
0%
Description
Tina commented logwarn is stuck.
Oliver changed recipient from o3-admins to him self but when he call /opt/openqa-logwarn/pretty_logwarn /var/log/openqa manually he doesn't see any output. he is monitoring and he will re-enable original recipients later if there are no more messages
Updated by okurz about 1 month ago
- Copied from action #169684: [alert] (Failed systemd services alert (except openqa.suse.de) Salt Uk02cifVkz) added
Updated by tinita about 1 month ago
- Related to action #128591: [openqa_logwarn] logwarn reports the same entry over and over size:M added
Updated by tinita about 1 month ago
- Related to action #168091: logwarn: "Publishing opensuse.openqa.job.done failed: SSL connect attempt failed" added
Updated by okurz about 1 month ago
yesterday evening I received two more emails. After that logwarn recovered itself. Probably because the source log file was rotated and that there were less entries to report about left. /var/lib/logwarn/var_log_openqa was updated with timestamp Nov 12 12:10. I have enabled the original email target o3-admins@suse.de again
Updated by okurz about 1 month ago
- Status changed from Feedback to Resolved
No more email at :10 so problem fixed.
Updated by okurz about 1 month ago
I found https://github.com/archiecobbs/logwarn/issues/5 'logwarn reports all "matches" every time it executes' but that one was also resolved due to not being able to reproduce anymore after some time. Probably there it was also the same that a rotated log fixed the issue.