TECHZEN Zenoss User Community ARCHIVE  

Beta 3 Issues with VM Image

Subject: Beta 3 Issues with VM Image
Author: [Not Specified]
Posted: 2015-01-29 12:11

I downloaded the VM image for beta 3 and followed the install guide.
Added the host entries to DNS and the local /etc/hosts
Deployed the ZenOSS application to the default resource pool

When I started it, I got a blue check mark on the front page. zenoss5x.host.domain was very, very slow and clicking on Events or Infrastructure produced portal errors.

When I went in to view the services, there were some that had a red exclamation mark that I assume would be critical:
CentralQuery (answering)
HMaster (cluster_healthy, rest_answering)
RegionServer (answering, cluster member)
zenhub (zep_answering)
opentsdb (answering)
zeneventserver (answering, running, zep_answering)
Zope (zep_answering)

I've stopped, restarted, and rebooted a number of times.

In the log (through control center) I found the following:

E0129 16:01:52.956172 00001 proxy.go:249] Error (net.Dial): dial tcp4 172.17.0.63:9080: connection refused
E0129 16:01:53.055086 00001 proxy.go:249] Error (net.Dial): dial tcp4 172.17.0.63:9080: connection refused
E0129 16:01:53.147401 00001 proxy.go:249] Error (net.Dial): dial tcp4 172.17.0.63:9080: connection refused
E0129 16:01:53.276667 00001 proxy.go:249] Error (net.Dial): dial tcp4 172.17.0.63:9080: connection refused
E0129 16:01:53.358693 00001 proxy.go:249] Error (net.Dial): dial tcp4 172.17.0.63:9080: connection refused

Any ideas what to try to debug the set up



Subject: More info
Author: [Not Specified]
Posted: 2015-01-29 13:31

After digging around a bit, I found the following error in the HMASTER instance log:

{"log":"I0129 19:20:18.637928 00001 controller.go:604] Restarting service process in 10 seconds.\n","stream":"stderr","time":"2015-01-29T19:20:18.638107181Z"}
{"log":"Invalid maximum heap size: -Xmx0m\n","stream":"stderr","time":"2015-01-29T19:20:18.654544105Z"}
{"log":"Error: Could not create the Java Virtual Machine.\n","stream":"stderr","time":"2015-01-29T19:20:18.654544105Z"}
{"log":"Error: A fatal exception has occurred. Program will exit.\n","stream":"stderr","time":"2015-01-29T19:20:18.654544105Z"}
{"log":"2015/01/29 19:20:20.790226 Registrar received 3 events\n","stream":"stderr","time":"2015-01-29T19:20:20.790408698Z"}

For CentralQuery:
{"log":"I0129 15:58:52.401504 00001 endpoint.go:591] Attempting port map for: 77vgjn5417gl1p9v9c8zsap8f_zproxy -\u003e {ServiceID:77vgjn5417gl1p9v9c8zsap8f Application:zproxy ContainerPort:8080 HostPort:49159 HostIP:192.168.151.57 ContainerIP:172.17.0.13 Protocol:tcp VirtualAddress: InstanceID:0 ProxyPort:8080}\n","stream":"stderr","time":"2015-01-29T15:58:52.401751866Z"}
{"log":"I0129 15:58:52.401685 00001 endpoint.go:611] Success binding port: 77vgjn5417gl1p9v9c8zsap8f_zproxy -\u003e proxy[{77vgjn5417gl1p9v9c8zsap8f zproxy 8080 49159 192.168.151.57 172.17.0.13 tcp 0 8080}; \u0026{%!s(*net.netFD=\u0026{{0 0 0} 18 2 1 false tcp4 0xc208917800 reflect.Value {140397714820472}})}]=\u003e[]\n","stream":"stderr","time":"2015-01-29T15:58:52.401795738Z"}
{"log":"2015-01-29 15:58:53,139 INFO success: central-query entered RUNNING state, process has stayed up for \u003e than 5 seconds (startsecs)\n","stream":"stdout","time":"2015-01-29T15:58:53.139930711Z"}
{"log":"W0129 15:58:54.708136 00001 controller.go:773] Health check answering failed.\n","stream":"stderr","time":"2015-01-29T15:58:54.70825209Z"}
{"log":"2015/01/29 15:58:56.624525 Registrar received 4 events\n","stream":"stderr","time":"2015-01-29T15:58:56.624702154Z"}
{"log":"2015/01/29 15:58:59 200 8.173238ms POST /api/metrics/store\n","stream":"stderr","time":"2015-01-29T15:58:59.121708245Z"}
{"log":"W0129 15:58:59.956943 00001 controller.go:773] Health check answering failed.\n","stream":"stderr","time":"2015-01-29T15:58:59.957098728Z"}

