Replies: 6 comments
-
try latest 1.0.7 |
Beta Was this translation helpful? Give feedback.
-
Same result with 'latest' (no 1.0.7 tag yet)
Strangely also now, 1.0.5 is are entering a crashbackoff loop without anything unusual being logged
Is there a debug or other additional logging I can do to see why it might be crashing now? In included the resource limits in my latest tests (CPU and memory) because it started crashing the Kubernetes worker nodes if I ran it without (assuming that was the memory issues alluded to in other issues/discussion) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
try thr new dev tag and please report back. it should scan dir. |
Beta Was this translation helpful? Give feedback.
-
With :dev tag. Same results
|
Beta Was this translation helpful? Give feedback.
-
Saw in the other issue/thread that the ghrc images weren't updated. I tried the 1.1.0 image from dockerhub and can report that the logs are loading fine in my configuration now. Glad to see the OTLP support also. Thanks! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
With a working 1.0.5 configuration, changing to the 1.0.6 release, no logs are read but no errors shown in logs that I can see. Was there a breaking change or something I missed? I'm using a mounted NFS folder with two subfolders, both listed for log reading. Snipped below
Beta Was this translation helpful? Give feedback.
All reactions