Zenoss System that started as 2.x Cannot upgrade to 3.2.1

[rphil001]

rphil001 [http://community.zenoss.org/people/rphil001] created the discussion

"Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63895#63895

--------------------------------------------------------------
We have a zenoss install that started out life as 2.5.2. We followed the upgrade path to 3.0.0, 3.0.1, 3.0.3, 3.1.0, but everytime we try to upgrade the 3.2.1 it breaks,

It runs stably on 3.1.0 but in order to restore onto 3.1.0 i had to rebuild a server by initially installing 2.5.2 then  following the same upgrade path to 3.1.0 and THEN doing the restore.

Is this normal and has anyone else has this issue. I thought this was fixed because we originally tried 3.2.0 but the catalog seemed to corrupt, so we though that had been fixed on 3.2.1 but alas we haave the same issue.

Symptoms are that alerting etc seems to work but the infastructure page and events page fail to load and eventually time out.

Any help would be greatly appreciated.

Ross
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63895#63895]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jshardlow]

jshardlow [http://community.zenoss.org/people/jshardlow] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63960#63960

--------------------------------------------------------------
I've just done something similar on a test box (CentOS 5.5 x86). It orignally started life running 1.x. The past few days I've gone from 2.5.2 to 3.2.1.

My path 2.5.2 -> 3.0 -> 3.0.3 -> 3.1 -> 3.2.1

It's been a bit painful, especially with the ZenPacks. It seems to be working OK, but I don't really have any confidence in the upgrade from 2.x to 3.x. So for the production boxes I'm going to get some more kit and start from scratch with 3.x.

Silly question, but are there any obvious errors in the logs? I'm far from an expert, but it does sound like there's something strange going on with your Zope DB. I'm not sure if a reindex (using zendmd) may be able to help?

Stop Zenoss, then as zenoss user:

$ zeoctl start
.
daemon process started, pid=22507
$ zendmd
Welcome to the Zenoss dmd command shell!
'dmd' is bound to the DataRoot. 'zhelp()' to get a list of commands.
Use TAB-TAB to see a list of zendmd related commands.
Tab completion also works for objects -- hit tab after an object name and '.'
(eg dmd. + tab-key).

dmd.Devices.reIndex()
commit()
quit()

$ zeoctl stop


Then start Zenoss back up.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63960#63960]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[rphil001]

rphil001 [http://community.zenoss.org/people/rphil001] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63974#63974

--------------------------------------------------------------
OK so i followed your advice and it came back with the following.

http://community.zenoss.org/mailto:***@EU974LINZENOS01:/usr/local/zenoss/zenoss/Products/ZenUtils$ ***@EU974LINZENOS01:/usr/local/zenoss/zenoss/Products/ZenUtils$ zendmd

Welcome to the Zenoss dmd command shell!
'dmd' is bound to the DataRoot. 'zhelp()' to get a list of commands.
Use TAB-TAB to see a list of zendmd related commands.
Tab completion also works for objects -- hit tab after an object name and '.'
(eg dmd. + tab-key).

dmd.Devices.reIndex

<bound method DeviceClass.reIndex of <DeviceClass at /zport/dmd/Devices>>

commit()
dmd.Devices.reIndex()

Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/usr/local/zenoss/zenoss/Products/ZenModel/DeviceClass.py", line 798, in reIndex
    notify(IndexingEvent(comp))
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.event-3.4.1-py2.6.egg/zope/event/__init__.py", line 23, in notify
    subscriber(event)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/event.py", line 26, in dispatch
    for ignored in zope.component.subscribers(event, None):
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/_api.py", line 138, in subscribers
    return sitemanager.subscribers(objects, interface)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/registry.py", line 323, in subscribers
    return self.adapters.subscribers(objects, provided)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.interface-3.5.2-py2.6-linux-i686.egg/zope/interface/adapter.py", line 579, in subscribers
    subscription(*objects)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/event.py", line 33, in objectEventNotify
    adapters = zope.component.subscribers((event.object, event), None)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/_api.py", line 138, in subscribers
    return sitemanager.subscribers(objects, interface)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.component-3.7.1-py2.6.egg/zope/component/registry.py", line 323, in subscribers
    return self.adapters.subscribers(objects, provided)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/zope.interface-3.5.2-py2.6-linux-i686.egg/zope/interface/adapter.py", line 579, in subscribers
    subscription(*objects)
  File "/usr/local/zenoss/zenoss/Products/Zuul/catalog/events.py", line 52, in onIndexingEvent
    update_metadata=event.update_metadata)
  File "/usr/local/zenoss/zenoss/Products/Zuul/catalog/global_catalog.py", line 322, in catalog_object
    ZCatalog.catalog_object(self, ob, uid, **kwargs)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-i686.egg/Products/ZCatalog/ZCatalog.py", line 529, in catalog_object
    update_metadata=update_metadata)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-i686.egg/Products/ZCatalog/Catalog.py", line 339, in catalogObject
    index = self.updateMetadata(object, uid)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-i686.egg/Products/ZCatalog/Catalog.py", line 278, in updateMetadata
    newDataRecord = self.recordify(object)
  File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-i686.egg/Products/ZCatalog/Catalog.py", line 417, in recordify
    if(attr is not MV and safe_callable(attr)): attr=attr()
  File "/usr/local/zenoss/zenoss/Products/Zuul/catalog/global_catalog.py", line 224, in searchExcerpt
    o.name(), o.getParentDeviceName())
