Archived community.zenoss.org | full text search
Skip navigation
1 2 3 4 Previous Next 15409 Views 47 Replies Latest reply: Mar 6, 2012 12:24 PM by Shane Scott RSS
Insane_Homer Rank: White Belt 54 posts since
Nov 21, 2008
Currently Being Moderated

Sep 7, 2011 5:34 AM

Post 3.2 Upgrade issues

Hi,

 

I've done an Upgrade from Source .tar on my Zenoss Ubuntu installation (from 3.1)

 

 

daemon process started, pid=13970
Loading initial Zenoss objects into the Zeo database
(this can take a few minutes)
zport portal object exits; exiting.
Data migration failed
zenoss@UBZEN01:~/zenoss-3.2.0$ zenmigrate
INFO:zen.migrate:Database going to version Zenoss 3.1.70
INFO:zen.migrate:Installing DeviceSearchCatalogUpdate (3.1.1)
WARNING:zen.migrate:Recovering
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py", line 21, in <module>
    main()
  File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py", line 18, in main
    m.main()
  File "/usr/local/zenoss/Products/ZenModel/migrate/Migrate.py", line 417, in main
    self.cutover()
  File "/usr/local/zenoss/Products/ZenModel/migrate/Migrate.py", line 304, in cutover
    self.migrate()
  File "/usr/local/zenoss/Products/ZenModel/migrate/Migrate.py", line 280, in migrate
    m.cutover(self.dmd)
  File "/usr/local/zenoss/Products/ZenModel/migrate/deviceSearchCatalogUpdate.py", line 76, in cutover
    brain.getObject().index_object()
  File "/usr/local/zenoss/Products/ZenModel/Device.py", line 1967, in index_object
    super(Device, self).index_object(idxs)
TypeError: new_index_object() takes exactly 1 argument (2 given)
zenoss@UBZEN01:~/zenoss-3.2.0$

 

thereafter I'm able to login and see the landing page, However I cannot access either the EVENTS or INFRASTRUCTURE PAGES

 

and end up with the following...

 

zenosserror3.JPG

 

Now I've followed the upgrade instructions in the Installation document but it seems to be a outdated. (Page 36 Upgrading a Source tarball Installation).

 

Daemons showing as Follows

 

daemons.JPG

 

any idea how I get this fixed?

