syehorov

Have found a reason of this. In elasticsearch/manifests/user.pp: ` elasticsearch_user { $name: ensure => $ensure, configdir => $elasticsearch::configdir, password => $password, }` But in /elasticsearch/manifests/instance.pp: `Stdlib::Absolutepath $configdir = "${elasticsearch::configdir}/${name}",` So,...

As from my side, if it will be done, best way will be to have it configurable field like in SDR#/SDR++

Hello. I faced the same issue and found interesting thing. I have device made by Great Scott Gadgets, and it may work fine for days, but may fail within seconds...

Update: I was wrong. It was good only for a first few hours. Now it is the same issues.

Logs from devel version, latest docker image, amd64 arch. ```[2024-01-18 14:29:24.990903] [info ] [main ] git commit: 4d83913754de5415327042fb389cde5f3178132b [2024-01-18 14:29:24.991017] [info ] [main ] git tag: [2024-01-18 14:29:24.991030] [info ]...

Got it fixed for me when noticed CPU throttling in logs. Have CPU cooling solution upgraded and issue disappeared. About 2 months with no one issue.

1000% reproduced again, and CPU thermal throttling was a culprit. Not sure about root cause for original issue author, but for me it is 100% hardware-related.