|
|
| Subject: | Struggling to get Zenoss Core to start |
| Author: | Larry Virden |
| Posted: | 2016-03-22 09:40 |
So, we are complete beginners with Centos and Zenoss. But we have been trying to follow along with the wiki and guides. We have gotten to the point where Control Center seems like it is working. We see Zenoss.Core on the list of applications. However, the 5.1.1. configuration guide, chapter3, itsays to find Zenoss.resmgr and click start.
We don't have anything called Zenoss.resmgr.
We tried to follow the instructions, only using Zenoss.Core, but when the endpoint URL appears, it is an https URL with a port on it. We click on that, and we get a browser page that says its unable to find the page - and the url displayed is missing the port 443.
We have been unable to figure out how to get the start wizard to start.
Has anyone else experienced this and found a solution for it
| Subject: | Have you got Zenoss.core |
| Author: | [Not Specified] |
| Posted: | 2016-03-22 11:14 |
Have you got Zenoss.coredisplayed in the list of Applications in the Control Center If, so, check that in theStatus displayed that the appliation has a blue checkmark. If Zenoss.core is not listed as an Application (just as an application template), then you've missed the step to deploy the Zenoss application to the Control Center.
| Subject: | Yes, we have a Zenoss.core |
| Author: | Larry Virden |
| Posted: | 2016-03-22 11:17 |
We have a Zenoss.core - just no Zenoss.resmgr like the documentation lists.
As for the other issue, we were modifying our box's /etc/hosts ... but our browser was running on our desktop and of course didn't SEE that /etc/hosts .
So we are working on getting the Zenoss endpoint URLs into LDAP so that they can be seen from our desks.
| Subject: | You don't need to modify any |
| Author: | [Not Specified] |
| Posted: | 2016-03-22 11:23 |
You don't need to modify any hosts files. You can create a zproxy endpoint to any URL you want as long asthe A record mapsto the IP address of the Control Center system. The internal DNS proxy will handle the host name mapping. That will be easier than using host files and cleaner.
And there is no Zenoss.resmgr; that must be a documentation flaw. So long as the Zenoss.core app is blue-checked, it's good.
| Subject: | Chapter 3 of the 5.1.1. |
| Author: | Larry Virden |
| Posted: | 2016-03-22 11:31 |
Chapter 3 of the 5.1.1. configuration guide mentions the Zenoss.resmgr several times - even appears in a screen shot. I finally figured it must be a mistake, but took us quite a while to get there.
I don't understand your comment about creating a zproxy endpoint. I apologize. I'm new to DNS as well.
| Subject: | please submit a defect if the |
| Author: | Andrew Kirch |
| Posted: | 2016-03-22 11:38 |
please submit a defect if the core documentation has resmgr references.
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: | No worries. If you click on |
| Author: | [Not Specified] |
| Posted: | 2016-03-22 11:46 |
No worries. If you click on the Zenoss.core application, it'll open up the application configuration. The top section will be the Public Endpoints section, where you'll have:
Zenoss.core of type zproxy with an address of https://zenoss5.your server fqdn
Along with the HMaster, opentsdb, and RabbitMQ. Click on Add public endpoint and add the name of what you want the Zenoss,core name to be: for us, the Control Centre's URL is cc.company.local, and I've created a new zproxy service endpoint as zenoss.company.local, similar to the screenshot I've attached.In DNS, cc.company.local maps to 192.168.1.10, so I've added another record for zenoss.company.local which also maps to 192.168.1.10. Then I can access Zenoss directly at https://zenoss.company.local.
| < |
Previous Zenoss Perl API and 5.1.1 |
Next Populating Graphs - Zenmodeler |
> |