|
|
| Subject: | Core 5 continually fails |
| Author: | Jim R |
| Posted: | 2015-09-29 10:41 |
I have an instance of Core 5 that continually fails. Usually, it is the elasticsearch-logstash service that won't start.
I've reinstalled several times and still have this issue creep up. So far, this is a test instance, so it is more of an annoyance, but I can't really roll this into production with these issues.
Is there some detail somewhere thatI haven't found
I am seeing lots of erros like this everytime I try and start:
Sep 29 10:33:39 server.mydomain.com docker[30356]: time="2015-09-29T10:33:39-05:00" level="error" msg="Handler for POST /containers/{name:.*}/start returned error: Could not get container for serviced-isvcs_elasticsearch-logstash"
Sep 29 10:33:39 server.mydomain.com docker[30356]: time="2015-09-29T10:33:39-05:00" level="error" msg="HTTP Error: statusCode=500 Could not get container for serviced-isvcs_elasticsearch-logstash"
Sep 29 10:33:39 server.mydomain.com serviced[2599]: E0929 15:33:39.987874 02599 manager.go:418] Error starting isvc logstash: API error (500): Could not get container for serviced-isvcs_elasticsearch-logstash
| Subject: | Your docker has some problem |
| Author: | Jan Garaj |
| Posted: | 2015-09-29 11:32 |
Your docker has some problem for example full docker volume.
Check your docker logs and df -ha.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | The docker volume appears |
| Author: | Jim R |
| Posted: | 2015-09-29 12:19 |
The docker volume appears fine, and I can't find anything meaningful in any docker output. Is there somplace other than /var/log/messages that I should be looking
| Subject: | docker logs: journalctl -u |
| Author: | Jan Garaj |
| Posted: | 2015-09-29 12:56 |
docker logs: journalctl -u docker -a -n 100
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | This is what I keep seeing, |
| Author: | Jim R |
| Posted: | 2015-09-29 13:20 |
This is what I keep seeing, but I can't figure out exactly where the problem is. Could there be file/directory permissions somewhere
| Subject: | write unix @: broken pipe |
| Author: | Jan Garaj |
| Posted: | 2015-09-29 13:31 |
write unix @: broken pipe
Pls provide df -ha
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | Nothing seems full, and I can |
| Author: | Jim R |
| Posted: | 2015-09-29 14:09 |
Nothing seems full, and I can't figure out what is causing the broken pipe.
I am also seeing a lot of messages like :
Warning: couldn't load ... from zenoss/core_5.0/5.0.3_RC7: could not find image: no such id...
Which I find odd as I have never installed that version
| Subject: | OK, I am not sure what was |
| Author: | Jim R |
| Posted: | 2015-09-29 15:33 |
OK, I am not sure what was going on, but there were some stale elasticsearch processes running that appear to have been in the way.
Killing those appears to have fixed my issues.
| < |
Previous Problem installing percona. |
Next Zenoss Core Community can not find Resource Manager when trying to deploy. |
> |