You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficcontrol.apache.org by Muhammed Olgun <mh...@gmail.com> on 2016/11/02 11:57:53 UTC

503 Service Unavailable on Traffic Router

Hi,

I'm trying to make a simple HTTP redirect from Traffic Router but I get 503.

There is no error log in Traffic Router's log file.
My TC version is 1.7
My content routing type is HTTP_LIVE_NATNL.
My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com

My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
*curl -Lvsk edge.origin.cdn1.tcmuolgun.com
<http://edge.origin.cdn1.tcmuolgun.com>* from the router VM, I get

> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: edge.origin.cdn1.tcmuolgun.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 12:45:51 GMT
< Server: ATS/5.3.2
< Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
< ETag: "9e-67-5404d5849c7b7"
< Accept-Ranges: bytes
< Content-Length: 103
< Content-Type: text/html; charset=UTF-8
< Age: 1
< Connection: keep-alive
< Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
pSeN:t cCMi p sS])

When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
<http://ccr.origin.cdn1.tcmuolgun.com> *outside from CDN I get

> GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> Host: ccr.origin.cdn1.tcmuolgun.com
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 961
< Date: Wed, 02 Nov 2016 12:45:20 GMT
< Connection: close
* HTTP/1.1 proxy connection set close!
< Proxy-Connection: close
<
* Closing connection 0

I don't know where I missed. Any help would be appreciated.

Thank you!
Muhammed

Re: 503 Service Unavailable on Traffic Router

Posted by Mark Torluemke <mt...@apache.org>.
If your Traffic Monitor doesn't show the caches as healthy, and you want to
isolate the Traffic Router component, you can change the status of the
cache(s) from REPORTED to ONLINE in Traffic Ops, and Snapshot the CRConfig
-- this will bypass the health protocol decision making.

Cheers,
Mark

On Wed, Nov 2, 2016 at 2:12 PM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:

> The CRConfig looks correct to me. One other thing that could cause the 503
> is if traffic-monitor doesn’t believe there are any caches that are
> available.
>
> Have you looked at the TM GUI to make sure that your edge caches are in
> the REPORTED state and are healthy?
>
> —Eric
>
> On Nov 2, 2016, at 3:30 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi David,
>
> Yes, I did and  to make it sure I ran ort script on edge server.
>
> [root@edge ort]# sudo ./traffic_ops_ort.pl syncds warn
> https://ops.tcmuolgun.com admin:tcmuolgun
> Wed Nov  2 21:30:04 EET 2016
> WARN Sleeping for 60 seconds: ..............................
> ..............................
> ERROR In syncds mode, but no syncds update needs to be applied. I'm outta
> here.
>
>
> 2 Kas 2016 Çar, 21:20 tarihinde, David Neuman <da...@gmail.com>
> şunu yazdı:
>
>> did you queue updates and the snapshot CrConfig after you assigned the
>> deliveryservice to the server?
>>
>> On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com>
>> wrote:
>>
>> Hi Dave,
>>
>> It was unassigned but I've just assigned it to the edge server.
>> Unfortunately still 503.
>>
>> 2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu
>> yazdı:
>>
>> Is your deliveryservice assigned to any caches?
>>
>> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
>> wrote:
>>
>> Hi Eric,
>>
>> Here is the snippet.
>>
>> https://paste.apache.org/X1q9
>>
>> Thank you!
>> Muhammed
>>
>> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> şunu yazdı:
>>
>> Could you please provide your cr-config file from your Traffic Router?
>> The file is located in /opt/traffic_router/db/cr-config.json. The most
>> relevant section is the one titled “deliveryServices” if you’d just like to
>> provide a snippet.
>>
>> —Eric
>>
>> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>>
>> Hi,
>>
>> Here is the access.log including with "tr" prefix.
>>
>> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
>> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>>
>> rurl is redirect url from my understanding and it looks like empty.
>>
>> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
>> HTTP routing type. I still get 503.
>>
>> Thank you!
>> Muhammed
>>
>>
>> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
>> şunu yazdı:
>>
>> Did you try "tr" instead of "ccr" in your URL? The default on traffic
>> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
>> old "ccr".
>>
>> I'm a bit confused about why "edge" works. Which Content Routing Type did
>> you select in your delivery service?
>>
>> Give it a try and see what comes back.
>>
>> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
>> Trevor_Ackerman@comcast.com> wrote:
>>
>> Hi Muhammed,
>>
>> There can be a variety of reasons why you get a 503.
>> Without going into a lot of detail, it sounds as if you are trying to
>> access a delivery service named ‘origin’ on can ‘cdn1’
>> Assuming that’s what you’re intending to do you’ll need to make sure
>> traffic router is finding caches for that delivery service and that all the
>> caches assigned to that delivery service are available.
>> I would check the access logs of the traffic router as they will provide
>> more detail about why you received a 503.
>> Note that receiving a 503 is intended if there’s a configuration problem
>> or TR cannot find any caches for the requested delivery service.
>>
>> Cheers,
>> Trevor Ackerman
>>
>> From: Muhammed Olgun <mh...@gmail.com>
>> Reply-To: "users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> Date: Wednesday, November 2, 2016 at 5:57 AM
>> To: "users@trafficcontrol.incubator.apache.org" <users@trafficcontrol.
>> incubator.apache.org>
>> Subject: 503 Service Unavailable on Traffic Router
>>
>> Hi,
>>
>> I'm trying to make a simple HTTP redirect from Traffic Router but I get
>> 503.
>>
>> There is no error log in Traffic Router's log file.
>> My TC version is 1.7
>> My content routing type is HTTP_LIVE_NATNL.
>> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>>
>> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
>> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
>> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>>
>> > GET / HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: edge.origin.cdn1.tcmuolgun.com
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>> < Date: Wed, 02 Nov 2016 12:45:51 GMT
>> < Server: ATS/5.3.2
>> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
>> < ETag: "9e-67-5404d5849c7b7"
>> < Accept-Ranges: bytes
>> < Content-Length: 103
>> < Content-Type: text/html; charset=UTF-8
>> < Age: 1
>> < Connection: keep-alive
>> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
>> pSeN:t cCMi p sS])
>>
>> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
>> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>>
>> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
>> > Host: ccr.origin.cdn1.tcmuolgun.com
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> >
>> < HTTP/1.1 503 Service Unavailable
>> < Server: Apache-Coyote/1.1
>> < Content-Type: text/html;charset=utf-8
>> < Content-Length: 961
>> < Date: Wed, 02 Nov 2016 12:45:20 GMT
>> < Connection: close
>> * HTTP/1.1 proxy connection set close!
>> < Proxy-Connection: close
>> <
>> * Closing connection 0
>>
>> I don't know where I missed. Any help would be appreciated.
>>
>> Thank you!
>> Muhammed
>>
>>
>>
>>
>>
>>
>

