ZenPacks, JSON API, and Integrations

Expand all | Collapse all

Questions about Docker ZenPack

  • 1.  Questions about Docker ZenPack

    Posted 16 days ago
    We tried to install Docker ZenPack v2.0.3 (the latest) on Zenoss 6.2.1, but the install failed: https://help.zenoss.com/in/zenpack-catalog/open-source/docker

    It says that it is Compatible with Zenoss 4.2.5 - 6.1, so this isn't surprising.

    Are there any plans to support Zenoss 6.2.1?

    As info, the end of the install is shown below.

    Thanks,
    Larry

    2019-10-30 03:57:14,934 INFO zpl.ZenPack: Finished adding ZenPacks.zenoss.Docker relationships to existing devices
    2019-10-30 03:57:16,558 ERROR zen.ZenPackCMD: Error installing ZenPack ZenPacks.zenoss.Docker-2.0.3.egg
    Traceback (most recent call last):
    File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 257, in InstallEggAndZenPack
    ignoreServiceInstall=ignoreServiceInstall)
    File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 524, in InstallDistAsZenPack
    zenPack, deferFileDeletion, existing = transactional_actions()
    File "/opt/zenoss/lib/python2.7/site-packages/ZODB/transact.py", line 51, in g
    _commit(note)
    File "/opt/zenoss/lib/python2.7/site-packages/ZODB/transact.py", line 23, in _commit
    t.commit()
    File "/opt/zenoss/lib/python2.7/site-packages/transaction/_transaction.py", line 310, in commit
    reraise(t, v, tb)
    File "/opt/zenoss/lib/python2.7/site-packages/transaction/_transaction.py", line 301, in commit
    self._commitResources()
    File "/opt/zenoss/lib/python2.7/site-packages/transaction/_transaction.py", line 446, in _commitResources
    reraise(t, v, tb)
    File "/opt/zenoss/lib/python2.7/site-packages/transaction/_transaction.py", line 423, in _commitResources
    rm.tpc_vote(self)
    File "/opt/zenoss/lib/python2.7/site-packages/ZODB/Connection.py", line 797, in tpc_vote
    s = vote(transaction)
    File "/opt/zenoss/lib/python2.7/site-packages/perfmetrics/__init__.py", line 133, in call_with_metric
    return f(*args, **kw)
    File "/opt/zenoss/lib/python2.7/site-packages/relstorage/storage.py", line 958, in tpc_vote
    resolved_by_vote = self._vote()
    File "/opt/zenoss/lib/python2.7/site-packages/relstorage/storage.py", line 1008, in _vote
    resolved_serials = self._finish_store()
    File "/opt/zenoss/lib/python2.7/site-packages/relstorage/storage.py", line 924, in _finish_store
    rdata = self.tryToResolveConflict(oid, prev_tid, serial, data)
    File "/opt/zenoss/lib/python2.7/site-packages/ZODB/ConflictResolution.py", line 299, in tryToResolveConflict
    data=newpickle)
    ConflictError: database conflict error (oid 0xf1c2, class ZenPacks.zenoss.Microsoft.Windows.Device.Device, serial this txn started with 0x03d374ed3c10be44 2019-10-30 03:57:14.077829, serial currently committed 0x03d374ed44965344 2019-10-30 03:57:16.075127)
    Command returned non-zero exit code 3. Container not committed.

    ------------------------------
    Larry
    Sr. Systems Engineer
    IPC Global
    Alpharetta GA
    470-407-9100 ext 136
    ------------------------------


  • 2.  RE: Questions about Docker ZenPack

    Posted 13 days ago
    Edited by Arthur 13 days ago
    Hi Larry

    I had the experience that often they are behind of updating the documentation for the ZP if a new Zenoss Core version is available.  Mostly what is compatible with 6.X is also working on later 6.X releases.

    I've installed the docker ZP 2.0.3 on my Core 6.2.1 r218, CC 1.5.1, ZenPackLib 2.1.1 and it worked. I've attached the installation trace, ZP list and picture.

    If I'm looking at your trace, it looks like you have an issue with your database.

    I would first try to scan your DB

    https://support.zenoss.com/hc/en-us/articles/203118175-How-To-Use-zodbscan-To-Scan-ZODB-for-Dangling-References

    https://support.zenoss.com/hc/en-us/articles/203121165-How-to-Use-zenrelationscan-to-Scan-Fix-Zenrelations

    Kind regards
    Arthur

    P.S. Some additional links my help you                                                                        

    https://support.zenoss.com/hc/en-us/articles/211554906-In-Zenoss-Resource-Manager-What-does-zpl-mean-

    https://github.com/zopefoundation/ZODB/blob/master/src/ZODB/ConflictResolution.py



    ------------------------------
    Arthur
    ------------------------------

    Attachment(s)



  • 3.  RE: Questions about Docker ZenPack

    Posted 12 days ago
    Hi Arthur,
       Thanks for the response! I ran the toolkit commands but didn't find any errors. I then tried the zenpack install again, and it WORKED! Strange.

    I'm showing 41 docker containers though, and you only show 3. Is your device a Zenoss master? I suspect yes. I'm also showing 91 file systems, so I think my server has some things wrong. It was our first Zenoss 6 install, and it's being used as a sandbox. Any suggestions for cleanup are welcome. This command only cleaned up 3 containers:

    docker rm $(docker ps -q -f status=exited)

    Thanks,
    Larry

    ------------------------------
    Larry
    Sr. Systems Engineer
    IPC Global
    Alpharetta GA
    470-407-9100 ext 136
    ------------------------------



  • 4.  RE: Questions about Docker ZenPack

    Posted 12 days ago

    Hi Larry

    Great to hear that the docker ZP installation was successful.

    No, this is not my Zenoss master. I haven't assigned the docker modeling template to my Zenoss servers yet.
    It's a box running nextcloud from a docker image.

    I think, if you check your services in CC and all are showing the blue bullet with the checkmark your environment should be fine. You can also use the commands

    # serviced service status

    and check the status, HC Fail and InSync fields.

    Often I use the following commands to remove stray containers.

    https://support.zenoss.com/hc/en-us/articles/211783563-Zenoss-Master-Staged-Startup-and-Shutdown-Best-Practices-for-Maintenance-

    # systemctl stop serviced                                                             // Master and Resource Pool workers

     

    # docker ps –a                                                                                 // Check remaining containers M & RP workers
    # docker ps -qa  | xargs --no-run-if-empty docker rm –fv       // M & RP workers

    It's also not worth to check if you have any remaining snapshots you don't need anymore.

     # serviced snapshot list

    Cheers

    ------------------------------
    Arthur
    ------------------------------