Automated Report Trouble After Update to 4.0.2

Graylog Central (peer support)
1

I have an automated report that is set to send via email once a week. Ever since upgrading to Graylog Enterprise 4.0.2 I have had issues. When it hits its weekly time to send, it will send a report every single minute continuously until disabling the report job and restarting the graylog-server service. This report always sent fine before the upgrade. Is anyone experiencing similar issues?

2

Hey @meghan,

do you see any errors in your server log when this situation is happening?

3

what version did you upgrade from? I had/have the same issue with Graylog 4.0.2, was fine on 3.x.

edit: mistyped graylog version

4

it is just the following lines continuously over and over

2021-02-22T15:42:23.854-05:00 WARN  [RemoteBrowserService] Chrome sandboxing is currently disabled. Please validate your security settings!
2021-02-22T15:42:25.023-05:00 INFO  [SystemJobManager] SystemJob <6b9afb70-754e-11eb-9c91-00155df29f17> [org.graylog.plugins.report.scheduler.ReportRenderSystemJob] finished in 21207ms.
2021-02-22T15:43:03.802-05:00 INFO  [ReportPeriodical] Starting report generation for: City of Niles, MI - Weekly Authentication Report
2021-02-22T15:43:03.812-05:00 INFO  [SystemJobManager] Submitted SystemJob <8f5d08f0-754e-11eb-9c91-00155df29f17> [org.graylog.plugins.report.scheduler.ReportRenderSystemJob]
2021-02-22T15:43:03.813-05:00 INFO  [ReportPeriodical] Setting report scheduler configuration: 0 0 16 ? * 2 *
2021-02-22T15:43:03.814-05:00 INFO  [ReportPeriodical] Next report generation will be at: 2021-02-22T16:00Z[UTC]
2021-02-22T15:43:03.945-05:00 INFO  [ProtocolHandshake] Detected dialect: OSS
5

I’m not 100% sure but I know it was 3.x

6

me too… think it was 3.3.8, I’ve turned the report off… and then promptly forgot about it as I moved onto a different task. I’ve just turned it back on to see if “kickin’ it” fixes the issue. I’ll let you know. Otherwise, I’ll probably try changing the time to see if the problem follows and go from there.

7

“kickin’ it” didn’t fix it…

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.