[2.5.2] - Apache and Mysql Zenpack don't work anymore

[blioncorp]

Hello,
 
I just upgraded my Zenoss installation to 2.5.2.
I use Linux monitor, Apache, and Mysql zenpacks (and some other less important)
 
Since the update, Mysql and Apache packages do not work anymore.
In event view, I have the following error:
Cmd:  /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ApacheMonitor-2.1.0-py2.4.egg/ZenPacks/zenoss/ApacheMonitor/libexec/check_apache.py  -H xxx.xxx.xxx.xxx -p 80 -u '/server-status?auto' - Code: 1 - Msg:  General error
 
If I manually run the same command as user zenoss, it works fine.
In zenaction.log, I had plenty of:
 
2010-03-04 00:17:03,578 ERROR zen.ZenActions: unexpected exception
Traceback (most recent call last):
  File "/usr/local/zenoss/zenoss/Products/ZenEvents/zenactions.py", line 583, in runCycle
    self.mainbody()
  File "/usr/local/zenoss/zenoss/Products/ZenEvents/zenactions.py", line 574, in mainbody
    self.maintenance(zem)
  File "/usr/local/zenoss/zenoss/Products/ZenEvents/zenactions.py", line 383, in maintenance
    self.execute(sql)
  File "/usr/local/zenoss/zenoss/Products/ZenEvents/zenactions.py", line 188, in execute
    return self._getCursor(stmt, callback)
  File "/usr/local/zenoss/zenoss/Products/ZenEvents/zenactions.py", line 174, in _getCursor
    rowsAffected = curs.execute(stmt)
  File "/usr/local/zenoss/python/lib/python2.4/site-packages/MySQLdb/cursors.py", line 137, in execute
    self.errorhandler(self, exc, value)
  File "/usr/local/zenoss/python/lib/python2.4/site-packages/MySQLdb/connections.py", line 33, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (1305, 'PROCEDURE zenoss.age_events does not exist')
 
The procedure was really missing.
I fixed this error by running : mysql -b zenoss < zenprocs.sql
Now, this log seems to be clean.
 
In zencommand.log, I have no errors.
 
What could cause this general error ?

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46250#46250





--end--

[guyverix]

I currently am able to duplicate this with the Apache ZenPack.  I am getting ready to re-install this one.  I have not found any problems with the mysql ZenPack against both MySQL 4 as well as MySQL 5 servers.
 
Have you had a chance to reinstall the ZenPack and see if that sorts out the problem?

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46271#46271





--end--

[guyverix]

Okay..  I fixed mine..
 
I re-installed the Apache ZenPack and restarted zenhub/zope
This initially did not change anything.
Then I changed zenhub and zencommand logging to verbose and restarted the daemons.
This got it from the ZenPack perspective.  However I started getting database conflict errors at this point.
At this point I went into zendmd and did a reindexd () and commit ().
 
Restarted and everything appears to be stable right now.
Hopefully you will not have to reindex, but try the steps I did to recover your ZenPack functions...

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46272#46272





--end--

[T_R_J]

How does one go into zendmd and do a reindex and commit?
 
 
Thanks,

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46318#46318





--end--

[blioncorp]

Hello,
 
I performed a reindex and commit.
I restarted Zenoss-stack completely.
Two times. It didn't solve my issue.
 
How to set up verbosity in configuration files ?
 
BR...

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46319#46319





--end--

[guyverix]

Post by blioncorp
 
Hello,
 
I dropped the entire Mysql database. I recreated it using files in
/usr/local/zenoss/zenoss/Products/ZenEvents/db
I ran /etc/cron.weekly/zenoss (after fixing python path in it) as root
and zenoss.
I deleted all logs to have something clean. They do not report any error.
How to clean the zope cache ?
Where can I find something about this "General error" ?
 
BR.
Jerome Blion.

http://IP ADDRESS:8080/ manage
Use your admin credentials.  You can pack the zope database, and clear zope caches inside here. 
 
I dont quite grok the details of the error from what you posted, but it looks like the information in zope and what is defined for an RRD graph / check are out of whack..
 
/zport/RenderServer/render:  <---  This is why I am suspecting it is something with RRD.
 
This would not have anything at all to do with your events database (mysql) this looks like it is entirely zope related.
 
Is there a chance that someone might have moved a populated device class, or something like that?

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46389#46389





