pront
commented
11 months ago Hi @LinoVieira13,
For vector 0.34.1 I cannot reproduce what you describe:
hoot:~$ which vector
/usr/bin/vector
host:~$ vector --version
vector 0.34.1 (x86_64-unknown-linux-gnu 86f1c22 2023-11-16 14:59:10.486846964)
host:~$ VECTOR_CONFIG_DIR=~/vector-config-dir/ vector
2023-12-08T10:21:15.402659Z INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=info,rdkafka=info,buffers=info,lapin=info,kube=info"
2023-12-08T10:21:15.404428Z INFO vector::app: Loading configs. paths=["/home/bits/vector-config-dir"]
2023-12-08T10:21:15.407402Z INFO vector::topology::running: Running healthchecks.
2023-12-08T10:21:15.407471Z INFO vector: Vector has started. debug="false" version="0.34.1" arch="x86_64" revision="86f1c22 2023-11-16 14:59:10.486846964"
2023-12-08T10:21:15.407487Z INFO vector::app: API is disabled, enable by setting `api.enabled` to `true` and use commands like `vector top`.
2023-12-08T10:21:15.407646Z INFO vector::topology::builder: Healthcheck passed.
{"appname":"AnthraX","facility":"local2","hostname":"up.cn","message":"Take a breath, let it go, walk away","msgid":"ID52","procid":1840,"severity":"crit","timestamp":"2023-12-08T10:21:15.408Z","version":1}
{"appname":"b0rnc0nfused","facility":"alert","hostname":"some.xn--fzys8d69uvgm","message":"Great Scott! We're never gonna reach 88 mph with the flux capacitor in its current state!","msgid":"ID717","procid":5058,"severity":"crit","timestamp":"2023-12-08T10:21:16.408Z","version":2}
{"appname":"KarimMove","facility":"user","hostname":"names.ls","message":"You're not gonna believe what just happened","msgid":"ID94","procid":5582,"severity":"debug","timestamp":"2023-12-08T10:21:17.408Z","version":1}
^C2023-12-08T10:21:17.796252Z INFO vector::signal: Signal received. signal="SIGINT"
2023-12-08T10:21:17.796317Z INFO vector: Vector has stopped.
2023-12-08T10:21:17.797442Z INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="print, parse_logs, dummy_logs" time_remaining="59 seconds left"
{"appname":"jesseddy","facility":"local0","hostname":"we.associates","message":"Maybe we just shouldn't use computers","msgid":"ID559","procid":8294,"severity":"err","timestamp":"2023-12-08T10:21:18.408Z","version":2}
host:~$ VECTOR_CONFIG_DIR=~/vector-config-dir/ vector validate
√ Loaded ["/home/bits/vector-config-dir"]
x Could not create subdirectory "validate_tmp" inside of data dir "/var/lib/vector/": Permission denied (os error 13)
host:~$ sudo VECTOR_CONFIG_DIR=~/vector-config-dir/ vector validate
√ Loaded ["/home/bits/vector-config-dir"]
√ Component configuration
√ Health check "print"
-----------------------------------------
ValidatedIs the Debug Output you shared above coming from vector 0.33.1 or vector 0.34.1?
LinoVieira13
fisheax
r3code
jszwedko
Skunnyk
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