Graylog2 / Graylog2/graylog2-server

Cron Event Def broke, is no longer running despite being enabled

Open
#26,012 2 comments 0 reactions 0 assignees View on GitHub
bug triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

I have an event def that is triggered every day and usually multiple times a day. It has not triggered since 5/12 despite there being logs that should have triggered it.

The event def appears to not be actually scheduled/running.

Image

Image

Image

For context this seemed to occur after updating the kernel from 5.x to 6.8. Not sure if that is relevant. This is the last graylog was started/restarted (May 12)

## Expected Behavior

Event Defs do not suddenly and unexpectedly break.

## Current Behavior

Cron Event Def no longer works.

## Possible Solution

## Steps to Reproduce (for bugs)

1.
2.
3.
4.

## Context

## Your Environment

* Graylog Version:
* Java Version:
* OpenSearch Version:
* MongoDB Version:
* Operating System:
* Browser version:

## Checklist
[] This issue fix need to be backported.
[] Does this issue have **security** implications?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.