Quick update - mysql & SNMP

Last night I also got a mysql VM and syslog VM up.  After the wiki issue, I figured now was a good time to get the database off the wiki server and onto a dedicated mysql server.  That server will then back up onto the NAS - something that will help me sleep better at night.  The dedicated mysql box is also pretty key for a number of other Linux applications.

I am not certain yet if I should be running postgresql and mysql on the same VM (even though there will be separate VMDKs for DBs, logs, temp, etc (wrong terminology??)).  At any rate, once that's ready and documented, I can really get cracking.  Can't wait to get the Nagios box online as well.

Speaking of which, I've learned a lot about SNMP lately.  The process from trap to Nagios alert is quite involved:
  1. Trap to Nagios host
  2. snmptrapd receives trap
  3. snmptrapd formats trap as per snmptt
  4. snmptt logs the trap and looks up what happens
  5. snmptt runs the EXEC line which submits the result to Nagios
I'd have to consult my documentation for more detail, but that's the gist of it.  Also learned some handy SNMP troubleshooting tips:
  • Use the snmptt debug to get a clear picture of what's going on
  • If you get 'unknown' traps logged, chances are your MIB is outdated or not present
  • Ensure logging is turned on and log directories are correctly specified
  • You can use the net-snmp-tools to manually send a trap from your workstation
Yep, good stuff.  I'll add an SNMP section to the wiki at some point.


Anyways, next step is configuring and documenting the mysql/postgresql VM.

Comments

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

Fixing duplicate SPNs (service principal name)

Logstash to Nagios - alerting based on Windows Event ID