Burak,
Your config looks good. If you turn on debug inrecords.config with a tag of “parent_select”, we can see what’s going on. By default, go_direct in parent.config is set to ‘true’ so, if there is a problem, connecting to your parent, the transaction will go direct to the origin. Verify that you are able to connect to the parent listed in parent.config. You can also set parent_direct=false. It will then not go to the origin directly but, if there is a problem connecting to the parent, you’ll get a 502. If you get a chance, send along your debug logs and I’ll have a look. *proxy.config.diags.debug.enabled INT 1* *proxy.config.diags.debug.tags STRING “http*|parent_select”* *[email protected] <[email protected]>* On Mon, Dec 25, 2017 at 11:23 AM, John Rushford <[email protected]> wrote: > No, it does not ignore remap.config. Try turning on debug with > “parent_select” and let’s see the logs. Your config looks good and should > be working > > Sent from my iPad > > On Dec 25, 2017, at 8:23 AM, Burak Sarp <[email protected]> wrote: > > Yes, it is enabled. > > Is ats ignored remap.config while parent is exist? > > > Sent from Yahoo Mail for iPhone > <https://overview.mail.yahoo.com/?.src=iOS> > > On Monday, December 25, 2017, 5:14 PM, John Rushford <[email protected]> > wrote: > > Is proxy.config.http.parent_proxy_routing_enable set to 1 in your > records.config? > > Sent from my iPad > > On Dec 25, 2017, at 6:31 AM, Burak Sarp <[email protected]> wrote: > > Firstly thanks for advice, > > we are trying to use parent.config, but we have problems on it. > when trafficserver is up, it is direct going to parent origin server, I > always see parent hit ats' access log while origin server is up on > remap.config > > our parent.config is > > dest_ip=10.31.25.5 parent="10.31.25.6:80" parent_is_proxy=false > round_robin=true parent_retry=unavailable_server_retry > unavailable_server_retry_responses=500,502,503 > > our remap.config > > map http://10.31.24.4/ http://10.31.25.5/ > > On Saturday, December 23, 2017, 7:52:34 PM GMT+3, John Rushford < > [email protected]> wrote: > > > We use parent.config to provide redundancy and load balance over origins. > See here for info on configuring parent.config. > > https://docs.trafficserver.apache.org/en/latest/admin- > guide/files/parent.config.en.html?highlight=parent% > 20config#std:configfile-parent.config > > On Dec 23, 2017, at 9:28 AM, Miles Libbey <[email protected]> wrote: > > On Sat, Dec 23, 2017 at 8:16 AM, Alan Carroll <[email protected]> > wrote: > > You can also use DNS round robin along with setting the server retries to a > non-zero value. > > > Will that "save" the first request to the dead origin? (or would the > error make its way back to the user?) > > On Sat, Dec 23, 2017 at 10:07 AM, Leif Hedstrom <[email protected]> wrote: > > > Yeh you can do this with parent.config or possibly the escalate plugin. > > > The escalate plugin works on missing objects, not dead servers. For > instance, perhaps origin1 periodically gets its data from > masterorigin, but, sometimes fails. The escalate plugin would have you > go to masterorigin when origin1 said it didn't have the content. > > I’d favor the former if possible, it has a new feature to go to an > alternative parent/origin on specified errors, as well as load balancing > etc. > > — Leif > > On Dec 23, 2017, at 5:51 AM, Burak Sarp <[email protected]> wrote: > > Hi all, > > Is there any way to cover origin server failover cases on ATS ? > > I mean if origin server is down, ATS will try another origin server.. > > Thanks, > Sarp > > > > > -- John Rushford [email protected]
