-
After migration 1.3.1 to 2.0, problems DB.pm/network modules – SOLVED
Hi Everybody.
I migrate from 1.3.1 to 2.0 and everything seems to be ok. After changed all my agents to point to the new 2.0 Pandora FMS Server, I realized problems with the network modules and the follow strange message in the pandora_server error logs:
“Use of uninitialized value in numeric lt (<) at /usr/lib/perl5/site_perl/5.8.8/PandoraFMS/DB.pm line 2255." The pratical result is no data from the defaults network modules (attached an example). During the migration I had to manualy enter 2 commands to make the migration works. The upgrade.php complained abount no collum named "disabled" at tagent_modulo table. I looked at the creation script and entered the alter table command below: ALTER TABLE tagente_modulo ADD disabled tinyint(1) unsigned default '0'; The command below was necessary too, and I found it in the docs. about migration to new 2.0 version: INSERT INTO `ttipo_modulo` VALUES (100,'keep_alive',-1,'KeepAlive','mod_keepalive.png'); Any tip about the problem or how to debug it? obs: I migrated from the vmware Ubuntu server 1.3 beta 2 to my CentOS production server. obs2: sorry about the big post... -
9 Replies
-
-
Yes. I restarted it and restarted the pandora server itself. The network server is running (pid: 8650). By the way, the message “Use of uninitialized value in numeric lt (<) at /usr/lib/perl5/site_perl/5.8.8/PandoraFMS/DB.pm line 2255." appeared a lot of times in the error log…
-
Seems that the problem rises when the network modules are processed inside the function “sub export_module_data” (DB.pm). I suppose that the SQL query is not working when processing this modules. I’m having a hard time trying to debug this sub-function..
Any tip about what could be wrong in the database upgrade process that booked this specific function? Any thing that point me to the right direction will be appreciated… I don’t wanna to throw away all the data that I have until now because of this problem only in the network modules….
-
-
-
Hi rnovoa,
Thank you. After the download of the new version from SVN, the message in the log error was vanished 😉
Unfortunately, my problems with the database and/or network modules still remains… I have no idea why this is happenning… Any tips about what could be wrong will be appreciated.
If I’m no be able to solve this problem, I will start from scratch with version 2.0 and keep an old version to query the old data… 🙁
-
Hi everybody,
After I cleared my head about the doubts in the process of upgrade the database I could see what seems to be the problem. Reading again all post, I follow the tip gave by Manu (at the first post) about the Network Server. Digging it, i discovered a dependecy error (that i missed during the upgrade process) in the perl-Net-Ping module… Seems like this is the source of the problem.
I will try to solve this and post here the results. Thanks a lot for your time and help.
-
No dependency problems… The Net::Ping module is working… But a new message in the pandora_server.error should point-me to the right direction:
DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/bin/pandora_network line 549.
The message appears lots of times…
-
At last, problem solved!
For some unknown reason, the Network-Server configured in the agents were not working. I just have to enter in each agent configuration module and hit “Update” to make the Network-Server start working.
I suspect from the fact that the hostname of the pandora server was missing a middle part of the domainname. I corrected that yesterday, but the changed only reflected after the update in the agents that I did today.
Thank you all for the help.
