|
|
| Subject: | Container can't connect to serviced |
| Author: | Jim R |
| Posted: | 2016-06-17 16:33 |
I've a service using 2 containers. When I import the service into Control Center and start it, one container starts properly, but the other shows the following:
I0617 21:31:15.487882 00001 vif.go:58] vif subnet is: 10.3
I0617 21:31:15.487996 00001 lbClient.go:79] ControlPlaneAgent.GetServiceInstance()
E0617 21:31:15.488474 00001 controller.go:144] Error getting service dq788aze6xub3osh4awg4sw7x error: dial tcp4 127.0.0.1:4979: connection refused
E0617 21:31:15.488527 00001 controller.go:292] dial tcp4 127.0.0.1:4979: connection refused
E0617 21:31:15.488550 00001 controller.go:293] Invalid service from serviceID:dq788aze6xub3osh4awg4sw7x
container: invalid serviced
serviced then continually tries to restart a new container, to no avail.
Is there a good way to debug this
My service definition is in https://github.com/jregovic/Seyren.CC
| Subject: | You can try to increse log |
| Author: | Jan Garaj |
| Posted: | 2016-06-21 19:54 |
You can try to increse log level to get more details in log file - SERVICED_LOG_LEVEL in /etc/default/serviced
TBH: Control Center is optimized for Zenoss use case only. It's not a good orchestration tool for some dockerized apps, which can be your case.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | Turns out my Docker image was |
| Author: | Jim R |
| Posted: | 2016-06-22 10:11 |
Turns out my Docker image was bunk. Once Iremoved the old images and re-synced the local registry, I got the service to run the proper Docker image.
One thing that I have discovered with Control Center is that the Docker image really needs to be built using the ENTRYPOINT and CMD combination.
Control Center creates the container and runs it using /serviced/serviced-controller SERVICEID INSTANCE COMMAND.
It is best to setup the image to run without forking as well. I am planning a wiki post about what I've discovered as it might be useful. As of now, I've managed to completely encapsulate Seyren instance inside of Control Center.
| < |
Previous What does this alert in means in Zenoss? Error:IO Error: Connection reset alert. ... |
Next Transform changes between Zenoss v3 and v5 |
> |