Hey, Richard.

Thanks for the feedback.  Can you provide a bit more data?

With which artifact did you try upgrading / installing?

     zenoss-stack_2.5.2_x64.deb

     zenoss-stack_2.5.2_i386.deb

Did you go through the deb repo or did you download the artifact directly and do a dpkg -i?

Please spell this out a bit more in gory detail so it is easier to repro.  Is there anything unique about your setup that would be helpful to know (i.e., in terms of install paths or overridden zope/zeo ports)?

What errors, if any, did you see while installing the core product (as opposed to what you saw while trying to install zenpacks).

Is there any interesting recent content in /tmp/bitrock_installer.log?

Can you post the exact steps you took to install the zenpacks?

Which zenpack were you trying to install, btw?

On a typical (healthy system), the zenpack executable is found here:

-rwxr-xr-x 1 zenoss zenoss 918 2010-03-03 10:22 /usr/local/zenoss/zenoss/bin/zenpack

Is this missing on your system or do you see, perhaps, a path issue when you become the zenoss user?

Please post your path...

su - zenoss

echo $PATH

Anyone else in the community having similar grief?

QA generally shakes out the *.deb artifacts on Ubuntu and does test installs off the repo once the bits have been blessed internally.

Thanks,

Glenn

p.s.

Zenoss QA is sponsoring a community test day on Thursday.  You might want to join in on that.  They actually had a test day a few weeks ago with a recent 2.5.2 candidate build.  Your input upstream of any release in any of these or similar events is much appreciated.

All - QA is trying to reproduce with the .deb installation against Ubuntu (that is the method we use for testing the .deb installers internally).  What ZenPacks were you trying to install?  Were they community zenpacks, or zenoss core zenpacks?  Links would be helpful, if they are community zenpacks.

"When you install zenpacks with the shell, they show as broken." - Gabriel

I'd just like to point out that quite a few ZenPacks will show as broken after being installed.  This generally means that you need to restart Zenoss.  This is completely normal behaviour (nothing new).

Based on what I've read here, this issue appears to be very specifically related to installing ZenPacks via the UI.

I'll be conducting a few tests tomorrow to see if I can duplicate this issue.

Hello, ticket http://dev.zenoss.com/trac/ticket/6250 (Cannot Install a Zenpack via UI on .deb installer) was opened to track this issue.

There is a workaround for this. Try to install the zenpack manually by using a ssh client

1. Log in on your system using the ssh client.
2. Change to the zenoss user by doing
   su - zenoss
3. Move to another where you can download the zenpack without problems like /tmp
   
   cd /tmp
   
4. use the wget command in order to download the zenpack
   wget [URL of the zenpack]
5. then use the zenpack command
   zenpack --install [.egg file or .zip file]

That will install the zenpack, now use browser and navigate on your server and look for the Zenpack page at Settings->Zenpack, if you see that the zenpack is reported as broken or missing then you need to restart zenoss. open a new ssh client on your system and as the root user execute:

/etc/init.d/zenoss-stack stop

/etc/init.d/zenoss-stack start

That will do the trick

Gabriel - is it any zenpack that fails to install, or the WMI one, via SSH?  Could you please try and install the core zenoss zenpacks and see how those fair?  Is it possible that what you are seeing from the command line is tied to a particular issue with that zenpack and not all zenpacks?

experiencing the same issue w/ ubuntu server, tried deleting/re-installing zenpack from command line, re-installing zenoss-stack, set sym link from message/46362, none of it works, 2.5.2 completely destroys wmi monitoring on ubuntu... is there anyway to downgrade

back to 2.5.1?

-m

What do you mean "affecting all artifacts"? Is it affecting other zenoss processes/daemons as well?

-m