-
Problems after updating from 1.2 to 1.3 -Modules not showing
Hello,
As I told in my previous post, I’ve just upgraded from v1.2 to v.1.3.
Almost everything keeps working ok. But when I add a new agent, the modules don’t show.
I create the the agent and leave it in “learning mode” and after a while, the new module count appears in the general view, but if I go into the agent’s details the new modules aren’t shown in the view mode!! Strangely, in “edit mode” all modules are shown.
And if I use the old console v1.2 (It’s still installed in the same server), all modules are shown correctly.
Any hints of what could be happening?
thanks,
VÃctor. -
6 Replies
-
Looks like there is something bad in the migration SQL that you have used.
Where did you downloaded it? There was any error when executing the script? Did you get any error in the PHP code? By default, PHP error reporting is disabled in the config.php file, try to change error_reporting(0) to error_reporting(E_ERROR) in that file and access those pages again.
Let see if we find what’s happening.
Regards,
Raul
-
I downloaded Pandora FMS 1.3 Console from SourceForge, and ran the script “upgrade.php”. The script stopped in step 4 with the following error:
[code:1]
Schema manipulation (FAILS)
Populating new schema and converting data (FAILS)
Created new config file at ‘include/config.php’ (FAILS)There was some problems. Installation is not completed.
Please correct failures, and restore original DB before trying again.
ERROR: Duplicate entry ‘3’ for key 1.I found a thread about the same error viewtopic.php?p=2285&sid=03ad400c16fa804d11409ee55a04cdc2 (can’t post URLs yet)
So I executed the SQL script line by line and found that the error seemed to happen because some tables already existed. So i added a line “DROP TABLE X” before each “CREATE TABLE X”, and the script seemed to finish OK.
I’m using the prepacked VMWare with Debian 3.1 R4 and Pandora FMS 1.2
Did I screw up my database?? 😥
-
I’m replying to your last post in 981.
So, you say you can only see your modules in the edition menu, therefore you can’t see any data of those modules in the view menu of the agent.
What do you get if you run:
select * from tagente_datos where id_agente_modulo = 1 and id_agente = 1;
You might want to change the module and the agente value to fit your own setup.
Seems you do screw up your database.
-
This is the output for a newly created agent (id_agente=45):
[code:1]
mysql> select * from tagente_datos where id_agente=45 order by timestamp desc limit 20;
+—————–+——————+————+———————+———–+————+
| id_agente_datos | id_agente_modulo | datos | timestamp | id_agente | utimestamp |
+—————–+——————+————+———————+———–+————+
| 3130213 | 474 | 50.00 | 2008-03-28 13:07:44 | 45 | 0 |
| 3130214 | 475 | 52884.00 | 2008-03-28 13:07:44 | 45 | 0 |
| 3130215 | 476 | 1353200.00 | 2008-03-28 13:07:44 | 45 | 0 |
| 3130128 | 473 | 0.00 | 2008-03-28 13:02:39 | 45 | 0 |
| 3130129 | 474 | 22.00 | 2008-03-28 13:02:39 | 45 | 0 |
| 3130130 | 475 | 54244.00 | 2008-03-28 13:02:39 | 45 | 0 |
| 3130131 | 476 | 1352800.00 | 2008-03-28 13:02:39 | 45 | 0 |
| 3130041 | 473 | 1.00 | 2008-03-28 12:57:35 | 45 | 0 |
| 3130042 | 474 | 1.00 | 2008-03-28 12:57:35 | 45 | 0 |
| 3130043 | 475 | 54616.00 | 2008-03-28 12:57:35 | 45 | 0 |
| 3130044 | 476 | 1352464.00 | 2008-03-28 12:57:35 | 45 | 0 |
| 3129958 | 474 | 0.00 | 2008-03-28 12:52:31 | 45 | 0 |
| 3129959 | 475 | 51860.00 | 2008-03-28 12:52:31 | 45 | 0 |
| 3129960 | 476 | 1354948.00 | 2008-03-28 12:52:31 | 45 | 0 |
| 3129871 | 474 | 6.00 | 2008-03-28 12:47:27 | 45 | 0 |
| 3129872 | 475 | 52104.00 | 2008-03-28 12:47:27 | 45 | 0 |
| 3129873 | 476 | 1354624.00 | 2008-03-28 12:47:27 | 45 | 0 |
| 3129779 | 474 | 13.00 | 2008-03-28 12:42:23 | 45 | 0 |
| 3129780 | 475 | 51852.00 | 2008-03-28 12:42:23 | 45 | 0 |
| 3129781 | 476 | 1354464.00 | 2008-03-28 12:42:23 | 45 | 0 |
+—————–+——————+————+———————+———–+————+
20 rows in set (0.02 sec)The timestamps are ok (data is being received)
Please tell me it’s de-screwable 🙄
-
-
