Zenoss ZenTech Community

I need to know how to commit a container after the Zenpack was installed. Another team member imported two new ZenPacks which work fine but I get the error below. Help!

I0126 19:29:01.692954 08484 server.go:341] Connected to the control center at port 10.##.##.##:4979

ZenPacks.zenoss.PythonCollector (/opt/zenoss/ZenPacks/ZenPacks.zenoss.PythonCollector-1.7.2-py2.7.egg)

ZenPacks.zenoss.ZenJMX (/opt/zenoss/ZenPacks/ZenPacks.zenoss.ZenJMX-3.11.1-py2.7.egg)

ZenPacks.zenoss.ZenMail (/opt/zenoss/ZenPacks/ZenPacks.zenoss.ZenMail-5.0.0-py2.7.egg)

Subject:	Since the ZenPacks are
Author:	Ken Jenkins
Posted:	2016-01-26 15:03

Since the ZenPacks are working, I am going to run through the process to install a new ZenPack in Zenoss Core 5. I will snapshot and commit my changes and hope for the best.

Subject:	I installed a new ZenPack
Author:	Ken Jenkins
Posted:	2016-01-26 20:30

I installed a new ZenPack successfully. The container was commited.

I0127 02:07:39.937042 09910 shell.go:225] Committing container

I ran another zenpack list and still see ...

...

ZenPacks.zenoss.ZenMail (/opt/zenoss/ZenPacks/ZenPacks.zenoss.ZenMail-5.0.0-py2.7.egg)

Command returned non-zero exit code 1. Container not commited.

Any ideas regarding if this is an issue

Subject:	The "Command returned non
Author:	Chet Luther
Posted:	2016-01-29 08:04

The "Command returned non-zero exit code 1. Container not commited." message when running "serviced service run zope zenpack list" is normal. For now the way we prevent the container from being committed by listing the ZenPacks is to return a non-zero exit code. There's no need to commit anything when just listing ZenPacks.

Subject:	Chet,
Author:	Ken Jenkins
Posted:	2016-01-29 09:27

Chet,

Great to know. Thanks for clarifying.

Ken

Subject:	Zenoss Core 5 - Container Not Committed Error when Listing ZenPacks
Author:	Ken Jenkins
Posted:	2016-01-26 13:32

Zenoss Core 5 - Container Not Committed Error when Listing ZenPacks