vector
refuses to start when connectivity to one/any external service is not working
#20382
Labels
domain: config
Anything related to configuring Vector
domain: observability
Anything related to monitoring/observing Vector
type: bug
A code related bug.
A note for the community
Problem
When running
vector
on RHEL9, the file/usr/lib/systemd/system/vector.service
contains the lineThis means vector will refuse to start-up if an external connection is not currently available, instead of starting up then retrying the connection, which is what it would do if the connection had gone down after it had successfully started.
From our config, I tried removing
and removing this from every service
but
vector validate
still fails causing the service to refuse to start.I would suggest
ExecStartPre=/usr/bin/vector validate
in thevector.system
file could have either--no-environment
or--skip-healthchecks
added sovector
will start up & retry the external connection once started, which is what it would do if the connection had failed during normal operation.Because we use
vector
to run other data migration services, in this case aggregating metrics, having them all fail because one (or more) is not working is not really a useful mode of operation.Configuration
Version
vector 0.37.0 (x86_64-unknown-linux-gnu c1da408 2024-03-26 13:41:34.870460047)
Debug Output
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: