Nagios Support Forum

Just for clarification, it was us that were asking about InnoDB vs MyISAM. But the order was reversed. http://support.nagios.com/forum/viewtopic.php?f=16&t=6180&p=27965&hilit=innoDB#p27965 We had found during an issue with the upgrade that the DB was not updated. When digging to find wha...

We are curious on if we could benefit from using fusion as are main login, and can see the obvious benefits of the user management and 10,000 foot view. We would like to have as much functionality in this server to reduce as much load as possible from users directly interacting with our XI servers. ...

We have a need in the BPI plugin, that by default nothing should be hidden. We keep a relatively clean list of the applications in the plugin, so the main page does not get to cluttered in the first place, and users can drill down from there to see things they would like to see. The BPI Beta, DOES a...

I can verify lmiltchev's fears in this area. At one point, we removed ' as well as <> from the character restrictions, and had the unfortunate pleasure of seeing things break when a check would have unmatched single quotes, and other oddities. Checks would come back with output only partially filled...

Mr Guthrie, Thank you for the head start, it gave us what to look for. So this is due to the table optimization in mysql. It's stalling out when deleting from nagios_logentries (910K rows) & nagios_statehistory (446K rows). This is because its copying the whole table to tmp space, deleting the r...

Alas... no change... Ran the DB upgrade (had to make some minor tweaks due to primary keys cols(varchar) being changed to text cols (which doesn't work in MySQL)) but nothing major. The count on the frozen checks continues to rise until we trigger the script to force a check. I would LOVE to do a re...

I can verify that the last_check and next_check times are the same in core and XI.

Ill update the DB and see what that does.

ok... I think i have it... Please let me know if this is right. the SQL files are inclusive of each other going backwards, thus, b3 -> current would have everything that b4 -> current would as well. So doing a diff of an sql with the previous version will tell me what was added to the older version....

This is where I'm stuck... that won't do anything. The script were calling will simply insert 1.5.1 into the DB table and exit. I'm doing diffs of the different sql files going backwards to see which one we seem to have all of the changes in... but this is long and arduous... I would LOVE to know if...

I can also verify that DB is missing changes that would have been in 1.4b6 & 1.4b5.

So we obviously have discrepancies...