I'm afraid I can't help that much from just that log snippet, without knowing
what containers you're seeing them in, or other information/logs.
I've taken a look at some of the logs on one of our test set ups, and find a
number of instances of the "CRIT Supervisor running as root (no user in config
file)\n","stream":"stdout","" log, when that deployment is running healthily. I
think that may be a symptom of the fact that some of our processes run as root
within the container, which is not a typical behaviour, but I don't believe
this log is a cause for concern, and so don't think your issue is due to
However, I can't find any instances of the Error log you have included, which
suggests that may be a part of your issue. I would suggest investigating that a
bit more. Possibly there is an issue in the networking meaning that your pods
cannot bind to sockets correctly. Are there security groups causing issues
If you can't resolve the issue, can you provide some more detailed information.
Which pods are restarting? Which logs are the 'Error' logs found in? Are there
any other errors shown in other outputs?
I'm afraid we have no direct experience of Stackube, so I'm not sure what else
Best of luck, and let us know how you progress,
From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On
Behalf Of Chirag Arora
Sent: 02 February 2018 05:44
Cc: Parwinder Singh <parwinder.si...@nectechnologies.in>; Atul Pandey
Subject: [Project Clearwater] Issue with Clearwater deployment on Stackube
We at NEC technologies, have been looking into Clearwater IMS on Kubernetes,
After preparing setup with STACKUBE, we went on to deploy Clearwater IMS on top
of it. Ref (https://github.com/Metaswitch/clearwater-docker/tree/master)
But we think we are facing an issue with "supervisord" due to with our pods
keeps on restarting. Debugging onto the same we looked into container
logs(/var/log/containers/) and found below suspicious logs.
"CRIT Supervisor running as root (no user in config
"Error: Cannot open an HTTP server: socket.error reported errno.ENXIO (6)\n"
We are not sure if we are looking into the right direction but if anyone can
share his/her expertise in debugging the same or help us in providing any
pointers it would be really helpful.
Clearwater mailing list