Re: 503 Service Unavailable on Traffic Router

Posted by Mark Torluemke <mt...@apache.org>.
Hi Muhammed -- If you'd like to dig further, see if you can find the
"allow_ip" and "allow_ip6" parameters (config file=astats.config) for your
edge profile in Traffic Ops. Those parameters should contain a comma
separated list of IPs that are allowed to access the astats endpoint.

Cheers,
Mark

On Wed, Nov 2, 2016 at 11:54 PM, Muhammed Olgun <mh...@gmail.com> wrote:

> Hi Eric,
>
> I didn't know that side effect. Actually my edge works but I have a
> problem with its reports. astats checks returns 404 from edge.
>
> I think it's more appropriate to create a new thread for this question.
> But I think that's the problem. I set EDGE status from REPORTED to ONLINE as
> Mark suggested and I got a cool output. So problem is solved.
>
> Thank you all!
> Muhammed
>
> 2 Kas 2016 Çar, 22:13 tarihinde, Eric Friedrich (efriedri) <
> efriedri@cisco.com> şunu yazdı:
>
>> The CRConfig looks correct to me. One other thing that could cause the
>> 503 is if traffic-monitor doesn’t believe there are any caches that are
>> available.
>>
>> Have you looked at the TM GUI to make sure that your edge caches are in
>> the REPORTED state and are healthy?
>>
>> —Eric
>>
>> On Nov 2, 2016, at 3:30 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>>
>> Hi David,
>>
>> Yes, I did and  to make it sure I ran ort script on edge server.
>>
>> [root@edge ort]# sudo ./traffic_ops_ort.pl syncds warn
>> https://ops.tcmuolgun.com admin:tcmuolgun
>> Wed Nov  2 21:30:04 EET 2016
>> WARN Sleeping for 60 seconds: ..............................
>> ..............................
>> ERROR In syncds mode, but no syncds update needs to be applied. I'm outta
>> here.
>>
>>
>> 2 Kas 2016 Çar, 21:20 tarihinde, David Neuman <da...@gmail.com>
>> şunu yazdı:
>>
>> did you queue updates and the snapshot CrConfig after you assigned the
>> deliveryservice to the server?
>>
>> On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com>
>> wrote:
>>
>> Hi Dave,
>>
>> It was unassigned but I've just assigned it to the edge server.
>> Unfortunately still 503.
>>
>> 2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu
>> yazdı:
>>
>> Is your deliveryservice assigned to any caches?
>>
>> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
>> wrote:
>>
>> Hi Eric,
>>
>> Here is the snippet.
>>
>> https://paste.apache.org/X1q9
>>
>> Thank you!
>> Muhammed
>>
>> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> şunu yazdı:
>>
>> Could you please provide your cr-config file from your Traffic Router?
>> The file is located in /opt/traffic_router/db/cr-config.json. The most
>> relevant section is the one titled “deliveryServices” if you’d just like to
>> provide a snippet.
>>
>> —Eric
>>
>> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>>
>> Hi,
>>
>> Here is the access.log including with "tr" prefix.
>>
>> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
>> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>>
>> rurl is redirect url from my understanding and it looks like empty.
>>
>> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
>> HTTP routing type. I still get 503.
>>
>> Thank you!
>> Muhammed
>>
>>
>> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
>> şunu yazdı:
>>
>> Did you try "tr" instead of "ccr" in your URL? The default on traffic
>> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
>> old "ccr".
>>
>> I'm a bit confused about why "edge" works. Which Content Routing Type did
>> you select in your delivery service?
>>
>> Give it a try and see what comes back.
>>
>> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
>> Trevor_Ackerman@comcast.com> wrote:
>>
>> Hi Muhammed,
>>
>> There can be a variety of reasons why you get a 503.
>> Without going into a lot of detail, it sounds as if you are trying to
>> access a delivery service named ‘origin’ on can ‘cdn1’
>> Assuming that’s what you’re intending to do you’ll need to make sure
>> traffic router is finding caches for that delivery service and that all the
>> caches assigned to that delivery service are available.
>> I would check the access logs of the traffic router as they will provide
>> more detail about why you received a 503.
>> Note that receiving a 503 is intended if there’s a configuration problem
>> or TR cannot find any caches for the requested delivery service.
>>
>> Cheers,
>> Trevor Ackerman
>>
>> From: Muhammed Olgun <mh...@gmail.com>
>> Reply-To: "users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> Date: Wednesday, November 2, 2016 at 5:57 AM
>> To: "users@trafficcontrol.incubator.apache.org" <users@trafficcontrol.
>> incubator.apache.org>
>> Subject: 503 Service Unavailable on Traffic Router
>>
>> Hi,
>>
>> I'm trying to make a simple HTTP redirect from Traffic Router but I get
>> 503.
>>
>> There is no error log in Traffic Router's log file.
>> My TC version is 1.7
>> My content routing type is HTTP_LIVE_NATNL.
>> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>>
>> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
>> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
>> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>>
>> > GET / HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: edge.origin.cdn1.tcmuolgun.com
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>> < Date: Wed, 02 Nov 2016 12:45:51 GMT
>> < Server: ATS/5.3.2
>> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
>> < ETag: "9e-67-5404d5849c7b7"
>> < Accept-Ranges: bytes
>> < Content-Length: 103
>> < Content-Type: text/html; charset=UTF-8
>> < Age: 1
>> < Connection: keep-alive
>> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
>> pSeN:t cCMi p sS])
>>
>> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
>> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>>
>> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
>> > Host: ccr.origin.cdn1.tcmuolgun.com
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> >
>> < HTTP/1.1 503 Service Unavailable
>> < Server: Apache-Coyote/1.1
>> < Content-Type: text/html;charset=utf-8
>> < Content-Length: 961
>> < Date: Wed, 02 Nov 2016 12:45:20 GMT
>> < Connection: close
>> * HTTP/1.1 proxy connection set close!
>> < Proxy-Connection: close
>> <
>> * Closing connection 0
>>
>> I don't know where I missed. Any help would be appreciated.
>>
>> Thank you!
>> Muhammed
>>
>>
>>
>>
>>
>>
>>

Re: 503 Service Unavailable on Traffic Router

Posted by Muhammed Olgun <mh...@gmail.com>.
Hi Eric,

I didn't know that side effect. Actually my edge works but I have a problem
with its reports. astats checks returns 404 from edge.

I think it's more appropriate to create a new thread for this question. But
I think that's the problem. I set EDGE status from REPORTED to ONLINE as
Mark suggested and I got a cool output. So problem is solved.

Thank you all!
Muhammed

2 Kas 2016 Çar, 22:13 tarihinde, Eric Friedrich (efriedri) <
efriedri@cisco.com> şunu yazdı:

> The CRConfig looks correct to me. One other thing that could cause the 503
> is if traffic-monitor doesn’t believe there are any caches that are
> available.
>
> Have you looked at the TM GUI to make sure that your edge caches are in
> the REPORTED state and are healthy?
>
> —Eric
>
> On Nov 2, 2016, at 3:30 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi David,
>
> Yes, I did and  to make it sure I ran ort script on edge server.
>
> [root@edge ort]# sudo ./traffic_ops_ort.pl syncds warn
> https://ops.tcmuolgun.com admin:tcmuolgun
> Wed Nov  2 21:30:04 EET 2016
> WARN Sleeping for 60 seconds:
> ............................................................
> ERROR In syncds mode, but no syncds update needs to be applied. I'm outta
> here.
>
>
> 2 Kas 2016 Çar, 21:20 tarihinde, David Neuman <da...@gmail.com>
> şunu yazdı:
>
> did you queue updates and the snapshot CrConfig after you assigned the
> deliveryservice to the server?
>
> On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi Dave,
>
> It was unassigned but I've just assigned it to the edge server.
> Unfortunately still 503.
>
> 2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu
> yazdı:
>
> Is your deliveryservice assigned to any caches?
>
> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
> wrote:
>
> Hi Eric,
>
> Here is the snippet.
>
> https://paste.apache.org/X1q9
>
> Thank you!
> Muhammed
>
> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
> efriedri@cisco.com> şunu yazdı:
>
> Could you please provide your cr-config file from your Traffic Router? The
> file is located in /opt/traffic_router/db/cr-config.json. The most relevant
> section is the one titled “deliveryServices” if you’d just like to provide
> a snippet.
>
> —Eric
>
> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi,
>
> Here is the access.log including with "tr" prefix.
>
> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="
> http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="
> http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>
> rurl is redirect url from my understanding and it looks like empty.
>
> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
> HTTP routing type. I still get 503.
>
> Thank you!
> Muhammed
>
>
> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
> şunu yazdı:
>
> Did you try "tr" instead of "ccr" in your URL? The default on traffic
> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
> old "ccr".
>
> I'm a bit confused about why "edge" works. Which Content Routing Type did
> you select in your delivery service?
>
> Give it a try and see what comes back.
>
> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
> Trevor_Ackerman@comcast.com> wrote:
>
> Hi Muhammed,
>
> There can be a variety of reasons why you get a 503.
> Without going into a lot of detail, it sounds as if you are trying to
> access a delivery service named ‘origin’ on can ‘cdn1’
> Assuming that’s what you’re intending to do you’ll need to make sure
> traffic router is finding caches for that delivery service and that all the
> caches assigned to that delivery service are available.
> I would check the access logs of the traffic router as they will provide
> more detail about why you received a 503.
> Note that receiving a 503 is intended if there’s a configuration problem
> or TR cannot find any caches for the requested delivery service.
>
> Cheers,
> Trevor Ackerman
>
> From: Muhammed Olgun <mh...@gmail.com>
> Reply-To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Date: Wednesday, November 2, 2016 at 5:57 AM
> To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Subject: 503 Service Unavailable on Traffic Router
>
> Hi,
>
> I'm trying to make a simple HTTP redirect from Traffic Router but I get
> 503.
>
> There is no error log in Traffic Router's log file.
> My TC version is 1.7
> My content routing type is HTTP_LIVE_NATNL.
> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>
> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>
> > GET / HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: edge.origin.cdn1.tcmuolgun.com
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Wed, 02 Nov 2016 12:45:51 GMT
> < Server: ATS/5.3.2
> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
> < ETag: "9e-67-5404d5849c7b7"
> < Accept-Ranges: bytes
> < Content-Length: 103
> < Content-Type: text/html; charset=UTF-8
> < Age: 1
> < Connection: keep-alive
> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
> pSeN:t cCMi p sS])
>
> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>
> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> > Host: ccr.origin.cdn1.tcmuolgun.com
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 503 Service Unavailable
> < Server: Apache-Coyote/1.1
> < Content-Type: text/html;charset=utf-8
> < Content-Length: 961
> < Date: Wed, 02 Nov 2016 12:45:20 GMT
> < Connection: close
> * HTTP/1.1 proxy connection set close!
> < Proxy-Connection: close
> <
> * Closing connection 0
>
> I don't know where I missed. Any help would be appreciated.
>
> Thank you!
> Muhammed
>
>
>
>
>
>
>

Re: 503 Service Unavailable on Traffic Router

Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
The CRConfig looks correct to me. One other thing that could cause the 503 is if traffic-monitor doesn’t believe there are any caches that are available.

Have you looked at the TM GUI to make sure that your edge caches are in the REPORTED state and are healthy?

—Eric

On Nov 2, 2016, at 3:30 PM, Muhammed Olgun <mh...@gmail.com>> wrote:

Hi David,

Yes, I did and  to make it sure I ran ort script on edge server.

[root@edge ort]# sudo ./traffic_ops_ort.pl<http://traffic_ops_ort.pl/> syncds warn https://ops.tcmuolgun.com<https://ops.tcmuolgun.com/> admin:tcmuolgun
Wed Nov  2 21:30:04 EET 2016
WARN Sleeping for 60 seconds: ............................................................
ERROR In syncds mode, but no syncds update needs to be applied. I'm outta here.


2 Kas 2016 Çar, 21:20 tarihinde, David Neuman <da...@gmail.com>> şunu yazdı:
did you queue updates and the snapshot CrConfig after you assigned the deliveryservice to the server?

On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com>> wrote:
Hi Dave,

It was unassigned but I've just assigned it to the edge server. Unfortunately still 503.

2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org>> şunu yazdı:
Is your deliveryservice assigned to any caches?

On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>> wrote:
Hi Eric,

Here is the snippet.

https://paste.apache.org/X1q9

Thank you!
Muhammed

2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <ef...@cisco.com>> şunu yazdı:
Could you please provide your cr-config file from your Traffic Router? The file is located in /opt/traffic_router/db/cr-config.json. The most relevant section is the one titled “deliveryServices” if you’d just like to provide a snippet.

—Eric

On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com>> wrote:

Hi,

Here is the access.log including with "tr" prefix.

1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"

rurl is redirect url from my understanding and it looks like empty.

My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only HTTP routing type. I still get 503.

Thank you!
Muhammed


2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>> şunu yazdı:
Did you try "tr" instead of "ccr" in your URL? The default on traffic Router is to use the "tr" prefix, but the Traffic OPs UI still reports the old "ccr".

I'm a bit confused about why "edge" works. Which Content Routing Type did you select in your delivery service?

Give it a try and see what comes back.

On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <Tr...@comcast.com>> wrote:
Hi Muhammed,

There can be a variety of reasons why you get a 503.
Without going into a lot of detail, it sounds as if you are trying to access a delivery service named ‘origin’ on can ‘cdn1’
Assuming that’s what you’re intending to do you’ll need to make sure traffic router is finding caches for that delivery service and that all the caches assigned to that delivery service are available.
I would check the access logs of the traffic router as they will provide more detail about why you received a 503.
Note that receiving a 503 is intended if there’s a configuration problem or TR cannot find any caches for the requested delivery service.

Cheers,
Trevor Ackerman

From: Muhammed Olgun <mh...@gmail.com>>
Reply-To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Date: Wednesday, November 2, 2016 at 5:57 AM
To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Subject: 503 Service Unavailable on Traffic Router

Hi,

I'm trying to make a simple HTTP redirect from Traffic Router but I get 503.

There is no error log in Traffic Router's log file.
My TC version is 1.7
My content routing type is HTTP_LIVE_NATNL.
My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>

My edge URL is http://edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/> and when I run
curl -Lvsk edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/> from the router VM, I get

> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0<http://3.14.0.0/> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/>
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 12:45:51 GMT
< Server: ATS/5.3.2
< Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
< ETag: "9e-67-5404d5849c7b7"
< Accept-Ranges: bytes
< Content-Length: 103
< Content-Type: text/html; charset=UTF-8
< Age: 1
< Connection: keep-alive
< Via: http/1.1 edge.tcmuolgun.com<http://edge.tcmuolgun.com/> (ApacheTrafficServer/5.3.2 [uScMsSf pSeN:t cCMi p sS])

When I run curl -Lvsk ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>outside from CDN I get

> GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> Host: ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 961
< Date: Wed, 02 Nov 2016 12:45:20 GMT
< Connection: close
* HTTP/1.1 proxy connection set close!
< Proxy-Connection: close
<
* Closing connection 0

I don't know where I missed. Any help would be appreciated.

Thank you!
Muhammed







Re: 503 Service Unavailable on Traffic Router

Posted by Muhammed Olgun <mh...@gmail.com>.
Hi David,

Yes, I did and  to make it sure I ran ort script on edge server.

[root@edge ort]# sudo ./traffic_ops_ort.pl syncds warn
https://ops.tcmuolgun.com admin:tcmuolgun
Wed Nov  2 21:30:04 EET 2016
WARN Sleeping for 60 seconds:
............................................................
ERROR In syncds mode, but no syncds update needs to be applied. I'm outta
here.


2 Kas 2016 Çar, 21:20 tarihinde, David Neuman <da...@gmail.com>
şunu yazdı:

> did you queue updates and the snapshot CrConfig after you assigned the
> deliveryservice to the server?
>
> On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi Dave,
>
> It was unassigned but I've just assigned it to the edge server.
> Unfortunately still 503.
>
> 2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu
> yazdı:
>
> Is your deliveryservice assigned to any caches?
>
> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
> wrote:
>
> Hi Eric,
>
> Here is the snippet.
>
> https://paste.apache.org/X1q9
>
> Thank you!
> Muhammed
>
> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
> efriedri@cisco.com> şunu yazdı:
>
> Could you please provide your cr-config file from your Traffic Router? The
> file is located in /opt/traffic_router/db/cr-config.json. The most relevant
> section is the one titled “deliveryServices” if you’d just like to provide
> a snippet.
>
> —Eric
>
> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi,
>
> Here is the access.log including with "tr" prefix.
>
> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="
> http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="
> http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>
> rurl is redirect url from my understanding and it looks like empty.
>
> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
> HTTP routing type. I still get 503.
>
> Thank you!
> Muhammed
>
>
> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
> şunu yazdı:
>
> Did you try "tr" instead of "ccr" in your URL? The default on traffic
> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
> old "ccr".
>
> I'm a bit confused about why "edge" works. Which Content Routing Type did
> you select in your delivery service?
>
> Give it a try and see what comes back.
>
> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
> Trevor_Ackerman@comcast.com> wrote:
>
> Hi Muhammed,
>
> There can be a variety of reasons why you get a 503.
> Without going into a lot of detail, it sounds as if you are trying to
> access a delivery service named ‘origin’ on can ‘cdn1’
> Assuming that’s what you’re intending to do you’ll need to make sure
> traffic router is finding caches for that delivery service and that all the
> caches assigned to that delivery service are available.
> I would check the access logs of the traffic router as they will provide
> more detail about why you received a 503.
> Note that receiving a 503 is intended if there’s a configuration problem
> or TR cannot find any caches for the requested delivery service.
>
> Cheers,
> Trevor Ackerman
>
> From: Muhammed Olgun <mh...@gmail.com>
> Reply-To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Date: Wednesday, November 2, 2016 at 5:57 AM
> To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Subject: 503 Service Unavailable on Traffic Router
>
> Hi,
>
> I'm trying to make a simple HTTP redirect from Traffic Router but I get
> 503.
>
> There is no error log in Traffic Router's log file.
> My TC version is 1.7
> My content routing type is HTTP_LIVE_NATNL.
> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>
> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>
> > GET / HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: edge.origin.cdn1.tcmuolgun.com
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Wed, 02 Nov 2016 12:45:51 GMT
> < Server: ATS/5.3.2
> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
> < ETag: "9e-67-5404d5849c7b7"
> < Accept-Ranges: bytes
> < Content-Length: 103
> < Content-Type: text/html; charset=UTF-8
> < Age: 1
> < Connection: keep-alive
> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
> pSeN:t cCMi p sS])
>
> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>
> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> > Host: ccr.origin.cdn1.tcmuolgun.com
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 503 Service Unavailable
> < Server: Apache-Coyote/1.1
> < Content-Type: text/html;charset=utf-8
> < Content-Length: 961
> < Date: Wed, 02 Nov 2016 12:45:20 GMT
> < Connection: close
> * HTTP/1.1 proxy connection set close!
> < Proxy-Connection: close
> <
> * Closing connection 0
>
> I don't know where I missed. Any help would be appreciated.
>
> Thank you!
> Muhammed
>
>
>
>
>
>

Re: 503 Service Unavailable on Traffic Router

Posted by David Neuman <da...@gmail.com>.
did you queue updates and the snapshot CrConfig after you assigned the
deliveryservice to the server?

On Wed, Nov 2, 2016 at 1:18 PM, Muhammed Olgun <mh...@gmail.com> wrote:

> Hi Dave,
>
> It was unassigned but I've just assigned it to the edge server.
> Unfortunately still 503.
>
> 2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu
> yazdı:
>
>> Is your deliveryservice assigned to any caches?
>>
>> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
>> wrote:
>>
>> Hi Eric,
>>
>> Here is the snippet.
>>
>> https://paste.apache.org/X1q9
>>
>> Thank you!
>> Muhammed
>>
>> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> şunu yazdı:
>>
>> Could you please provide your cr-config file from your Traffic Router?
>> The file is located in /opt/traffic_router/db/cr-config.json. The most
>> relevant section is the one titled “deliveryServices” if you’d just like to
>> provide a snippet.
>>
>> —Eric
>>
>> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>>
>> Hi,
>>
>> Here is the access.log including with "tr" prefix.
>>
>> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
>> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>>
>> rurl is redirect url from my understanding and it looks like empty.
>>
>> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
>> HTTP routing type. I still get 503.
>>
>> Thank you!
>> Muhammed
>>
>>
>> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
>> şunu yazdı:
>>
>> Did you try "tr" instead of "ccr" in your URL? The default on traffic
>> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
>> old "ccr".
>>
>> I'm a bit confused about why "edge" works. Which Content Routing Type did
>> you select in your delivery service?
>>
>> Give it a try and see what comes back.
>>
>> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
>> Trevor_Ackerman@comcast.com> wrote:
>>
>> Hi Muhammed,
>>
>> There can be a variety of reasons why you get a 503.
>> Without going into a lot of detail, it sounds as if you are trying to
>> access a delivery service named ‘origin’ on can ‘cdn1’
>> Assuming that’s what you’re intending to do you’ll need to make sure
>> traffic router is finding caches for that delivery service and that all the
>> caches assigned to that delivery service are available.
>> I would check the access logs of the traffic router as they will provide
>> more detail about why you received a 503.
>> Note that receiving a 503 is intended if there’s a configuration problem
>> or TR cannot find any caches for the requested delivery service.
>>
>> Cheers,
>> Trevor Ackerman
>>
>> From: Muhammed Olgun <mh...@gmail.com>
>> Reply-To: "users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> Date: Wednesday, November 2, 2016 at 5:57 AM
>> To: "users@trafficcontrol.incubator.apache.org" <users@trafficcontrol.
>> incubator.apache.org>
>> Subject: 503 Service Unavailable on Traffic Router
>>
>> Hi,
>>
>> I'm trying to make a simple HTTP redirect from Traffic Router but I get
>> 503.
>>
>> There is no error log in Traffic Router's log file.
>> My TC version is 1.7
>> My content routing type is HTTP_LIVE_NATNL.
>> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>>
>> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
>> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
>> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>>
>> > GET / HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: edge.origin.cdn1.tcmuolgun.com
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>> < Date: Wed, 02 Nov 2016 12:45:51 GMT
>> < Server: ATS/5.3.2
>> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
>> < ETag: "9e-67-5404d5849c7b7"
>> < Accept-Ranges: bytes
>> < Content-Length: 103
>> < Content-Type: text/html; charset=UTF-8
>> < Age: 1
>> < Connection: keep-alive
>> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
>> pSeN:t cCMi p sS])
>>
>> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
>> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>>
>> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
>> > Host: ccr.origin.cdn1.tcmuolgun.com
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> >
>> < HTTP/1.1 503 Service Unavailable
>> < Server: Apache-Coyote/1.1
>> < Content-Type: text/html;charset=utf-8
>> < Content-Length: 961
>> < Date: Wed, 02 Nov 2016 12:45:20 GMT
>> < Connection: close
>> * HTTP/1.1 proxy connection set close!
>> < Proxy-Connection: close
>> <
>> * Closing connection 0
>>
>> I don't know where I missed. Any help would be appreciated.
>>
>> Thank you!
>> Muhammed
>>
>>
>>
>>
>>

Re: 503 Service Unavailable on Traffic Router

Posted by Muhammed Olgun <mh...@gmail.com>.
Hi Dave,

It was unassigned but I've just assigned it to the edge server.
Unfortunately still 503.

2 Kas 2016 Çar, 20:56 tarihinde, Dave Neuman <ne...@apache.org> şunu yazdı:

> Is your deliveryservice assigned to any caches?
>
> On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com>
> wrote:
>
> Hi Eric,
>
> Here is the snippet.
>
> https://paste.apache.org/X1q9
>
> Thank you!
> Muhammed
>
> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
> efriedri@cisco.com> şunu yazdı:
>
> Could you please provide your cr-config file from your Traffic Router? The
> file is located in /opt/traffic_router/db/cr-config.json. The most relevant
> section is the one titled “deliveryServices” if you’d just like to provide
> a snippet.
>
> —Eric
>
> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi,
>
> Here is the access.log including with "tr" prefix.
>
> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="
> http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="
> http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>
> rurl is redirect url from my understanding and it looks like empty.
>
> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
> HTTP routing type. I still get 503.
>
> Thank you!
> Muhammed
>
>
> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
> şunu yazdı:
>
> Did you try "tr" instead of "ccr" in your URL? The default on traffic
> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
> old "ccr".
>
> I'm a bit confused about why "edge" works. Which Content Routing Type did
> you select in your delivery service?
>
> Give it a try and see what comes back.
>
> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
> Trevor_Ackerman@comcast.com> wrote:
>
> Hi Muhammed,
>
> There can be a variety of reasons why you get a 503.
> Without going into a lot of detail, it sounds as if you are trying to
> access a delivery service named ‘origin’ on can ‘cdn1’
> Assuming that’s what you’re intending to do you’ll need to make sure
> traffic router is finding caches for that delivery service and that all the
> caches assigned to that delivery service are available.
> I would check the access logs of the traffic router as they will provide
> more detail about why you received a 503.
> Note that receiving a 503 is intended if there’s a configuration problem
> or TR cannot find any caches for the requested delivery service.
>
> Cheers,
> Trevor Ackerman
>
> From: Muhammed Olgun <mh...@gmail.com>
> Reply-To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Date: Wednesday, November 2, 2016 at 5:57 AM
> To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Subject: 503 Service Unavailable on Traffic Router
>
> Hi,
>
> I'm trying to make a simple HTTP redirect from Traffic Router but I get
> 503.
>
> There is no error log in Traffic Router's log file.
> My TC version is 1.7
> My content routing type is HTTP_LIVE_NATNL.
> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>
> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>
> > GET / HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: edge.origin.cdn1.tcmuolgun.com
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Wed, 02 Nov 2016 12:45:51 GMT
> < Server: ATS/5.3.2
> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
> < ETag: "9e-67-5404d5849c7b7"
> < Accept-Ranges: bytes
> < Content-Length: 103
> < Content-Type: text/html; charset=UTF-8
> < Age: 1
> < Connection: keep-alive
> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
> pSeN:t cCMi p sS])
>
> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>
> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> > Host: ccr.origin.cdn1.tcmuolgun.com
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 503 Service Unavailable
> < Server: Apache-Coyote/1.1
> < Content-Type: text/html;charset=utf-8
> < Content-Length: 961
> < Date: Wed, 02 Nov 2016 12:45:20 GMT
> < Connection: close
> * HTTP/1.1 proxy connection set close!
> < Proxy-Connection: close
> <
> * Closing connection 0
>
> I don't know where I missed. Any help would be appreciated.
>
> Thank you!
> Muhammed
>
>
>
>
>

Re: 503 Service Unavailable on Traffic Router

Posted by Dave Neuman <ne...@apache.org>.
Is your deliveryservice assigned to any caches?

On Wed, Nov 2, 2016 at 11:45 AM, Muhammed Olgun <mh...@gmail.com> wrote:

> Hi Eric,
>
> Here is the snippet.
>
> https://paste.apache.org/X1q9
>
> Thank you!
> Muhammed
>
> 2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
> efriedri@cisco.com> şunu yazdı:
>
>> Could you please provide your cr-config file from your Traffic Router?
>> The file is located in /opt/traffic_router/db/cr-config.json. The most
>> relevant section is the one titled “deliveryServices” if you’d just like to
>> provide a snippet.
>>
>> —Eric
>>
>> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>>
>> Hi,
>>
>> Here is the access.log including with "tr" prefix.
>>
>> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
>> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.
>> tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=-
>> rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>>
>> rurl is redirect url from my understanding and it looks like empty.
>>
>> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
>> HTTP routing type. I still get 503.
>>
>> Thank you!
>> Muhammed
>>
>>
>> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
>> şunu yazdı:
>>
>> Did you try "tr" instead of "ccr" in your URL? The default on traffic
>> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
>> old "ccr".
>>
>> I'm a bit confused about why "edge" works. Which Content Routing Type did
>> you select in your delivery service?
>>
>> Give it a try and see what comes back.
>>
>> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
>> Trevor_Ackerman@comcast.com> wrote:
>>
>> Hi Muhammed,
>>
>> There can be a variety of reasons why you get a 503.
>> Without going into a lot of detail, it sounds as if you are trying to
>> access a delivery service named ‘origin’ on can ‘cdn1’
>> Assuming that’s what you’re intending to do you’ll need to make sure
>> traffic router is finding caches for that delivery service and that all the
>> caches assigned to that delivery service are available.
>> I would check the access logs of the traffic router as they will provide
>> more detail about why you received a 503.
>> Note that receiving a 503 is intended if there’s a configuration problem
>> or TR cannot find any caches for the requested delivery service.
>>
>> Cheers,
>> Trevor Ackerman
>>
>> From: Muhammed Olgun <mh...@gmail.com>
>> Reply-To: "users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> Date: Wednesday, November 2, 2016 at 5:57 AM
>> To: "users@trafficcontrol.incubator.apache.org" <users@trafficcontrol.
>> incubator.apache.org>
>> Subject: 503 Service Unavailable on Traffic Router
>>
>> Hi,
>>
>> I'm trying to make a simple HTTP redirect from Traffic Router but I get
>> 503.
>>
>> There is no error log in Traffic Router's log file.
>> My TC version is 1.7
>> My content routing type is HTTP_LIVE_NATNL.
>> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>>
>> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
>> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
>> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>>
>> > GET / HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: edge.origin.cdn1.tcmuolgun.com
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>> < Date: Wed, 02 Nov 2016 12:45:51 GMT
>> < Server: ATS/5.3.2
>> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
>> < ETag: "9e-67-5404d5849c7b7"
>> < Accept-Ranges: bytes
>> < Content-Length: 103
>> < Content-Type: text/html; charset=UTF-8
>> < Age: 1
>> < Connection: keep-alive
>> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
>> pSeN:t cCMi p sS])
>>
>> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
>> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>>
>> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
>> > Host: ccr.origin.cdn1.tcmuolgun.com
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> > Proxy-Connection: Keep-Alive
>> >
>> < HTTP/1.1 503 Service Unavailable
>> < Server: Apache-Coyote/1.1
>> < Content-Type: text/html;charset=utf-8
>> < Content-Length: 961
>> < Date: Wed, 02 Nov 2016 12:45:20 GMT
>> < Connection: close
>> * HTTP/1.1 proxy connection set close!
>> < Proxy-Connection: close
>> <
>> * Closing connection 0
>>
>> I don't know where I missed. Any help would be appreciated.
>>
>> Thank you!
>> Muhammed
>>
>>
>>
>>

Re: 503 Service Unavailable on Traffic Router

Posted by Muhammed Olgun <mh...@gmail.com>.
Hi Eric,

Here is the snippet.

https://paste.apache.org/X1q9

Thank you!
Muhammed

2 Kas 2016 Çar, 19:37 tarihinde, Eric Friedrich (efriedri) <
efriedri@cisco.com> şunu yazdı:

> Could you please provide your cr-config file from your Traffic Router? The
> file is located in /opt/traffic_router/db/cr-config.json. The most relevant
> section is the one titled “deliveryServices” if you’d just like to provide
> a snippet.
>
> —Eric
>
> On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com> wrote:
>
> Hi,
>
> Here is the access.log including with "tr" prefix.
>
> 1478096725.820 qtype=HTTP chi=192.168.56.1 url="
> http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
> 1478110576.852 qtype=HTTP chi=192.168.56.1 url="
> http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
> rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"
>
> rurl is redirect url from my understanding and it looks like empty.
>
> My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only
> HTTP routing type. I still get 503.
>
> Thank you!
> Muhammed
>
>
> 2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
> şunu yazdı:
>
> Did you try "tr" instead of "ccr" in your URL? The default on traffic
> Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
> old "ccr".
>
> I'm a bit confused about why "edge" works. Which Content Routing Type did
> you select in your delivery service?
>
> Give it a try and see what comes back.
>
> On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
> Trevor_Ackerman@comcast.com> wrote:
>
> Hi Muhammed,
>
> There can be a variety of reasons why you get a 503.
> Without going into a lot of detail, it sounds as if you are trying to
> access a delivery service named ‘origin’ on can ‘cdn1’
> Assuming that’s what you’re intending to do you’ll need to make sure
> traffic router is finding caches for that delivery service and that all the
> caches assigned to that delivery service are available.
> I would check the access logs of the traffic router as they will provide
> more detail about why you received a 503.
> Note that receiving a 503 is intended if there’s a configuration problem
> or TR cannot find any caches for the requested delivery service.
>
> Cheers,
> Trevor Ackerman
>
> From: Muhammed Olgun <mh...@gmail.com>
> Reply-To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Date: Wednesday, November 2, 2016 at 5:57 AM
> To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Subject: 503 Service Unavailable on Traffic Router
>
> Hi,
>
> I'm trying to make a simple HTTP redirect from Traffic Router but I get
> 503.
>
> There is no error log in Traffic Router's log file.
> My TC version is 1.7
> My content routing type is HTTP_LIVE_NATNL.
> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>
> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
> <http://edge.origin.cdn1.tcmuolgun.com/>* from the router VM, I get
>
> > GET / HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: edge.origin.cdn1.tcmuolgun.com
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Wed, 02 Nov 2016 12:45:51 GMT
> < Server: ATS/5.3.2
> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
> < ETag: "9e-67-5404d5849c7b7"
> < Accept-Ranges: bytes
> < Content-Length: 103
> < Content-Type: text/html; charset=UTF-8
> < Age: 1
> < Connection: keep-alive
> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
> pSeN:t cCMi p sS])
>
> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
> <http://ccr.origin.cdn1.tcmuolgun.com/>*outside from CDN I get
>
> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> > Host: ccr.origin.cdn1.tcmuolgun.com
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 503 Service Unavailable
> < Server: Apache-Coyote/1.1
> < Content-Type: text/html;charset=utf-8
> < Content-Length: 961
> < Date: Wed, 02 Nov 2016 12:45:20 GMT
> < Connection: close
> * HTTP/1.1 proxy connection set close!
> < Proxy-Connection: close
> <
> * Closing connection 0
>
> I don't know where I missed. Any help would be appreciated.
>
> Thank you!
> Muhammed
>
>
>
>

