ERROR vector_common::shutdown #14591
-
Today when I tried it for the first time, everything was normal, and I ran part of the logs then killed the vector process but the second time I tried the same configuration:
After waiting for a while, there was no INFO about " file_server: vector::internal_events::file::source: Found new file to watch."So I Ctrl + c to stop the vector
my vector version is 0.23.3. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
👋
This implies it reloaded old data, and may not have discovered new files to tail at the time. Forcing shutdown happens when we can gracefully exit the topology within 60 seconds, either due to still having lines to read from open files or having connections open to upstream clients. I'd suggest monitoring Vector's activity either with the internal API:
Or using the |
Beta Was this translation helpful? Give feedback.
👋
This implies it reloaded old data, and may not have discovered new files to tail at the time.
Forcing shutdown happens when we can gracefully exit the topology within 60 seconds, either due to still having lines to read from open files or having connections open to upstream clients.
I'd suggest monitoring Vector's activity either with the internal API:
Or…