-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
[Bug]: Network interfaces are not picked up at boot #466
Comments
Thanks for reporting this! Looks like we might need to swap So instead of this: [Unit]
Description=Beszel Agent Service
After=network.target We would want this: [Unit]
Description=Beszel Agent Service
Wants=network-online.target
After=network-online.target I'll see if I can replicate and whether this change fixes the issue. |
Changed the systemd service to below and now the interfaces are there after a reboot.
|
Great, thanks for checking! I'll update the install script and docs. I may add a check for this in the agent, but for now here's a fix: sudo sed -i 's/^After=network.target$/After=network-online.target\nWants=network-online.target/' /etc/systemd/system/beszel-agent.service
sudo systemctl daemon-reload
sudo systemctl restart beszel-agent.service |
Cool! Thanks! |
Description
Might be related to #416
When the binary agents starts after the system is start up, it does not pick up the network interfaces to collect the metrics. They are not shown in the agents status. I noticed this on mulitple x86 and arm64 machines
I need to restart the agent again for the network to be picked up. Seems we might need a bigger delay for the network to be fully really ?
Expected Behavior
Network interfaces are picked up when the agent starts
Steps to Reproduce
OS / Architecture
amd64 & arm64
Beszel version
0.9.1
Installation method
Binary
Configuration
Hub Logs
Agent Logs
The text was updated successfully, but these errors were encountered: