-
Bug
-
Resolution: Done
-
Medium
-
None
-
Dublin Release
I have deployed ONAP Dublin on bare metal about 2 months ago. Everything was working properly after deployment. But, suddenly from last few days, getting problem in dmaap-message-router-mirrormaker (getting CrashLoopBackOff). The error are as follows:
dev-dmaap-message-router-mirrormaker-677857bbc-gjpns 0/1 CrashLoopBackOff 7988 75d
The log for pod dmaap-message-router-mirrormaker is:
+ exec start-mirrormaker.sh
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.38/containers/dev-dmaap-message-router-mirrormaker-677857bbc-gjpns/json: dial unix /var/run/docker.sock: connect: permission denied
2019-10-07 10:36:15 INFO - mmagenthome is set :/opt loading properties at /etc/mmagent.config
2019-10-07 10:36:15 INFO - kafkahome is set :/opt/kafka
2019-10-07 10:36:15 ERROR - Exception Occered java.net.SocketException: Unexpected end of file from server
2019-10-07 10:36:15 ERROR - Problem publishing to topic, please verify the config org.onap.dmaap.mr.mirrormakeragent MR URL is:http://message-router:3904 Error is: ERROR:Unexpected end of file from server
ERROR: mmagent startup unsuccessful, please make sure the mmagenthome /etc/mmagent.config is set and mechid have the rights to the topic
I also did robot health check and got the following error corresponding to dmaap:
Basic DMAAP Data Router Health Check | PASS |
------------------------------------------------------------------------------
Basic DMAAP Message Router Health Check [ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', error(104, 'Connection reset by peer'))': /topics
[ WARN ] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', error(104, 'Connection reset by peer'))': /topics
[ WARN ] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', error(104, 'Connection reset by peer'))': /topics
FAIL |
ConnectionError: HTTPConnectionPool(host='message-router.onap', port=3904): Max retries exceeded with url: /topics (Caused by ProtocolError('Connection aborted.', error(104, 'Connection reset by peer')))
And in SDC health check "U-EB cluster is not available"
{ "healthCheckComponent": "DE", "healthCheckStatus": "DOWN", "description": "U-EB cluster is not available" },