the
following error:
*503 Service Unavailable No server is available to handle this request.*
I have checked the logs on neutron_lbaas_agent and the openshift router
pods but I could not drill down as to why this is happening.
Both HTTP and HTTPS listeners have the same configuration, only the ports
I did an advanced install of OpenShift Origins. When I try and test my install
with the Jenkins-Ephemeral project it installs and I see the service listed. I
can click on the link and it brings me to a 503 service unavailable webpage.
Underneath the service hyperlink it says "there a
gt;>>>>>> On Wed, Mar 2, 2016 at 7:38 PM, Clayton Coleman <
>>>>>>>>>> ccole...@redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> What do the router logs say?
>>>>>>>>
t;>>>>>>> those permissions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On the host, running :
>>>>>>>>>>>>> $ oadm policy who-can get endpoints
>>
t;>
>>>>>>>>>>>> On Wed, Mar 2, 2016 at 11:56 PM, Dean Peterson <
>>>>>>>>>>>> peterson.d...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Ram//
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>&g
>>>>>>>>>>>>>
>>>>>>>>>>>>> The token info from inside the router container
>>>>>>>>>>>>> (/var/run/secrets/kubernetes.io/serviceaccount/token) seems
>
t;>>>>>>>>>>
>>>>>>>>>>>> Ram//
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Mar 2, 2016 at 11:56 PM, Dea
gt;>>>>> are also running on namespace default?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> El 3 mar 2016, a las 7:58, Dean Peterson <
>>>>>>>>>>>
>>>>>>>> - system:serviceaccount:default:router
>>>>>>>>>>>> - system:serviceaccount:default:registry
>>>>>>>>>>>>
>>>>>>>>>>>> router has always been a privileged user ser
t;>>>>>>>> route to. Most likely its due to the router service account has no
>>>>>>>>>>>> permissions to get the routes/endpoints info from etcd.
>>>>>>>>>>>> Check that the router service account (r
>>>>>>>>>>>> route to. Most likely its due to the router service account has no
>>>>>>>>>>>> permissions to get the routes/endpoints info from etcd.
>>>>>>>>>>>> Check that the router ser
lic gist from the output:
>>>>>>>>>>>> https://gist.github.com/deanpeterson/76aa9abf2c7fa182b56c
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Mar 3, 2016 at 12:35 AM, Ram Ranganathan <
&g
onf/haproxy.config# router-pod-name as shown
>>>>>>>>>>> in oc
>>>>>>>>>>> get pods
>>>>>>>>>>>
>>>>>>>>>>> Ram//
>>>>>>>>>>>
>
;>> Can you check that your haproxy.config file is correct (has the
>>>>>>>>>>>> correct backends and servers).
>>>>>>>>>>>> Either nsenter into your router docker container and cat the
>>>>&g
n.d...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I ran that "oc env dc router RELOAD_INTERVAL=5s" but I still
>>>>>>>>>>> get the 503 error. Do I need to restart anything?
>>>>>
are more
>>>>>>>>>>> aggressive
>>>>>>>>>>> with the reloads which could be causing this problem.
>>>>>>>>>>>
>>>>>>>>>>> Could you please try setting an environme
# or even 2s or 3s - that's reload interval in seconds
>>>>>>>>>> btw
>>>>>>>>>># if you have a custom deployment config then replace the
>>>>>>>>>> dc name router to that deployment config nam
> wrote:
>>>>>>>>>
>>>>>>>>>> Is there another place I can look to track down the problem? The
>>>>>>>>>> router logs don't say much, just: " Router is including routes
>>>>>&
;
>>>>>>>>>>
>>>>>>>>>> On Wed, Mar 2, 2016 at 7:39 PM, Dean Peterson <
>>>>>>>>>> peterson.d...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> All it say
ding routes in
>>>>>>>>> all namespaces"
>>>>>>>>>
>>>>>>>>> On Wed, Mar 2, 2016 at 7:39 PM, Dean Peterson <
>>>>>>>>> peterson.d...@gmail.com> wrote:
>>>&g
>>>>>>> ccole...@redhat.com> wrote:
>>>>>>>>>
>>>>>>>>>> What do the router logs say?
>>>>>>>>>>
>>>>>>>>>> On Mar 2, 2016, at 7:43 PM, Dean Peterson <
>>
. I
>>> thought I was finally going to have a smooth running Openshift; I just need
>>> to get past this last router issue. It makes little sense. I have set up
>>> a router many times before and never had this issue. I've had issues with
>>> other part
>>>>>>>>>>
>>>>>>>>>> This is as close to having openshift origin set up perfectly as I
>>>>>>>>>> have gotten. My builds work great, container deployments always
>>>>>>>>&g
;>> to get past this last router issue. It makes little sense. I have set up
>>> a router many times before and never had this issue. I've had issues with
>>> other parts of the system but never the router.
>>>
>>> On Wed, Mar 2, 2016 at 6:34 PM, Dean Pete
ccole...@redhat.com> wrote:
>>>>>>>>
>>>>>>>>> What do the router logs say?
>>>>>>>>>
>>>>>>>>> On Mar 2, 2016, at 7:43 PM, Dean Peterson
>>>>>>>>> wrote:
>
tem but never the router.
>>
>> On Wed, Mar 2, 2016 at 6:34 PM, Dean Peterson > <mailto:peterson.d...@gmail.com>> wrote:
>> I have a number of happy pods. They are all running normally.
>>
>> On Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi
>> mailto:mo
s work great, container deployments always work
>>>>>>>> now.
>>>>>>>> I thought I was finally going to have a smooth running Openshift; I
>>>>>>>> just
>>>>>>>> need to get past this last rou
g to have a smooth running Openshift; I just
>>>>>>> need to get past this last router issue. It makes little sense. I have
>>>>>>> set up a router many times before and never had this issue. I've had
>>>>>>> issues with other parts
>> now.
>>>>>>> I thought I was finally going to have a smooth running Openshift; I just
>>>>>>> need to get past this last router issue. It makes little sense. I have
>>>>>>> set up a router many times before and never had this issue.
; set up a router many times before and never had this issue. I've had
>>>>>> issues with other parts of the system but never the router.
>>>>>>
>>>>>> On Wed, Mar 2, 2016 at 6:34 PM, Dean Peterson <
>>>>>> peterson.d...@gmail
ittle sense. I have
>>>>>> set up a router many times before and never had this issue. I've had
>>>>>> issues with other parts of the system but never the router.
>>>>>>
>>>>>> On Wed, Mar 2, 2016 at 6:34 PM, Dea
the system but never the router.
>>>>>
>>>>> On Wed, Mar 2, 2016 at 6:34 PM, Dean Peterson >>>> > wrote:
>>>>>
>>>>>> I have a number of happy pods. They are all running normally.
>>>>>>
>>
:
>>>>>
>>>>>> I have a number of happy pods. They are all running normally.
>>>>>>
>>>>>> On Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi <
>>>>>> mohamed.lrh...@georgetown.edu> wrote:
>>>>>&
> wrote:
>>>>
>>>>> I have a number of happy pods. They are all running normally.
>>>>>
>>>>> On Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi <
>>>>> mohamed.lrh...@georgetown.edu> wrote:
>>>>>
>&
pods. They are all running normally.
>>>>
>>>> On Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi <
>>>> mohamed.lrh...@georgetown.edu> wrote:
>>>>
>>>>> Click on a pod and get to its log and events tabs see if they are
>>>
Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi <
>>> mohamed.lrh...@georgetown.edu> wrote:
>>>
>>>> Click on a pod and get to its log and events tabs see if they are
>>>> actually happy or stuck on something...
>>>>
>>>> On Wed, Mar 2,
gt;> wrote:
>>>
>>>> I have successfully started the ha proxy router. I have a pod running,
>>>> yet all my routes take me to a 503 service unavailable error page. I
>>>> updated my resolv.conf file to have my master ip as nameserver; I've never
&
d, Mar 2, 2016 at 7:03 PM, Dean Peterson
>> wrote:
>>
>>> I have successfully started the ha proxy router. I have a pod running,
>>> yet all my routes take me to a 503 service unavailable error page. I
>>> updated my resolv.conf file to have my master ip as namese
I have successfully started the ha proxy router. I have a pod running,
>>> yet all my routes take me to a 503 service unavailable error page. I
>>> updated my resolv.conf file to have my master ip as nameserver; I've never
>>> had this problem on previous versions. I ins
ar 2, 2016 at 7:03 PM, Dean Peterson
> wrote:
>
>> I have successfully started the ha proxy router. I have a pod running,
>> yet all my routes take me to a 503 service unavailable error page. I
>> updated my resolv.conf file to have my master ip as nameserver; I've nev
Click on a pod and get to its log and events tabs see if they are
actually happy or stuck on something...
On Wed, Mar 2, 2016 at 7:03 PM, Dean Peterson
wrote:
> I have successfully started the ha proxy router. I have a pod running,
> yet all my routes take me to a 503 service unava
I have successfully started the ha proxy router. I have a pod running, yet
all my routes take me to a 503 service unavailable error page. I updated
my resolv.conf file to have my master ip as nameserver; I've never had this
problem on previous versions. I installed openshift origin 1.1.3
43 matches
Mail list logo
