-
Pandora FMS V3 RC2 Availability
Hi all,
trying to run with a new monitoring project and really would like to use Pandora, however I am having some issues which are preventing me moving forward.it seems that after adding items to a fresh install agents, checks etc (have tried with both the VirtualBox ISO and a fresh manual install on Centos 5.3 with same results) the backend DB seems to get confused, sometimes showing, all, none, or sometimes OLD DELETED objects on the web interface on each refresh of the webpage.
At this point I have noticed the ‘Sanitize Database’ tool also throws errors, where on a fresh install before the strange behaviour is noticed, the db sanity tool runs without error.
Sanatize DB output is as follows:
Checking tagente_estado table Inserting module 1 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (1, 0, '0000-00-00 00:00:00', 0, 100, 1, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48 Inserting module 2 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (2, 0, '0000-00-00 00:00:00', 0, 100, 1, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48 Inserting module 3 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (3, 0, '0000-00-00 00:00:00', 0, 100, 1, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48I am guessing these issues are related to the bugs found in RC1. The website said RC2 would be available about two weeks ago so does anyone know what is happening with this?
I would really like to use pandora but time is running out for the test implimentation and at some point I guess I’ll have to go back to OpenNMS 🙁
The other alternative is downgrading to the older stable versions, what features would I miss out on here?
Thanks,
//TrX -
5 Replies
-
RC2 is here… now!
(just in time!)
https://sourceforge.net/projects/pandora/files
I don’t have written the release notes, so you’re probably the first in know about the rc2.
This bug you talk about sanitize DB tool is not fixed becausa was not reported, I’ve added to our bug tracker, expect to have it fixed in a few days. Thx for reporting.
-
Hi Guys,
Now running RC2 (Fresh re-install) and still very much want to use pandora, however after configuring a couple of agents (Created some new modules, such as SMTP checks via TCP module), I start to notice some modules are no longer showing up within the agent view.
I try to re-add the module and it add’s OK, but then after a few more clicks around the web interface it is gone.Running a ‘Check DB Sanity’ gives me the same issue as my previous post in RC1:
Checking tagente_estado table Inserting module 10 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (10, 0, '0000-00-00 00:00:00', 0, 100, 5, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48 Inserting module 12 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (12, 0, '0000-00-00 00:00:00', 0, 100, 5, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48 Inserting module 13 in state table SQL error: Column count doesn't match value count at row 1 ('INSERT INTO tagente_estado (id_agente_modulo, datos, timestamp, estado, id_agente, last_try, utimestamp, current_interval, running_by, last_execution_try) VALUE (13, 0, '0000-00-00 00:00:00', 0, 100, 5, '0000-00-00 00:00:00', 0, 0, 0, 0)') in /var/www/php/godmode/db/db_sanity.php on line 48Has this been fixed? if so can you confirm the issue would make modules dissapear from agent’s and where can I get the new code from?
Thanks,
TrX -
I’ve review this problem in current code (RC3-dev, not officially tested, but you can checkout from our public SVN) and this works fine. Anyway this was one of the small bugs fixed in the RC’s.
Test the current code in SVN, its just this command:
svn co https://pandora.svn.sourceforge.net/svnroot/pandora/trunk/pandora_console
-
Touch wood I am not seeing any more issues with dissapearing hosts or DB sanity errors 🙂
Thank you, latest SVN seems to fix my issues.
Excellent product, One major requirement for me was the ease of management (mostly web gui based) as I will not always be the one managing our NMS system. Pandora FMS seems to fill this requirement very well!
I have now got round to playing with the windows agent and am so far impressed!
I have another question regarding tentacle use with the windows agent however I will ask this in another post.
Regards,
TrX -
We’re glad to produce a useful piece of software ! 😉
Don’t forget to add any bug or feature you may consider useful in our tracker in sourceforge:
https://sourceforge.net/tracker/?group_id=155200&atid=794852
Touch wood I am not seeing any more issues with dissapearing hosts or DB sanity errors 🙂
Thank you, latest SVN seems to fix my issues.
Excellent product, One major requirement for me was the ease of management (mostly web gui based) as I will not always be the one managing our NMS system. Pandora FMS seems to fill this requirement very well!
I have now got round to playing with the windows agent and am so far impressed!
I have another question regarding tentacle use with the windows agent however I will ask this in another post.
Regards,
TrX
