About almulaiki

almulaiki · ‎04-28-2017

Dears, Just to update: I found the solution in https://community.hortonworks.com/articles/18088/ambari-shows-hdp-services-to-be-down-whereas-they.html "One of the issue could be due to /var/lib/ambari-agent/data/structured-out-status.json. Cat this file to review the content. Typical content could be like following: cat structured-out-status.json {"processes": [], "securityState": "UNKNOWN"} Compare the content with the same file in another node which is working fine. Stop ambari-agent, move this file to another file and restart ambari-agent." After that I restarted ambari-agent on the relevant host and things working back properly.

almulaiki · ‎04-26-2017

@Aravindan Vijayan But why this issue is not showing in my another testing HDP 2.4 cluster which start running few months back?!

almulaiki · ‎04-26-2017

@Aravindan Vijayan Thanks a lot for your response Aravindan, I spent days on this issue and just found now that: 1) When I kill the process with ": : :3000" and restart services, they run and then go down from ambari dashboard only. 2) When I checked some services using urls with specific ports, I found services are running . Which one is not risky, upgrading HDP or manually updating Grafana, I spent long in building the cluster and I do not want to come up with new unexpected issues? If you have best and clear reference to follow in upgrading , it will be highly appreciated?

almulaiki · ‎04-26-2017

@amarnathreddy pappu I followed what you recommended, Grafana ran for sometime and goes down with all services in the same host. Whenever I kill the process before restarting all services in the host where Grafana is installed, all services works for few seconds and all go down immediately. Why should I kill the process ": : : 3000" every time and no way to prevent it from running at all? Why all services go down only in this specific host? Please help?

almulaiki · ‎04-25-2017

@amarnathreddy pappu Thank you very much. I run that command but it seems that no proccess is using that port. Could you please check the attached screenshot to see if I am right? if yes, what the issue then netstat-anlp-3000.png

almulaiki · ‎04-24-2017

@amarnathreddy pappu Thank you very much. I think I have tried that, I will try that again and inform you. so what should I do if another service take that port, just killing that service? The proper way to check if another service running that port, in Ubuntu?

almulaiki · ‎04-24-2017

Dears, I need your help in fixing Grafana relevant issue: when I start services using Ambari, all start successfully except Grafana. And after it fails to start, all other services in the same host fail also. While I was troubleshooting, I found that : 1) Process id in "grafana-server.pid" is not matching the actual Id which is shown from "ps aux | grep grafana". After changing it manaully in grafana-server.pid, it changes back to mismatched PID after I restart Grafana. 2) in "/var/log/ambari-metrics-grafana/log", it says that "web.go:93 StartServer()] [E] Fail to start server: listen tcp 0.0.0.0:3000: bind: address already in use" Please your kind help? grafana-error-1377.txt grafana-error-output-1377.txt grafana-log.txt

Online	Offline
Last Visited	‎08-26-2017 06:48 PM

Member Since	‎04-22-2017 08:25 PM
Last Visited	‎08-26-2017 06:48 PM
Posts	8

Cloudera Community

Re: Garafana faild to start

Re: Garafana faild to start

Re: Garafana faild to start

Re: Garafana faild to start

Re: Garafana faild to start

Re: Garafana faild to start

Re: Garafana faild to start

Garafana faild to start