I can dig through the others, but I think HMASTER is the one I need to resolve.



Subject: Managed to solve the heap
Author: [Not Specified]
Posted: 2015-01-29 15:13

Managed to solve the heap size issue on HMaster and RegionServer and that seems to have cleaned up a lot of the issues.
These services are still not running:
zenhub (zep_answering)
zeneventserver (answering, running, zep_answering)
Zope (zep_answering)

Has anyone got a working ZenOSS beta 3 VM working I imported the OVA and didn't expect any problems.



Subject: The OVA is a testing/demo
Author: Andrew Kirch
Posted: 2015-02-04 11:16

The OVA is a testing/demo system and is meant for evaluation. If you're looking to put 5.x into production, please create a Centos 7 VM and install manually following the instructions on the wiki.

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: Thanks for this helpful
Author: [Not Specified]
Posted: 2015-02-07 07:13

Thanks for this helpful answer Trelane!!!

I'm currently bumping into the same problem as Dmcushings. Anyway, V5 being a Beta version we don't want to put it in production, we only want to test it, just as the appliance is made for... if only we can make it work.
So my only concern is about solving problem to test Zenoss 5.



Subject: Same problems.... working through them
Author: [Not Specified]
Posted: 2015-02-22 17:29

I would like to be able to eval quickly and show others without having to build the system from scratch if possible.

Issues encountered so far:
- Xmx setting in zeneventserver causes failure. Setting the value manually in the UI has gotten the service started.
- always being redirected to the CC, no matter which hostname is entered
- Same failure for hbase as above - heap size.



Subject: 5.0 GA was released yesterday
Author: [Not Specified]
Posted: 2015-02-26 11:34

5.0 GA was released yesterday. Please let me know if these issues are still ongoing.



Subject: Zproxy_answering failed
Author: [Not Specified]
Posted: 2015-04-28 05:05

Hi, Resource manager is working fine after installation. But it got stopped after some time. When i restart it its not coming up.So started individual services from resource manager.

Metric shaper and zproxy_answering is not coming up.

Zope zproxy_answering failed, all other services are up except this one.

metric shaper (store_answering failed)
Zenhub (zproxy_answering failed)
Zope (zproxy_answering failed)

Metricshaper ERROR from logs :

ERROR 2015-04-28 09:53:54,433 org.zenoss.metrics.reporter.ZenossMetricsReporter: Error posting metrics
! org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:8080 refused
! at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190) ~metric-consumer-app-0.0.17.jar:na
! at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294) ~metric-consumer-app-0.0.17.jar:na
! at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:645) ~metric-consumer-app-0.0.17.jar:na
! at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:480) ~metric-consumer-app-0.0.17.jar:na
! at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) ~metric-consumer-app-0.0.17.jar:na
! at org.zenoss.app.consumer.metric.impl.MetricServicePoster.getTenantId(MetricServicePoster.java:156) ~metric-consumer-app-0.0.17.jar:na
! at org.zenoss.app.consumer.metric.impl.MetricServicePoster.post(MetricServicePoster.java:95) ~metric-consumer-app-0.0.17.jar:na
! at org.zenoss.metrics.reporter.ZenossMetricsReporter.post(ZenossMetricsReporter.java:275) ~metric-consumer-app-0.0.17.jar:na
! at org.zenoss.metrics.reporter.ZenossMetricsReporter.run(ZenossMetricsReporter.java:125) ~metric-consumer-app-0.0.17.jar:na
! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) na:1.7.0_75
! at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) na:1.7.0_75
! at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) na:1.7.0_75
! at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) na:1.7.0_75
! at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) na:1.7.0_75
! at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) na:1.7.0_75
! at java.lang.Thread.run(Thread.java:745) na:1.7.0_75

ERROR :
"I0428 10:02:07.350361 00036 pool.go:34] Unable to connect to consumer ws://localhost:8080/ws/metrics/store"
AND
W0428 10:02:04.929283 00001 controller.go:777] Health check store_answering failed.

Regards,
Sunnybmv



< Previous
Can't add new hosts
  Next
Datasource HttpMonitor FtpMonitor
>