Attachments:
  • artifact Rank: Green Belt 303 posts since
    Mar 11, 2008
    Currently Being Moderated
    2. Sep 7, 2011 2:29 PM (in response to Insane_Homer)
    Re: Post 3.2 Upgrade issues

    Hey,

     

    I opened a ticket for this: http://dev.zenoss.com/trac/ticket/7862

     

    I was able to restore *some* functionality by clearing the DeviceSearch, Ipsearch, and componentsearch catalogs, re-running zenmigrate, and rebuilding the catalogs. Some stuff is still broken like modeling and adding new devices, and changing devices... anything that requires a change to the index.

  • ones_and_zeros Rank: White Belt 12 posts since
    Mar 31, 2010
    Currently Being Moderated
    3. Sep 7, 2011 9:13 PM (in response to artifact)
    Re: Post 3.2 Upgrade issues

    artifact - did you do an upgrade from pre-3.x? the only time i've ever seen the specific reason for failure that you posted in that trac ticket is if the PreUpgrade zenpack is still installed. that is supposed to automatically be removed immediately post-upgrade to 3.x, however if something broke along the way that can get left behind and will result in this message. check your list of zenpacks and see if the Zenoss.ZenPacks.PreUpgrade zenpack is still there. if it is, you can get past this ... but will also need a copy of the $ZENHOME/log/install.log to determine what failed in the first place to cause that zenpack to be left behind.

  • ones_and_zeros Rank: White Belt 12 posts since
    Mar 31, 2010
    Currently Being Moderated
    5. Sep 8, 2011 8:46 AM (in response to Insane_Homer)
    Re: Post 3.2 Upgrade issues

    Insane_Homer - if that zenpack was left behind, then you'll have a traceback in your $ZENHOME/log/install.log from when you were doing the upgrade, and this will point to what caused the problem initially and give a clue as to what state the installation is currently in. there's also a chance that whatever the original issue was has cleared up and simply removing the PreUpgrade zenpack is all you needed to do.

  • VBinet Rank: White Belt 5 posts since
    Oct 22, 2010
    Currently Being Moderated
    6. Sep 8, 2011 11:28 AM (in response to ones_and_zeros)
    Re: Post 3.2 Upgrade issues

    I have the same problem and the PreUpgrade Zenpack is not present.

     

    Zenoss was updaded automatically  and stopped working. All the processes were stopped and restarting them didn't help getting the webinterface back on. zeoctl failed to restart.

    After rebooting the server, we saw update processes running and the webinterface was up again but we are getting the messages described here.

     

    Message was edited by: VBinet Install.log added.

    Attachments:
  • blackice8r Newbie 5 posts since
    Sep 5, 2011
    Currently Being Moderated
    7. Sep 8, 2011 11:01 AM (in response to Insane_Homer)
    Re: Post 3.2 Upgrade issues

    exact same thing here, same behaviour after the upgrade

     

    upgraded from 3.1

    apt-get update

    apt-get upgrade zenoss-stack

     

    Any suggestions?

  • artifact Rank: Green Belt 303 posts since
    Mar 11, 2008
    Currently Being Moderated
    8. Sep 8, 2011 2:02 PM (in response to Insane_Homer)
    Re: Post 3.2 Upgrade issues

    For me, the PreUpgrade zenpack was not listed in the Zenoss gui or in Zope, but there were two ZenPack directories in $ZENHOME/ZenPacks for some reason:

     

    $ZENHOME/ZenPacks/ZenPacks.zenoss.PreUpgrade30-1.1.egg

    $ZENHOME/ZenPacks/ZenPacks.zenoss.PreUpgrade30-1.1-py2.4.egg

     

    I moved the latter directory to /tmp, restarted Zenoss, and now everything is working perfectly.

     

    Thank you very much ones_and_zeros for pointing me in the right direction.

  • ones_and_zeros Rank: White Belt 12 posts since
    Mar 31, 2010
    Currently Being Moderated
    9. Sep 8, 2011 8:11 PM (in response to VBinet)
    Re: Post 3.2 Upgrade issues

    VBinet - you've got a relationship problem in the object database that got in the way of a catalog update. you'll want to run the 'zenfixit' utility, and when it's complete just run 'zenmigrate' at the zenoss server command line, as the zenoss user. that should get it to pick up with the migration where it failed out. i'd actually recommend stopping all of the zenoss daemons before doing this, and then only starting zeoctl so that there's nothing else accessing the object database while you're doing this. once the migration steps complete, as they hopefully will, then start up all of the zenoss services and you should be set.

  • VBinet Rank: White Belt 5 posts since
    Oct 22, 2010
    Currently Being Moderated
    13. Sep 9, 2011 10:50 AM (in response to ones_and_zeros)
    Re: Post 3.2 Upgrade issues

    I couldn't find zenfixit so I downloaded it form

    servlet/JiveServlet/download/47157-2585/zenfixit.py.txt.zip

     

    Followed the instructions and tried the WUI again. I got a message telling me to run mysqladmin flush-hosts and after doing it, I can see the events and the infrastructure.

     

    Problem solved in my case. Thank you.

  • blackice8r Newbie 5 posts since
    Sep 5, 2011
    Currently Being Moderated
    14. Sep 12, 2011 9:56 AM (in response to VBinet)
    Re: Post 3.2 Upgrade issues

    I managed to download zenfixit.py.txt.zip , it's in /root   now

    I managed to un-zip and if I recall correct rename it, it and I have zenfixit.py now

     

    Am i doing it right?

     

    I'm a linux noob, do you mind telling me what I need to do, what commands I need to fire at the terminal to run this tool?

     

    I got Webmin installed and SSH.  How to I run this tool?

     

    My problem is exactly as yours and I really hope this tool will fix it...

1 2 3 4 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points