Yes, install.sh tries to be careful on the update. Assuming we didn't break things in the last few weeks, that's the way to go.

Here's what we do internally:

   # shutdown
   $ zenoss stop
   # livin' on the edge:
   $ svn update $ZENHOME/bin $ZENHOME/Products ./zenossinst
   # prep the database for migration
   $ zeoctl start
   # test
   $ zenmigrate run
   # really do it: no turning back
   $ zenmigrate run --commit
   # get any updated/new configuration files
   $ cd zenossinst
   $ make config-install ZOPEPASSWORD=yourpassword

-Eric

Kent Tenney wrote:
On 7/18/06, Eric Newton <[EMAIL PROTECTED]> wrote:
It's in there.  Here's the patch:

http://dev.zenoss.org/trac/changeset/1910

Right, I didn't notice the additional param to load1()

What is the correct way to update zenoss?

It seems that running ../zenossinst/install.sh will do it.
Is that correct?

Thanks,
Kent



I didn't set the path, since that's _supposed_ to be set by the zenmib
wrapper.

-Eric

Kent Tenney wrote:
> On 7/18/06, Eric Newton <[EMAIL PROTECTED]> wrote:
>> Right... I had the same issue and I commited the fix to SVN.
>
> Is this the correct URL for the file?
> http://dev.zenoss.org/svn/trunk/Products/ZenModel/zenmib.py
> I don't see the fix, is there a delay?
>
>> $ZENHOME/bin should be put in your path by the zenmib script.
>
> I don't see that in the zenmib script, however after removing
> SUDO=sudo
> the script works fine.
>
> Thanks,
> Kent
>
>>
>> -Eric
>>
>> Kent Tenney wrote:
>> > I've been trying to register mibs.
>> > I worked around my unresolved path problem by
>> > qualifying smidump's name in zenmib.py;
>> >
>> > exec os.popen('smidump -fpython %s 2>/dev/null' % mibname) in result
>> > to
>> > exec os.popen('/usr/local/zenoss/bin/smidump -fpython %s 2>/dev/null'
>> > % mibname) in result
>> >
>> > I then came accross a name error.
>> > the method load() defines mibs;
>> >        mibs = self.dmd.Mibs
>> >
>> > and the method load1() refers to mibs;
>> >            mod = mibs.createMibModule(modname, self.options.path)
>> >
>> > but it is not in the scope of load1()
>> > I replaced the line in load1() with
>> > mod = self.dmd.Mibs.createMibModule(modname, self.options.path)
>> >
>> > I was then able to register mibs.
>> >
>> > Thanks,
>> > Kent
>>


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to