Munin is a great resource monitoring tool. However, it can easily max out the server resource depending on number of monitored devices. I’ve ran into some disk I/O contention issue on my Munin server. I don’t even have that many monitored devices… only eighteen. There are couple ways to speed …..
For home servers I funnel all emails through a single Postfix SMTP relay via a Gmail account. (On Debian 9 you need to install libsasl2-modules first.) Create /etc/postfix/sasl_passwd file with following content (replace the obvious variables): [smtp.gmail.com]:587 [email protected]:$PASS Then generate Postfix map file. This will create /etc/postfix/sasl_passwd.db file. …..
This happens when CentOS do a major version release like from 6 to 7. It doesn’t happen immediately but after the new major version has been released for a while they’ll update repository URL from major.minor (e.g. 6.5) version to just a major (6). So it changes from something like …..
Change minimum rebuild speed: By default Linux SW RAID minimum rebuild speed is quite low by today’s storage standard. Regular mechanical HDD easily performs 50MB+ and a SSD easily performs between 250-500MB. The default RAID rebuild minimum speed is 1MB and maximum is 200MB. While the maximum rebuild speed is fine …..
It’s very easy to move Let’s Encrypt SSL certificates to new server. If you don’t know who Let’s Encrypt certificate authority is… read up here. All you need to do install Let’s Encrypt on new serer first, then transfer the following directories to same location on new server. /etc/letsencrypt/archive/$SITE /etc/letsencrypt/live/$SITE …..
Munin by default probably doesn’t graph MySQL data. It might if you installed Debian’s default MySQL server. Since I’m using MySQL’s repo and installed version 5.7 on my server… Munin doesn’t detect on install and doesn’t monitor my MySQL server. The default setting reading /etc/mysql/debian.cnf file using MySQL user “debian-sys-maint” …..