-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vector doesn't start after upgrading from v0.33.1-1 to v.0.34.1-1 #19333
Comments
Hi @LinoVieira13, For vector 0.34.1 I cannot reproduce what you describe:
Is the Debug Output you shared above coming from |
Hello @pront, |
I had met the similar situation. The same point is that |
@LinoVieira13 in order to help us debug this:
|
I met the same bug. I tried to upgrade from 0.24.1 to 0.35.0 (aslo for latest 0.37) and it failes to start at PreStart stage. Started it with VECTOR_LOG=DEBUG with strace and it also stucks with my huge config, Ctrl+C can't stop it but it shows log messages
|
What I see with strace of
|
Can someone experiencing this failure share the Vector configuration they are trying to load and exact command they are running? |
Forgot to mention - I run vector under Ubuntu 20.04.04 LTS x64. |
Can't share my config files right now. I'll try to split and test it, i think It might be an issue due to the files count, or a topolgy issue |
Anybody with the problem on stuck |
A note for the community
Problem
Hello,
I'm opening this bug at the request of jszwedko via discord.
So, I'm using an Ubuntu 22.04 machine, and I have vector v0.33.1-1 already installed and working, however, when I try to upgrade the package via Ubuntu APT to version v.0.34.1-1 it fails to start after 1m30s (timeout).
I don't have a /etc/vector/vector.yaml file, because I'm using environment variables to point the VECTOR_CONFIG_DIR to this folder: /etc/vector/conf.d. This is the error when it tries to start the service after the upgrade:
Configuration
Version
vector 0.33.1 (x86_64-unknown-linux-gnu 3cc27b9 2023-10-30 16:50:49.747931844)
Debug Output
Example Data
No response
Additional Context
Vector machine is an LXC host.
References
No response
The text was updated successfully, but these errors were encountered: