-
Notifications
You must be signed in to change notification settings - Fork 147
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
Binary agent not picking up additional disks #307
Comments
Please restart the agent with |
These are the logs with debug level enabled, reapeating over and over again:
|
Thanks, there should be a couple lines that are logged once, immediately after startup, and begin with |
Got you, there you go:
Getting errors with invalid filesystem names, but just to be sure here's the lsblk output for this host:
|
Okay, try You can reference the In this case, you have three partitions with mount points, so those are the ones that the agent can see.
Edit: Also make sure you reload the config after changes with |
Alright, that worked, thanks a ton! So it is only possible to monitor partitions / mount points, not whole disks? Running Proxmox with Ceph, where Ceph disks have no real local mount point, it's impossible to monitor them with Beszel? See outputs below.
|
Correct, we're using gopsutil's disk.Usage, which requires a mount point to calculate usage via the filesystem. Maybe in the future we can attempt to read block counts if there's no mount point, but I haven't looked into it yet to see if that's feasible. For ceph specifically, there appears to be some utility commands that give that info, like |
Using the binary agent on my Proxmox VE as well as Backup servers, it won't pick up and monitor additional disks, just the root filesystem.
As documented, I used lsblk to identify the drives, added them to the beszel-agent.service, reloaded the service-daemon as well as restarting the agent-service, restarted the beszel-hub and even re-added the host - still nothing.
See screenshots below.
The text was updated successfully, but these errors were encountered: