Skip to content
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

Option to skip disk check for a certain node (also, no swap causes division by zero once again) #55

Closed
zejjnt opened this issue Dec 4, 2023 · 3 comments

Comments

@zejjnt
Copy link

zejjnt commented Dec 4, 2023

One of my USB-hubs has a built-in memory card reader which makes the agent hog huge system resources, never report any data and not prompt any error messages if not manually checking hetrixtools_cron.log.
I don't know how I can assist in the troubleshooting, but here is that log (the device in question is /dev/sdc).

hetrixtools_cron.log

@zejjnt
Copy link
Author

zejjnt commented Dec 4, 2023

Seems like something additional is wrong here; the awk problem remains even after disabling disk health checking.
Is there any way to get any useful info at all except for dissecting the script statement by statement?
hetrixtools_cron2.log

@zejjnt
Copy link
Author

zejjnt commented Dec 4, 2023

Couldn't resist doing a bit of digging. Once again (#38) you assume that everyone has a swap file, just like last time. That's the division by zero. The disk problem is probably a separate issue though but please, not everyone uses swap.

@zejjnt zejjnt changed the title Option to skip disk check for a certain node Option to skip disk check for a certain node (also, no swap causes division by zero once again) label:bug Dec 4, 2023
@zejjnt zejjnt changed the title Option to skip disk check for a certain node (also, no swap causes division by zero once again) label:bug Option to skip disk check for a certain node (also, no swap causes division by zero once again) Dec 4, 2023
@hetrixtools
Copy link
Owner

Hello,

Thank you for reporting these issues.

The division by zero error has now been fixed in version 2.0.10 c76788e

For the disk related issue, please open a support ticket on our platform, as we'll need more info in order to try and reproduce the issue on our testing environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants