The only thing different from all my other openshift router installs is that I installed Openshift with ansible and I had to change the default network CIDR. Since I needed to access openshift from a computer on a network with an ip in the 10.0.0.0/16 range. I ended up using something like 192.168.1.0/19.
On Thu, Mar 3, 2016 at 12:10 AM, Dean Peterson <[email protected]> wrote: > I ran that "oc env dc router RELOAD_INTERVAL=5s" but I still get the 503 > error. Do I need to restart anything? > > On Wed, Mar 2, 2016 at 11:47 PM, Ram Ranganathan <[email protected]> > wrote: > >> Dean, we did have a recent change to coalesce router reloads (default is >> 0s) and it looks like with that default we are more aggressive with the >> reloads which could be causing this problem. >> >> Could you please try setting an environment variable ala: >> oc env dc router RELOAD_INTERVAL=5s >> # 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 name. >> >> and see if that helps. >> >> >> On Wed, Mar 2, 2016 at 6:21 PM, Dean Peterson <[email protected]> >> 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 in all >>> namespaces" >>> >>> On Wed, Mar 2, 2016 at 7:39 PM, Dean Peterson <[email protected]> >>> wrote: >>> >>>> All it says is: " Router is including routes in all namespaces" That's >>>> it. >>>> >>>> On Wed, Mar 2, 2016 at 7:38 PM, Clayton Coleman <[email protected]> >>>> wrote: >>>> >>>>> What do the router logs say? >>>>> >>>>> On Mar 2, 2016, at 7:43 PM, Dean Peterson <[email protected]> >>>>> wrote: >>>>> >>>>> This is as close to having openshift origin set up perfectly as I have >>>>> gotten. My builds 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 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 Peterson <[email protected] >>>>> > wrote: >>>>> >>>>>> I have a number of happy pods. They are all running normally. >>>>>> >>>>>> On Wed, Mar 2, 2016 at 6:28 PM, Mohamed Lrhazi < >>>>>> [email protected]> 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, 2016 at 7:03 PM, Dean Peterson < >>>>>>> [email protected]> 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 had this problem on previous versions. I installed >>>>>>>> openshift >>>>>>>> origin 1.1.3 with ansible; everything seems to be running smoothly like >>>>>>>> before but I just get 503 service unavailable errors trying to visit >>>>>>>> any >>>>>>>> route. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> users mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> _______________________________________________ >>>>> users mailing list >>>>> [email protected] >>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> >> >> -- >> Ram// >> main(O,s){s=--O;10<putchar(3^O?97-(15&7183>>4*s)*(O++?-1:1):10)&&\ >> main(++O,s++);} >> > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
