|
|
| Subject: | How to make server listening on port 4979 as agent? |
| Author: | [Not Specified] |
| Posted: | 2016-06-03 09:30 |
Hello
This is the first time I am trying to install and use Zenoss, I was able to install the Zenoss Core 5 (zenoss-core-service-5.1.3-1.noarch) on one server and access its Admin UI, I saw some errors on some zenoss.core services: e.g. HMaster, Regionservice..., but in general it is working and monitoring itself.
I wanted to add another host, but I am not sure how to make it listen on port 4979 -or any port- to communicate properly with the master. After reading the documentation, I thought I hadto install docker and serviced on any new agent, so I reused part of the same script that I used to install the master, and I was able to install Docker (docker-engine-1.9.0-1.el7.centos.x86_64); RPC (rpcbind-0.2.0-33.el7_2.x86_64); and serviced (serviced-1.1.5-1.x86_64).
I was able to start Docker and RPC, but I was getting and error when I tried to start serviced:
systemctl status serviced
serviced.service - Zenoss ServiceD
Loaded: loaded (/usr/lib/systemd/system/serviced.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-06-03 07:11:43 PDT; 859ms ago
Process: 3870 ExecStopPost=/opt/serviced/bin/serviced-systemd.sh post-stop (code=exited, status=0/SUCCESS)
Process: 3856 ExecStart=/opt/serviced/bin/serviced $SERVICED_OPTS server (code=exited, status=1/FAILURE)
Process: 3843 ExecStartPre=/opt/serviced/bin/serviced-systemd.sh pre-start (code=exited, status=0/SUCCESS)
Main PID: 3856 (code=exited, status=1/FAILURE)
At this point I am not sure if I am on the right track, and what should I do to add new hosts to be monitored by the master I installed What should be listenning on port 4979 Should I have partitions on the agent server too
I appreciate any help or guidance.
Thank you
| Subject: | Hi, |
| Author: | [Not Specified] |
| Posted: | 2016-09-08 02:20 |
Hi,
Simply edit the vi /usr/lib/systemd/system/serviced.service and change SERVICED_MASTER=1 to SERVICED_MASTER=0.
This is an essential lack of information in the documentation guide.
Although /etc/default/serviced is correctly set with
# Set enable/disable the master role, set to 1/0, respectively
# SERVICED_MASTER=0
it ignores it when starting.
I tried reinstalling the resource host again(no zookeper), in case I skipped some steps, but had exactly your problem.
| Subject: | Pretty sure that step is in |
| Author: | Jay Stanley |
| Posted: | 2016-09-08 08:16 |
Pretty sure that step is in the documentation. Under "Installing resource pool hosts" > "Configuring and starting Control Center"
SERVICED_AGENT=1
SERVICED_MASTER=0
And the rest of the config needs to be changed as well. IP's and what not.
| Subject: | Hi, |
| Author: | [Not Specified] |
| Posted: | 2016-09-08 09:50 |
Hi,
I've already tried to set AGENT=1 and MASTER=0 but it was not enough to make it work.
After troubleshooting the logs, I changed also few params to point to Master address, and I was finally able to connect the Agent with the Master. It is working now, but I am not sure if what I did was the right thing to do or not
The params I changed were:
SERVICED_ZK=
SERVICED_DOCKER_REGISTRY=
SERVICED_ENDPOINT=
SERVICED_RPC_PORT=4979
SERVICED_LOG_ADDRESS=
SERVICED_STATS_PORT=
Thank you
| Subject: | Did you read the section I |
| Author: | Jay Stanley |
| Posted: | 2016-09-08 12:27 |
Did you read the section I posted about It covers exactly what you need to change.
Make sure you have the latest document as well from docs.zenoss.com
| < |
Previous MIB import issue |
Next Ignoring arguments related to loopback devices ? |
> |