- observium - lists.observium.org

Moving obvsevium to a new host
by Ryan, Spencer J. 19 Jul '14

19 Jul '14

Hi All, We are going to migrate our Observium install (paid) to a different VM, same architecture and everything. I ended up pulling down the latest version from SVN, but to move the actual data over do I need to move anything other than the RRD directory, the config file, and the MySQL database? Thanks! -Spencer _______________________________________________________________ NOTICE TO PERSONS SUBJECT TO UNITED STATES TAXATION (MCPS) DISCLOSURE UNDER TREASURY CIRCULAR 230: The United States Federal tax advice, if any, contained in this document and its attachments may not be used or referred to in the promoting, marketing or recommending of any entity, investment plan or arrangement, nor is such advice intended or written to be used, and may not be used, by a taxpayer for the purpose of avoiding Federal tax penalties. _______________________________________________________________

3 3

Housekeeping script
by Tom Laermans 18 Jul '14

18 Jul '14

Hi everyone, Yesterday I committed a housekeeping script to clean up after Observium. If you have a nice number of devices combined with a long running time of Observium, you're sure to have a gigantic database of event log, syslog and performance timing information. Some of you have resorted to periodically truncating tables - fear no more, housekeeping.php is here! You have a choice of specifying either -a for all modules or s, e, r, p and/or t for specific things. Apart from that, there are options in the configuration to set before most of these things actually do anything. What it does: -s Cleans up syslog data, based on the age of the entries. Configured by $config['housekeeping']['syslog']['age'] = 0; // Maximum age of syslog entries in seconds; 0 to disable i.e. 7*86400 for 7 days. -e Cleans up eventlog data, based on the age of the entries. Configured by $config['housekeeping']['eventlog']['age'] = 0; // Maximum age of eventlog entries in seconds; 0 to disable i.e. 30*86400 for 30 days. -r Cleans up RRD files, there are 2 options here: Cleanup of RRD files with a modification time of a certain age. Ports that are gone, sensors that are gone, erroneaously created RRD files due to bugs or hardware changes, etc. Configured by $config['housekeeping']['rrd']['age'] = 0; // Maximum age of unused rrd files in seconds before automatically purging; 0 to disable i.e. 90*86400 for 90 days. Cleanup of invalid RRD files. Requires $config['file'] to be set correctly to the path of the "file" magic utility. Runs over all .rrd files to see if they are identified as RRDTool Databases. They can sometimes get corrupted (0 bytes, half a file) when your disk/ramdrive is full. When they exist, they are not recreated even if they're invalid. Consequently RRDtool refuses to add data into them as they are not valid RRD database files. This scripts deletes any .rrd file not identified as RRDTool. Configured by $config['housekeeping']['rrd']['invalid'] = TRUE; // Delete .rrd files that are not valid RRD files (eg created with a full disk) Note: this defaults to true currently. Handle with care. -p Cleans up deleted ports. You can do this manually by using the purge button in the web interface, but one could probably safely assume if a port has not returned after 30 days it really is gone. Shorter could be useful in your environment, mine is set to 7 days. Configured by $config['housekeeping']['deleted_ports']['age'] = 0; // Maximum age of deleted ports in seconds before automatically purging; 0 to disable i.e. 30*86400 for 30 days. -t: Cleans up perf time information. Observium keeps performance times per module, per device and per run. This quickly accumulates into a giant number of rows in the database. Configured by $config['housekeeping']['timing']['age'] = 0; // Maximum age of timing (discovery and poll time) entries in seconds; 0 to disable i.e. 7*86400 for 7 days. Housekeeping logs into housekeeping.log in the log_dir. (*) I recommend putting this into cron, daily or weekly (yes, even though the age is set in seconds, I don't recommend running it every minute ;), but only after you've run it manually once. It'll take quite a while the first time to clean up large databases. The "check for invalid RRD files" is probably quite I/O heavy. i'll be documenting this on the wiki soonish. (*) log_dir was also added as a new configuration directive, it defaults to ${installdir}/logs which will be created automatically for you if possible. Tom

6 10

alert temp checker
by Benoit Lambert 17 Jul '14

17 Jul '14

