[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: oc cluster up - router not starting

Hi Cesar,

I stopped apache and now it works. Thanks a lot for help.

Best Regards,

On Wed, Oct 25, 2017 at 8:06 PM, Cesar Wong <cewong redhat com> wrote:
Hi Jan,

So I see this in your log:

E1025 15:45:01.408533    6242 pod_workers.go:182] Error syncing pod 6734f809-b99b-11e7-9b1d-3a4633f0fe38 ("router-1-fmvnv_default(6734f809-b99b-11e7-9b1d-3a4633f0fe38)"), skipping: failed to "CreatePodSandbox" for "router-1-fmvnv_default(6734f809-b99b-11e7-9b1d-3a4633f0fe38)" with CreatePodSandboxError: "CreatePodSandbox for pod \"router-1-fmvnv_default(6734f809-b99b-11e7-9b1d-3a4633f0fe38)\" failed: rpc error: code = 2 desc = failed to start sandbox container for pod \"router-1-fmvnv\": Error response from daemon: {\"message\":\"driver failed programming external connectivity on endpoint k8s_POD_router-1-fmvnv_default_6734f809-b99b-11e7-9b1d-3a4633f0fe38_23 (dc57db8d5856b460dd0b7ba84d320f5e24f46e4577e1d30288c28c086986237a): Error starting userland proxy: Bind for unexpected error (Failure EADDRINUSE)\"}"

Looks like either there is a pod or a process on your machine using port 80 and it's not letting the router bind to that port.

Jan Hellar

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]