The good news....
Zack has done a great job uploading all the right files to SourceForge, with all the consistent names. We have discussed the naming convention and agreed on what is now on SourceForge.
The bad news....
The autobuild script won't work as-of today because of the name changes. I need to change it anyway to pick up all the files from SourceForge but, I'm sorry Gals and Guys, it will probably be at least mid next week before I can do this. If anyone needs the script in the next week, please contact me directly and I'll try and guide you through.
Thanks again, Zack - great work.
Subject: |
RE: Zenoss 4 appears to have been axed |
Author: |
Jane Curry |
Posted: |
2019-01-04 12:37 |
Mike had a go with this script on Jan 3rd (before the filename changes) and it largely worked except for the final 2 spot patches. He reports the following:
Jane,
I attempted to use your latest autodeploy script for 4.2.5 on a CentOS6.10 fresh install. It seems to stop at this point. It hangs at the already running list, i eventually had to ctrl + c out.
Zenoss will start, but noticed issues with LinuxMonitor / SSH, so tried upgrading and got Python errors below:
Installed:
zenup.x86_64 0:1.1.0.267.869d67a-1.el6
Complete!
Downloading zenoss_community_edition-4.2.5-SP743-zenup11.zup...
Pristine file zenoss_core-4.2.5-2108.el6-pristine-SP203.tgz installed
SUP file zenoss_community_edition-4.2.5-SP743-zenup11.zup installed
Fixing Device.py for production state change - see ticket ZEN-30167.
patching file Products/ZenModel/Device.py
Hunk #1 FAILED at 1344.
1 out of 1 hunk FAILED -- saving rejects to file Products/ZenModel/Device.py.rej
Fixing actions.py for paging notification issue with SUP743
patching file Products/ZenModel/actions.py
Hunk #1 FAILED at 385.
Hunk #2 FAILED at 494.
2 out of 2 hunks FAILED -- saving rejects to file Products/ZenModel/actions.py.rej
Daemon: zeneventserver is already running
Daemon: zopectl daemon process already running; pid=8180
Daemon: zenrrdcached is already running
Daemon: zenhub is already running
Daemon: zenjobs is already running
Daemon: zeneventd is already running
Daemon: zenping is already running
Daemon: zensyslog is already running
Daemon: zenstatus is already running
Daemon: zenactiond is already running
Daemon: zentrap is already running
Daemon: zenmodeler is already running
Daemon: zenperfsnmp is already running
Daemon: zencommand is already running
Daemon: zenprocess is already running
Daemon: zredis is already running
Daemon: zenpython is already running
Daemon: zenjmx is already running
Seeing some issues with the I think Python. I've tried running easy_installl PyYAML. same results when re attemping ZenPack upgrade.
2019-01-02T23:22:00 INFO zen.ZenPackManager Output from installing ZenPack ZenPacks.zenoss.LinuxMonitor-2.2.7.egg:
ERROR:zen.zenpacklib:ZenPacks.zenoss.LinuxMonitor-2.2.7.egg requires PyYAML. Run "easy_install PyYAML".
ERROR:zen.ZenPackCMD:Error installing ZenPack /tmp/tmp5fI42t/ZenPacks.zenoss.LinuxMonitor-2.2.7.egg
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 247, in InstallEggAndZenPack
fromUI=fromUI)
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 477, in InstallDistAsZenPack
zenPack, deferFileDeletion, existing = transactional_actions()
File "/opt/zenoss/lib/python/ZODB/transact.py", line 44, in g
r = f(*args, **kwargs)
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 362, in transactional_actions
module = packEntry.load()
File "/opt/zenoss/lib/python/pkg_resources.py", line 1954, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.LinuxMonitor-2.2.7.egg/ZenPacks/zenoss/LinuxMonitor/__init__.py", line 24, in <module>
from . import schema
ImportError: cannot import name schema
Any help is appreciated
--------------------------------------------
I think this has probably installed everything except the two spot patches. I also think the problem with the LinuxMonitor ZenPack is probably unrelated to the build. Mike later reported on IRC:
"i think i got it working, blew the DB alway. tried again"
Mike - perhaps you could explain this one a bit more? Which DB did you blow?
If possible, Mike, I suggest we put any more experimentation with the autobuild script on hold for a week until I update it for Zack's work on the SourceForge site. I will also then re-address the failure of those two patches. For reference re those two patches, I have:
-rw-r--r-- 1 jane users 38139 Jan 4 17:29 actions.py_plus_skipfails_patch
-rw-r--r-- 1 jane users 37914 Dec 18 12:25 actions.py_SUP732
-rw-r--r-- 1 jane users 38152 Dec 18 12:34 actions.py_SUP743
-rw-r--r-- 1 jane users 84186 Dec 18 12:24 Device.py_SUP732
-rw-r--r-- 1 jane users 84136 Dec 18 12:42 Device.py_SUP743
-rw-r--r-- 1 jane users 84313 Dec 18 12:42 Device.py_SUP743_plus_patch
for the files in /opt/zenoss/Products/ZenModel - I think the nomenclature is self-evident? Mike, be interesting to know what size your Device.py and actions.py are?? (note these are my copies of the files - under /opt/zenoss, the files should be owned by zenoss:zenoss.
Thanks for everyone's help and patience with this.
Happy New Year to one and all,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------
Subject: |
RE: Zenoss 4 appears to have been axed |
Author: |
Jane Curry |
Posted: |
2019-01-10 12:55 |
I have updated the autodeploy script again today (Jan 10th, 2019) with the correct filenames on SourceForge and retested. I have also done some cleaning up, especially around the two little patches at the end of the script.
I would much appreciate any comments and feedback. The link to the autodeploy package on GitHub is
https://github.com/jcurry/Zenoss_4.2.5_core-autodeploy .
Cheers,
Jane
------------------------------
Jane Curry
Skills 1st United Kingdom
jane.curry@skills-1st.co.uk
------------------------------