Hello again, 6 temp_greater_65<https://syst3092.bellnordiq.net/alert_check/alert_test_id=6/> Temperature is greater than 65 Celsius! sensor_value greater 65 * temperature 69 0/0/0/0/69 6 temp_greater_65<https://syst3092.bellnordiq.net/alert_check/alert_test_id=6/> Temperature is greater than 65 Celsius! sensor_value greater 65 * sensor_class equals temperature 69 0/0/0/0/69 Neither of these seems to work... It's not checking them, can anyone explain why? Any help would be greatly appreciated. :)

1 0

Issue with discovery.php -h all and certain cisco devices
by David Lagace 17 Jul '14

17 Jul '14

Hello, I've run into a problem where the discovery cron seems to error out. I noticed this in checking the polling times where it was at almost 3 days. I ran discovery.php -h all manually from the shell and noticed it would error out to prompt when scanning the same switch everytime. When I put the device causing the issue in ignore it would go through untill it hit another device that errrored it out. If I run it on the host only it also seems to error out: <SNIP> ./discovery.php -h mksc-dob-lab-sw1 Observium v0.14.7.5654 Discovery Current Revision : 5654 New Revision : 5659 mksc-dob-lab-sw1 433 ios (cisco) OLD: ios, NEW: ios --- Ports : ........................................................... Port Stacks: Processors : CISCO-ENTITY-QFP-MIB CISCO-PROCESS-MIB . hrDevice: Memory : CISCO-ENTITY-QFP-MIB CISCO-ENHANCED-MEMPOOL-MIB CISCO-MEMORY-POOL-MIB ... HOST-RESOURCES-MIB IPv4 Addresses : . IPv6 Addresses : Sensors: CISCO-ENTITY-SENSOR-MIB CISCO-ENVMON-MIB .. Fans . ENTITY-SENSOR-MIB Storage : Inventory: Physical Inventory : ............................................................... hrDevice : Discovery protocols: LLDP-MIB CISCO-CDP-MIB .obs@MTPTSMON01:/opt/observium </SNIP> Here with added debug <SNIP> SQL[SELECT * FROM `ports` WHERE `device_id` = '433' AND `ifIndex` = '10101'] SQL[SELECT `device_id` FROM `devices` WHERE `sysName` = 'MKSC-DOB-1A-ASW1.MKSC.CA' OR `hostname` = 'MKSC-DOB-1A-ASW1.MKSC.CA'] SQL[SELECT `port_id` FROM `ports` WHERE (`ifDescr` = 'GigabitEthernet3/0/41' OR `ifName` = 'GigabitEthernet3/0/41') AND `device_id` = '263'] SQL[SELECT * FROM `links` WHERE `local_port_id` = '26157' AND `remote_hostname` = 'MKSC-DOB-1A-ASW1.MKSC.CA' AND `protocol` = 'cdp' AND `remote_port` = 'GigabitEthernet3/0/41'] . SQL[SELECT * FROM `ports` WHERE `device_id` = '433' AND `ifIndex` = '10104'] SQL[SELECT `device_id` FROM `devices` WHERE `sysName` = 'Blee' OR `hostname` = 'Blee'] PHP Fatal error: Call to undefined function nicecase() in /opt/observium/includes/discovery/functions.inc.php on line 151 Fatal error: Call to undefined function nicecase() in /opt/observium/includes/discovery/functions.inc.php on line 151 </SNIP> Anyone seen this issue? Thanks for your help! --Dave

2 1

Barracuda Spam Firewall Support
by Sveatoslav Persianov 17 Jul '14

17 Jul '14

Hello Observium Team, We bought an Observium Pro subscription and found out that Barracuda Spam Firewall devices are not supported. Would you be so kind to give an estimation, when Observium will support these devices, or if you actually plan to add them to supported devices list? Thank you. Best regards, Sveatoslav PERSIANOV Informational Systems Engineer Informational Systems Services Department S.E. Special Telecommunications Center Tel : +373 60 300 591 Email : sveatoslav.persianov(a)cts.md Web : www.cts.md Acest mesaj si orice fisiere atasate acestuia sunt permise spre utilizare doar destinatarului si poate contine informatie cu acces restrictionat. Daca nu sunteti un destinatar sau autorizat in alt mod de a primi acest mesaj, va aducem la cunostinta ca dezvaluirea, copierea sau distribuirea acestui mesaj este strict interzisa si poate fi ilegala. Daca ati primit acest mesaj din greseala, va rugam sa informati imediat IS CTS la adresa de raspuns si sa stergeti acest mesaj din sistem. This e-mail message and any attachments are only for the use of the intended recipient and may contain confidential information. If you are not an addressee or otherwise authorized to receive this message, you are hereby notified that any disclosure, copying or distribution of this message is strictly prohibited and may be unlawful. If you have received this email by mistake, please inform S.E. CTS immediately by reply e-mail and delete this message from your system.

