All Resource Manager components run on the same vm. Impact runs on its own vm.
Subject: |
RE: How to get Dynamic View to work in Zenoss RM 4.2.5 Enterprise |
Author: |
Larry Ouellette |
Posted: |
2018-07-16 09:37 |
zenjserver log after switching to debug mode:
2018-07-16 09:10:36,944 INFO zen.JServer.JavaClient: stop():stopping java client
2018-07-16 09:10:36,946 INFO zen.ZenJServer: Deleting PID file /opt/zenoss/var/zenjserver-localhost.pid ...
2018-07-16 09:10:36,946 INFO zen.ZenJServer: Daemon ZenJServer shutting down
2018-07-16 09:10:59,557 DEBUG zen.JServer: Retrieving java client startup args
2018-07-16 09:10:59,558 INFO zen.JServer.JavaClient: run():starting java process
2018-07-16 09:10:59,558 DEBUG zen.JServer.JavaClient: run():spawn process ('java', '-server', '-Xmx512m', '-Dorg.eclipse.jetty.server.Request.maxFormContentSize=10000000', '-jar', '/opt/zenoss/ZenPacks/ZenPacks.zenoss.DynamicView-1.2.2-py2.7.egg/ZenPacks/zenoss/DynamicView/ZenJServer.jar', '-port', '8700')
2018-07-16 09:10:59,563 DEBUG zen.JServer.JavaClient: connectionMade():java client started
2018-07-16 09:10:59,564 DEBUG zen.JServer.JavaClient: connectionMade():scheduling callback
2018-07-16 09:10:59,564 DEBUG zen.JServer.JavaClient: connectionMade(): done
2018-07-16 09:10:59,928 INFO zen.JServer.JavaClient: 2018-07-16 09:10:59.927:INFO:oejs.Server:jetty-7.5.3.v20111011
2018-07-16 09:10:59,988 INFO zen.JServer.JavaClient: 2018-07-16 09:10:59.988:INFO:oejsh.ContextHandler:started o.e.j.s.ServletContextHandler{/,null}
2018-07-16 09:11:00,027 INFO zen.JServer.JavaClient: 2018-07-16 09:11:00.026:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8700 STARTING
2018-07-16 09:11:02,566 DEBUG zen.JServer.JavaClient: doCallback(): callback on deferred java client proc is up
------------------------------
Larry Ouellette
Automation Administrator
Boston University - IS&T
Boston Massachusetts
617-353-9190
------------------------------