![]() |
![]() |
Subject: | Zenoss 5 Zenpack install: The current working directory must be world readable+executable |
Author: | [Not Specified] |
Posted: | 2015-03-24 13:02 |
Subject: | The system deleted the entire body of my post. It is below... I |
Author: | [Not Specified] |
Posted: | 2015-03-24 13:04 |
[root@zenoss2 ~]# serviced service run zope zenpack install ZenPacks.vmware.VirtualMachines-1.2.3.egg
I0324 13:48:23.272897 02029 server.go:341] Connected to the control center at port 192.168.155.249:4979
I0324 13:48:23.403607 02029 server.go:435] Acquiring image from the dfs...
I0324 13:48:23.406008 02029 server.go:437] Acquired! Starting shell
E0324 17:48:24.198196 00001 endpoint.go:514] No proxy for 9sir6rqokqm7eyzlup2hp4b6y_localhost_zenhubPB - no need to set empty address list
E0324 17:48:24.200528 00001 endpoint.go:514] No proxy for 9sir6rqokqm7eyzlup2hp4b6y_zproxy - no need to set empty address list
Trying to connect to logstash server... 127.0.0.1:5042
Connected to logstash server.
Error: The current working directory must be world readable+executable
Command returned non-zero exit code 1. Container not commited.
Any ideas
Subject: | sounds like your filesystem |
Author: | Andrew Kirch |
Posted: | 2015-03-25 14:24 |
sounds like your filesystem permissions are set incorrectly. I'd specifically look at your btrfs mountpoint in this case.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
Subject: | The problem is that the |
Author: | Matt |
Posted: | 2015-03-25 18:24 |
The problem is that the ZenPack is located in the home directory of root.
Therefore the installation process (which is running as a different user within the container) can't access the file.
Put the ZenPack into the /tmp folder and you should be good to go. :)
Subject: | Thanks Matze - that did the trick |
Author: | [Not Specified] |
Posted: | 2015-03-28 22:15 |
I tried it with other users but never out of the temp directory. Might be a good add to the troubleshooting index or the procedure itself.
Thanks!
< |
Previous Zenoss Core 5 - How do I install a ZenPack? CLI only? Which ZenPacks are Support ... |
Next IISSite: Failed collection |
> |