2 1

Ubuntu 14.04 Support?
by William Jimenez 17 Jul '14

17 Jul '14

Hello I am curious if there are any plans at the present to support Ubuntu 14.04. Thanks, William

3 3

Device not yet discovered
by Kiru Pananthan 17 Jul '14

17 Jul '14

Dear all getting error message as below for few machines in observium, how this can be fixed This device has not yet been successfully discovered. System information and statistics will not be populated and graphs will not draw. This device should be automatically discovered within 10 minutes. Thanks Kiru -- *Confidentiality Disclaimer:* This e-mail and any attachments are confidential and intended solely for the intended addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the intended addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose, distribute or otherwise act in reliance upon any part of this e-mail or its attachments. Australian International School Malaysia and all affiliates under Taylor's Education Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party in reliance to this email, or from the transmission of any viruses. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Australian International School Malaysia and all affiliates under Taylor's Education Group. Replies to this e-mail may be monitored by Australian International School Malaysia and all affiliates under Taylor's Education Group for operational or business reasons.

4 3

alert checker email alert
by Gorbachev Anthony 16 Jul '14

16 Jul '14

Hi All, I am not receiving email alerts for the below checks also the alerted status says never and I can't find any documents online for the same. Can anyone please point me in the right direction ? -- Regards, Gorbachev Anthony

6 7

Discovery crashing UPS management card
by Steve Kersley 16 Jul '14

16 Jul '14

Good morning all, I'm a recent adopter of Observium so still finding my feet and slowly learning how best to set it up. However, I have noticed that since installing it, it was reporting that my main UPS management card was rebooting every 6 hours. The UPS is an Eaton 9SX 5000i + battery pack, with Network-MS management card, firmware HF which is the latest available for card tech level 16. Dabbling more, it seems that it's the discovery process that is causing it, specifically when it walks the xupsOutput table (.1.3.6.1.4.1.534.1.4) in the Powerware MIB, the UPS management card immediately stops responding and reboots. It actually appears to be crashing on doing a GetNext on .1.3.6.1.4.1.534.1.4.7.0, which is beyond the defined values in that table. The UPS continues to operate, but the management card stops. This also means that Observium has only managed to discover the 'input' voltage - output, bypass and current/power readings all just read as zero as the card has stopped responding when it tries to read those. The poll runs fine and gets data from the input voltage sensor. Clearly this is not an Observium issue: I can reproduce the reboot with a simple snmpwalk on the commandline, which should be a valid operation on a published MIB. I do have a ticket open with the manufacturer, although the first response was 'does it work with our management software?'. It may even be a fault on my unit, but I don't have more than one of these to test. I'm assuming there's a reason for the discovery module to need to walk the tables rather than just read the specific values - presumably bigger UPS units might have multiple metered AC inputs and outputs rather than just the one? I could disable sensor discovery, which will stop the reboots but that won't let it learn about the additional sensors that it still hasn't found. Unless I can manually insert data into the database for the poller to pick up? Alternatively, is there a way for me to override the detection of a Powerware UPS and use the generic UPS MIB rather than the XUPS MIB? Any other thoughts? Steve.

4 3

Ubuntu 12.04? Does r5229 work on Ubuntu 14.04?
by Rob Townley 15 Jul '14

15 Jul '14

Loving observium, but noticed some issues with it detecting well over 448 ports on a switch that nothing was plugged into except two patch cables but then i just happened to notice php version on Ubuntu 12.04. The Ubuntu installation directions had some conflicting information: Requires php5.4 but Ubuntu 12.04 does not includes php5.3 only. Recommend LTS, but recommend 13.04 which is not LTS. Does not mention 14.04 LTS. The existing community download is from April which provides another reason that Ubuntu 14.04 LTS will not work well since there has not been another release since then. So i am trying to decide to add a PPA for php5.4 or do i upgrade the entire OS to 14.04? Will the April 2014 (SVN# 5229 ) Observium release work just fine on 14.04.

2 2