mastodon
4.6.6
Geek, father, blogging on www.claudiokuenzler.com
A new version of check_smart, a #monitoring plugin to monitor hard drives (HDD), solid state drives (SSD) and NVMe drives, is available.
The newest release, 6.18.2, is a bugfix release and fixes a regression introduced in 6.18.1. Using symbolic links as device path - for example in /dev/disk/by-id/ - were broken.
https://www.claudiokuenzler.com/blog/1537/regression-fix-check-smart-monitoring-plugin
And because we can barely catch our breath anymore with yet another #Kernel #vulnerability, we just published our internal #Ansible playbook to mitigate against #copyfail and #dirtyfrag .
https://github.com/infiniroot/ansible-mitigate-copyfail-dirtyfrag
A new version of check_smart, a #monitoring plugin to monitor hard drives, solid state drives and NVMe drives, is available.
The latest release, 6.18.1, is a #security release and fixes a command injection #vulnerability in the handling of the interface parameter.
https://www.claudiokuenzler.com/blog/1535/check-smart-6.18.1-security-fix-vulnerability
After running #PowerDNS for several years, it took until today, that I saw a completely new alert in our #monitoring.
The alert from the monitoring plugin told us about a "mandatory upgrade".
In my latest #blog post I got to the bottom of it: Where this information comes from and why this alert happened today.
https://www.claudiokuenzler.com/blog/1533/powerdns-monitoring-security-release
check_smart 6.18.0 is out!
The newest release fixes a bug in the execution in the plugin's background, where the PATH definition was missing for the sudo command. To my current knowledge only #FreeBSD (or other #BSD) users might have run into that bug.
There's an important enhancement for servers running with #NVME drives, too. The plugin should now detect and alert on input/output errors.
https://www.claudiokuenzler.com/blog/1532/check-smart-6.18.0-sudo-command-path-fix-nvme-io-error
The RabbitMQ queue monitoring broke - because there were no queues.
Sounds weird? It kind of is. The #Perl script, which I've been using for #RabbitMQ monitoring for a very long time, checks for queues and their current values. But when a RabbitMQ server returned no queues at all, this #monitoring plugin just showed a weird (division by zero) error.
https://www.claudiokuenzler.com/blog/1531/monitoring-rabbitmq-queues-handle-no-queue-situation
Upgraded @debian@framapiaf.org , which upgraded #MariaDB to 11.8.
Noticed daily mysqldump runs into warnings.
Attempt to fix led yet to another error, caused by an old config snippet from #Znuny.
Analysis and fix in the latest #blog post.
https://www.claudiokuenzler.com/blog/1530/mysql-upgrade-unknown-variable-max-allowed-packet-znuny-config