Open uriklagnes opened 6 years ago
error handling the gelf NIF is clearly lacking and you hit one such case.
It seems that you journal is not containing any valid entries or the the real time clock source is not working. Could you some more details of the system this happening on (OS, OS Version, Erlang version, ....)?
NIF? Erlang version? We are in c-land here.
sd_journal_get_monotonic_usec
is failing here. this could be because an entry is handled from a previous boot or other corruption. this would clearly need more detailed error handling. the passed boot_id is not initialized. this could be the issue here. initializing boot_id with sd_id128_get_boot(3)
sounds like the right thing to do.
In my case this was due to lack of persistent journal in specified location.
I installed journal-gateway-gelf as a systemd unit and this assert is firing causing a SIGABRT:
./src/journal-gateway-gelf.c:192: check_timestamps: Assertion `rc == 0' failed