TypeError: 'str' object is not callable


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

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63974#63974]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jcurry]

jcurry [http://community.zenoss.org/people/jcurry] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63984#63984

--------------------------------------------------------------
I have just done 2 systems from 2.5.2 -> 3.0.3 -> 3.1 upgrades.  Not gone on to 3.2.1.  No problems other than care around ZenPacks.

Silly question perhaps.  You did install the PreUpgrade ZenPack  before going from 2.5.2 to 3.0.3 and make sure that zencatalog REALLY ran to completion (check zencatalog.logs) in the log directory???  I find the easiest way to be sure that zencatalog has really run to completion is to run it again and you get a fairly instant append to the log effectively saying the catalog is done, nothing to do.

Cheers,
Jane
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63984#63984]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jshardlow]

jshardlow [http://community.zenoss.org/people/jshardlow] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63986#63986

--------------------------------------------------------------
Good point. I got caught out on that (2.5.2 -> 3.0.3). The docs aren't too forthcoming, but when it's finished the zencatalog.log should say something like:

2012-01-25 15:45:43,165 INFO zen.catalog: Completed 12488 out of an estimated 12488, 100.0 percent done
2012-01-25 15:45:43,982 INFO zen.catalog: Committed a batch of 88 objects
2012-01-25 15:45:43,982 INFO zen.catalog: Finished cataloguing all objects
2012-01-25 15:45:44,042 INFO zen.ZenCatalog: Deleting PID file /opt/zenoss/var/zencatalog-localhost.pid ...
2012-01-25 15:45:44,042 INFO zen.ZenCatalog: Daemon ZenCatalog shutting down


If run again (once already complete) as Jane suggests, it should say:

2012-01-25 15:48:56,907 INFO zen.catalog: zencatalog already ran. Nothing to index
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63986#63986]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[rphil001]

rphil001 [http://community.zenoss.org/people/rphil001] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/64001#64001

--------------------------------------------------------------
Thanks for the reply. Yes we ran the pre upgrade patch and everything went fine. We ran on 3.0.3 for about 8 months before upgrading to 3.1.0. Even that's worked fine its only the upgrade to 3.2.1 that broke everything.

Originally it was the failed to connect to server error when on the events or infrastructure page. Since then I manually ran the last step in zenmigrate and can get to the infrastructure page but half the kits missing and I keep getting the error in the previous post when I try to reindex or recatalog everything.

I just don't know how to find out what's causing the error because there doesn't seem to be a verbose output when re indexing.

Ross

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

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/64001#64001]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[rphil001]

rphil001 [http://community.zenoss.org/people/rphil001] created the discussion

"Re: Zenoss System that started as 2.x Cannot upgrade to 3.2.1"

To view the discussion, visit: http://community.zenoss.org/message/63989#63989

--------------------------------------------------------------
OK so brief update on this, I got this working after alot of work. I cant remember what i did totally but if anyone gets this issue do the following.

Stop Zenoss
zeoctl start

then run zenmigrate manually step by step from 3.1.0 onwards

3.1.0    RegisterRootDevtype Register root devtype, to support propertyItems access at
                      all device type levels.
3.1.1    IpSearchCatalogUpdate This migration script adds indexes for fields displayed
                      in the device list.
3.1.1    RebuildPathIndex Not Documented
3.1.1    ToManyPersistentList Changes all of the ToManyRelationships to be persistent
                      lists instead of regular python lists. This results in
                      performance improvements when accessing the objects
3.1.1    eventfacadeUsingCatalog Not Documented
3.1.1    DeviceSearchCatalogUpdate This migration script adds indexes for fields displayed
                      in the device list.
3.1.70   snmpv3trap      Add zProperties for SNMPv3

So it would be

zenmigrate --step=RegisterRootDevtype

zenmigrate --step=IpSearchCatalogUpdate

etc....

Then run zendmd
dmd.Devices.reIndex()
commit()

then restart zenoss. All the devices are not totally there but deleteing them and readding them seems to work.

Anyway this worked for me i think, i would test it but i dont want it broken again. :)
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63989#63989]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]