Matthew, Sorry to hear you are having problems deploying Clearwater on Docker.
I think that the socket factory error is actually fairly benign. Does this happen every time you create your deployment? Can you provide the config map that you are providing when deploying on Kubernetes? Can you connect into one of the pods that is failing to run homestead-prov and grab the logs. The relevant ones will be under /var/log/homestead-prov inside the container. We cannot reproduce your issue on our kubernetes setup - can you provide details of your kubernetes setup - what version of k8s and what networking configuration you are using? >From the diagnostics we have at the moment, the most likely scenario is that >the Homestead and Homestead Prov containers are unable to contact Cassandra - >if that's the case they will continually restart to attempt to resolve the >problem. Richard From: Clearwater [mailto:[email protected]] On Behalf Of Davis, Matthew Sent: 14 May 2018 07:05 To: [email protected] Subject: Re: [Project Clearwater] Issues with clearwater-docker homestead and homestead-prov under Kubernetes Hi everyone, I've fixed the issue I had with homestead-prov and submitted the patch as this pull request: https://github.com/Metaswitch/clearwater-docker/pull/89 However now I just run into another issue, so homestead-prov is giving me the same error as homestead. The error message is not verbose. Does anyone know how to make it more verbose? I have no idea what's happening. ``` 2018-05-14 05:47:41,369 INFO success: snmpd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-05-14 05:47:41,370 INFO success: clearwater-infrastructure entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-05-14 05:47:42,476 INFO success: socket-factory-sig entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-05-14 05:47:42,476 INFO success: socket-factory-mgmt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-05-14 05:47:42,477 INFO exited: snmpd (exit status 0; expected) 2018-05-14 05:47:42,478 CRIT reaped unknown pid 61) 2018-05-14 05:47:44,572 CRIT reaped unknown pid 65) 2018-05-14 05:47:44,576 CRIT reaped unknown pid 66) 2018-05-14 05:47:45,883 CRIT reaped unknown pid 235) 2018-05-14 05:47:45,883 CRIT reaped unknown pid 236) 2018-05-14 05:47:45,902 CRIT reaped unknown pid 257) 2018-05-14 05:47:48,153 CRIT reaped unknown pid 294) 2018-05-14 05:47:48,226 INFO spawned: 'homestead-prov' with pid 297 2018-05-14 05:47:48,237 INFO spawned: 'nginx' with pid 298 2018-05-14 05:47:48,747 INFO exited: homestead-prov (exit status 0; not expected) 2018-05-14 05:47:49,750 INFO spawned: 'homestead-prov' with pid 324 2018-05-14 05:47:49,750 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-05-14 05:47:50,089 INFO exited: clearwater-infrastructure (exit status 0; expected) 2018-05-14 05:47:50,335 INFO exited: homestead-prov (exit status 0; not expected) 2018-05-14 05:47:52,339 INFO spawned: 'homestead-prov' with pid 335 2018-05-14 05:47:53,324 INFO exited: homestead-prov (exit status 0; not expected) 2018-05-14 05:47:56,330 INFO spawned: 'homestead-prov' with pid 346 2018-05-14 05:47:56,902 INFO exited: homestead-prov (exit status 0; not expected) 2018-05-14 05:47:57,904 INFO gave up: homestead-prov entered FATAL state, too many start retries too quickly ``` Regards, Matt Davis Telstra | Graduate Engineer
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
