|
|
| Subject: | OpenTSDB and Central Query Failing |
| Author: | [Not Specified] |
| Posted: | 2016-10-27 10:51 |
I've had my OpenTSDB and Central Query services failing for about 2 weeks now. It just happened over one weekend and I was unable to fix the issues since. I was originally on v 5.1.2, but just upgraded to 5.1.8 and the issue persists.
Opentsdb and central query are showing the red ! with answering. When I run journalctl -u serviced -fa on the resource host (resourceHost1IP)containing OpenTSDB, it keeps spitting out these entries:
Oct 27 12:31:46 fqdnhostnameserviced[30976]: E1027 16:31:46.176896 30976 mux.go:137] got resourceHost1IP:22250 => resourceHost2IP:56600, could not dial to '172.17.0.3:4242' : dial tcp4 172.17.0.3:4242: connection refused
I can't figure out why this is happening.
Anyone got any ideas or things to check I've already tried most of the things onhttps://support.zenoss.com/hc/en-us/articles/204643769-How-to-Recover-Control-Center-from-Hardware-Failure.
Any help would really be appreciated, Thanks.
| Subject: | Well, I realized that some |
| Author: | [Not Specified] |
| Posted: | 2016-10-27 11:47 |
Well, I realized that some commands onhttps://support.zenoss.com/hc/en-us/articles/204643769-How-to-Recover-Control-Center-from-Hardware-Failure has .resmgr instead of core (whoops). Once I reverted back to 5.1.2, I reran these commands and it seems to be working again. Now I will upgrade to 5.1.8 again and make sure it still works after that.
| < |
Previous Feature Enhancement |
Next SUP update for 4.2.5 overdue? |
> |