Re: 503 Service Unavailable on Traffic Router

Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
Could you please provide your cr-config file from your Traffic Router? The file is located in /opt/traffic_router/db/cr-config.json. The most relevant section is the one titled “deliveryServices” if you’d just like to provide a snippet.

—Eric

On Nov 2, 2016, at 1:28 PM, Muhammed Olgun <mh...@gmail.com>> wrote:

Hi,

Here is the access.log including with "tr" prefix.

1478096725.820 qtype=HTTP chi=192.168.56.1 url="http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
1478110576.852 qtype=HTTP chi=192.168.56.1 url="http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"

rurl is redirect url from my understanding and it looks like empty.

My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only HTTP routing type. I still get 503.

Thank you!
Muhammed


2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>> şunu yazdı:
Did you try "tr" instead of "ccr" in your URL? The default on traffic Router is to use the "tr" prefix, but the Traffic OPs UI still reports the old "ccr".

I'm a bit confused about why "edge" works. Which Content Routing Type did you select in your delivery service?

Give it a try and see what comes back.

On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <Tr...@comcast.com>> wrote:
Hi Muhammed,

There can be a variety of reasons why you get a 503.
Without going into a lot of detail, it sounds as if you are trying to access a delivery service named ‘origin’ on can ‘cdn1’
Assuming that’s what you’re intending to do you’ll need to make sure traffic router is finding caches for that delivery service and that all the caches assigned to that delivery service are available.
I would check the access logs of the traffic router as they will provide more detail about why you received a 503.
Note that receiving a 503 is intended if there’s a configuration problem or TR cannot find any caches for the requested delivery service.

Cheers,
Trevor Ackerman

From: Muhammed Olgun <mh...@gmail.com>>
Reply-To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Date: Wednesday, November 2, 2016 at 5:57 AM
To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Subject: 503 Service Unavailable on Traffic Router

Hi,

I'm trying to make a simple HTTP redirect from Traffic Router but I get 503.

There is no error log in Traffic Router's log file.
My TC version is 1.7
My content routing type is HTTP_LIVE_NATNL.
My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>

My edge URL is http://edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/> and when I run
curl -Lvsk edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/> from the router VM, I get

> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0<http://3.14.0.0/> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com/>
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 12:45:51 GMT
< Server: ATS/5.3.2
< Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
< ETag: "9e-67-5404d5849c7b7"
< Accept-Ranges: bytes
< Content-Length: 103
< Content-Type: text/html; charset=UTF-8
< Age: 1
< Connection: keep-alive
< Via: http/1.1 edge.tcmuolgun.com<http://edge.tcmuolgun.com/> (ApacheTrafficServer/5.3.2 [uScMsSf pSeN:t cCMi p sS])

When I run curl -Lvsk ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>outside from CDN I get

> GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> Host: ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com/>
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 961
< Date: Wed, 02 Nov 2016 12:45:20 GMT
< Connection: close
* HTTP/1.1 proxy connection set close!
< Proxy-Connection: close
<
* Closing connection 0

I don't know where I missed. Any help would be appreciated.

Thank you!
Muhammed




Re: 503 Service Unavailable on Traffic Router

Posted by Muhammed Olgun <mh...@gmail.com>.
Hi,

Here is the access.log including with "tr" prefix.

1478096725.820 qtype=HTTP chi=192.168.56.1 url="
http://ccr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.265 rurl="-" rh="-"
1478110576.852 qtype=HTTP chi=192.168.56.1 url="
http://tr.origin.cdn1.tcmuolgun.com/" cqhm=GET cqhv=HTTP/1.1 rtype=MISS
rloc="-" rdtl=- rerr="-" rgb="-" pssc=503 ttms=0.377 rurl="-" rh="-"

rurl is redirect url from my understanding and it looks like empty.

My content routing type *was* HTTP_LIVE_NATNL. I've changed it to only HTTP
routing type. I still get 503.

Thank you!
Muhammed


2 Kas 2016 Çar, 18:51 tarihinde, Steve Malenfant <sm...@gmail.com>
şunu yazdı:

Did you try "tr" instead of "ccr" in your URL? The default on traffic
Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
old "ccr".

I'm a bit confused about why "edge" works. Which Content Routing Type did
you select in your delivery service?

Give it a try and see what comes back.

On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
Trevor_Ackerman@comcast.com> wrote:

Hi Muhammed,

There can be a variety of reasons why you get a 503.
Without going into a lot of detail, it sounds as if you are trying to
access a delivery service named ‘origin’ on can ‘cdn1’
Assuming that’s what you’re intending to do you’ll need to make sure
traffic router is finding caches for that delivery service and that all the
caches assigned to that delivery service are available.
I would check the access logs of the traffic router as they will provide
more detail about why you received a 503.
Note that receiving a 503 is intended if there’s a configuration problem or
TR cannot find any caches for the requested delivery service.

Cheers,
Trevor Ackerman

From: Muhammed Olgun <mh...@gmail.com>
Reply-To: "users@trafficcontrol.incubator.apache.org" <
users@trafficcontrol.incubator.apache.org>
Date: Wednesday, November 2, 2016 at 5:57 AM
To: "users@trafficcontrol.incubator.apache.org" <
users@trafficcontrol.incubator.apache.org>
Subject: 503 Service Unavailable on Traffic Router

Hi,

I'm trying to make a simple HTTP redirect from Traffic Router but I get 503.

There is no error log in Traffic Router's log file.
My TC version is 1.7
My content routing type is HTTP_LIVE_NATNL.
My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com

My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
*curl -Lvsk edge.origin.cdn1.tcmuolgun.com
<http://edge.origin.cdn1.tcmuolgun.com>* from the router VM, I get

> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: edge.origin.cdn1.tcmuolgun.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 12:45:51 GMT
< Server: ATS/5.3.2
< Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
< ETag: "9e-67-5404d5849c7b7"
< Accept-Ranges: bytes
< Content-Length: 103
< Content-Type: text/html; charset=UTF-8
< Age: 1
< Connection: keep-alive
< Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
pSeN:t cCMi p sS])

When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
<http://ccr.origin.cdn1.tcmuolgun.com>*outside from CDN I get

> GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> Host: ccr.origin.cdn1.tcmuolgun.com
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 961
< Date: Wed, 02 Nov 2016 12:45:20 GMT
< Connection: close
* HTTP/1.1 proxy connection set close!
< Proxy-Connection: close
<
* Closing connection 0

I don't know where I missed. Any help would be appreciated.

Thank you!
Muhammed

Re: 503 Service Unavailable on Traffic Router

Posted by Steve Malenfant <sm...@gmail.com>.
Did you try "tr" instead of "ccr" in your URL? The default on traffic
Router is to use the "tr" prefix, but the Traffic OPs UI still reports the
old "ccr".

I'm a bit confused about why "edge" works. Which Content Routing Type did
you select in your delivery service?

Give it a try and see what comes back.

On Wed, Nov 2, 2016 at 11:55 AM, Ackerman, Trevor (Contractor) <
Trevor_Ackerman@comcast.com> wrote:

> Hi Muhammed,
>
> There can be a variety of reasons why you get a 503.
> Without going into a lot of detail, it sounds as if you are trying to
> access a delivery service named ‘origin’ on can ‘cdn1’
> Assuming that’s what you’re intending to do you’ll need to make sure
> traffic router is finding caches for that delivery service and that all the
> caches assigned to that delivery service are available.
> I would check the access logs of the traffic router as they will provide
> more detail about why you received a 503.
> Note that receiving a 503 is intended if there’s a configuration problem
> or TR cannot find any caches for the requested delivery service.
>
> Cheers,
> Trevor Ackerman
>
> From: Muhammed Olgun <mh...@gmail.com>
> Reply-To: "users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> Date: Wednesday, November 2, 2016 at 5:57 AM
> To: "users@trafficcontrol.incubator.apache.org" <users@trafficcontrol.
> incubator.apache.org>
> Subject: 503 Service Unavailable on Traffic Router
>
> Hi,
>
> I'm trying to make a simple HTTP redirect from Traffic Router but I get
> 503.
>
> There is no error log in Traffic Router's log file.
> My TC version is 1.7
> My content routing type is HTTP_LIVE_NATNL.
> My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com
>
> My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
> *curl -Lvsk edge.origin.cdn1.tcmuolgun.com
> <http://edge.origin.cdn1.tcmuolgun.com>* from the router VM, I get
>
> > GET / HTTP/1.1
> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> > Host: edge.origin.cdn1.tcmuolgun.com
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Date: Wed, 02 Nov 2016 12:45:51 GMT
> < Server: ATS/5.3.2
> < Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
> < ETag: "9e-67-5404d5849c7b7"
> < Accept-Ranges: bytes
> < Content-Length: 103
> < Content-Type: text/html; charset=UTF-8
> < Age: 1
> < Connection: keep-alive
> < Via: http/1.1 edge.tcmuolgun.com (ApacheTrafficServer/5.3.2 [uScMsSf
> pSeN:t cCMi p sS])
>
> When I run *curl -Lvsk ccr.origin.cdn1.tcmuolgun.com
> <http://ccr.origin.cdn1.tcmuolgun.com>*outside from CDN I get
>
> > GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> > Host: ccr.origin.cdn1.tcmuolgun.com
> > User-Agent: curl/7.47.0
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 503 Service Unavailable
> < Server: Apache-Coyote/1.1
> < Content-Type: text/html;charset=utf-8
> < Content-Length: 961
> < Date: Wed, 02 Nov 2016 12:45:20 GMT
> < Connection: close
> * HTTP/1.1 proxy connection set close!
> < Proxy-Connection: close
> <
> * Closing connection 0
>
> I don't know where I missed. Any help would be appreciated.
>
> Thank you!
> Muhammed
>
>

Re: 503 Service Unavailable on Traffic Router

Posted by "Ackerman, Trevor (Contractor)" <Tr...@comcast.com>.
Hi Muhammed,

There can be a variety of reasons why you get a 503.
Without going into a lot of detail, it sounds as if you are trying to access a delivery service named 'origin' on can 'cdn1'
Assuming that's what you're intending to do you'll need to make sure traffic router is finding caches for that delivery service and that all the caches assigned to that delivery service are available.
I would check the access logs of the traffic router as they will provide more detail about why you received a 503.
Note that receiving a 503 is intended if there's a configuration problem or TR cannot find any caches for the requested delivery service.

Cheers,
Trevor Ackerman

From: Muhammed Olgun <mh...@gmail.com>>
Reply-To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Date: Wednesday, November 2, 2016 at 5:57 AM
To: "users@trafficcontrol.incubator.apache.org<ma...@trafficcontrol.incubator.apache.org>" <us...@trafficcontrol.incubator.apache.org>>
Subject: 503 Service Unavailable on Traffic Router

Hi,

I'm trying to make a simple HTTP redirect from Traffic Router but I get 503.

There is no error log in Traffic Router's log file.
My TC version is 1.7
My content routing type is HTTP_LIVE_NATNL.
My delivery URL is http://ccr.origin.cdn1.tcmuolgun.com

My edge URL is http://edge.origin.cdn1.tcmuolgun.com and when I run
curl -Lvsk edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com> from the router VM, I get

> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0<http://3.14.0.0> zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: edge.origin.cdn1.tcmuolgun.com<http://edge.origin.cdn1.tcmuolgun.com>
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 12:45:51 GMT
< Server: ATS/5.3.2
< Last-Modified: Wed, 02 Nov 2016 08:37:01 GMT
< ETag: "9e-67-5404d5849c7b7"
< Accept-Ranges: bytes
< Content-Length: 103
< Content-Type: text/html; charset=UTF-8
< Age: 1
< Connection: keep-alive
< Via: http/1.1 edge.tcmuolgun.com<http://edge.tcmuolgun.com> (ApacheTrafficServer/5.3.2 [uScMsSf pSeN:t cCMi p sS])

When I run curl -Lvsk ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com>outside from CDN I get

> GET http://ccr.origin.cdn1.tcmuolgun.com/ HTTP/1.1
> Host: ccr.origin.cdn1.tcmuolgun.com<http://ccr.origin.cdn1.tcmuolgun.com>
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 503 Service Unavailable
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 961
< Date: Wed, 02 Nov 2016 12:45:20 GMT
< Connection: close
* HTTP/1.1 proxy connection set close!
< Proxy-Connection: close
<
* Closing connection 0

I don't know where I missed. Any help would be appreciated.

Thank you!
Muhammed