--end--

[blioncorp]

Hello,
 
I dropped the entire Mysql database. I recreated it using files in
/usr/local/zenoss/zenoss/Products/ZenEvents/db
I ran /etc/cron.weekly/zenoss (after fixing python path in it) as root
and zenoss.
I deleted all logs to have something clean. They do not report any error.
How to clean the zope cache ?
Where can I find something about this "General error" ?
 
BR.
Jerome Blion.

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46386#46386





--end--

[blioncorp]

Hello,
 
The only thing I did is to upgrade from 2.5.1 to 2.5.2.
I packed the database several times. with no changes.
I want to /manage URI to clear zope caches. That didn't change anything.
 
I still have same errors, and my zenoss is now totally useless !
 
Best regards.
Jerome Blion.
 
 
Le 07/03/2010 12:00, guyverix a écrit :

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46393#46393





--end--

[blioncorp]

Hello,
 
I removed zenoss-stack package. I deleted /usr/local/zenoss and
/opt/bitrock. So, everything has been deleted.
I reinstalled it and reinstalled following zenpacks : LinuxMonitor,
LinuxMonitorAddon, Apache, Mysql.
As I don't have many devices, I added them manually. Successfully.
 
I bound one device to Apache Template :
 
Cmd:
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ApacheMonitor-2.1.0-py2.4.egg/ZenPacks/zenoss/ApacheMonitor/libexec/check_apache.py
-H 192.168.1.2 -p 80 -u '/server-status?auto' - Code: 1 - Msg: General error
 
(as zenoss) serveur:~$
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ApacheMonitor-2.1.0-py2.4.egg/ZenPacks/zenoss/ApacheMonitor/libexec/check_apache.py
-H 192.168.1.2 -p 80 -u '/server-status?auto'
STATUS OK|slotDNSLookup=0 slotOpen=59 totalAccesses=111056
slotReadingRequest=0 totalKBytes=4018477 busyServers=1 slotKeepAlive=0
slotGracefullyFinishing=0 bytesPerReq=37052.7 cpuLoad=.00473853
bytesPerSec=3939.13 slotLogging=0 slotSendingReply=1 slotStartingUp=0
reqPerSec=.106312 slotWaiting=4 idleServers=4
 
(This server is not loaded at all)
 
I bound the same device to Mysql template :
 
Cmd:
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-2.1.1-py2.4.egg/ZenPacks/zenoss/MySqlMonitor/libexec/check_mysql_stats.py
-H 192.168.1.2 -p 3306 -u jerome -w '' -g
STATUS OK|Aborted_clients=58 Aborted_connects=54 Binlog_cache_disk_use=0
Binlog_cache_use=0 Bytes_received=160581655 Bytes_sent=1494231798
Com_admin_commands=274929 ...
 
I bound another device to the same template and only this one. Same
error raises in Event log.
 
How could I confirm the problem comes from zenoss either from zenpacks ?
The "General error" message is totally useless ! It does not provide any
information at all...
The 2.5.2 update totally destroyed my monitoring solution.
 
Best regards.
Jerome Blion.

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46394#46394





--end--

[Matt Ray]

Which stack installer did you use, the .bin or the .deb?

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46399#46399





--end--

[blioncorp]

Hello,
 
I installed it with apt-get from repositories.
As it seems there is a bug somewhere, I opened a new ticket : http://dev.zenoss.com/trac/ticket/6260
 
Jerome Blion.

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46372#46372





--end--

[Matt Ray]

We've refreshed the .deb installer with an updated package to address   path issues that were uncovered after the 2.5.2 release.  The Zenoss   version number remains 2.5.2, but the .deb archive has an updated   package number of 2.5.2-1.  We've tested upgrading with it and marked  this as the  fix for
http://dev.zenoss.com/trac/ticket/6250
http://dev.zenoss.com/trac/ticket/6260
 
If   you're using the .deb installer with Debian or Ubuntu and using the   Zenoss apt repository, you should be able to upgrade directly.  Direct downloads of the .deb and future installs will use this version and should upgrade cleanly.  We   apologize for any inconvenience, thanks for helping us fix this.
 
Thanks,
Matt   Ray
Zenoss Community Manager

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46661#46661





--end--

[blioncorp]

Hello,
 
As described in the bug, the update fixed the problem.
 
Thank you.

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/46697#46697





--end--