Ubuntu mirror disable because of Bad response code: 503

Bug #252840 reported by tafrikya
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

My mirror server is removed from the list second time within a month with " Bad response code: 503 " output,
For sure My server is up and running, My internet connection is stable and my server was accessible in that time.

http://launchpadlibrarian.net/16364638/ubuntu.mirrors.adc.am-release-probe-logfile.txt

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Salgado, do you know what's going on here?

Changed in launchpad:
assignee: nobody → salgado
importance: Undecided → High
Revision history for this message
Guilherme Salgado (salgado) wrote :

That could've been a problem on our side, but the Ubuntu mirror admins have left a comment on the whiteboard[1] stating that they had problems when browsing the mirror.

Anyway, the check has been successful for quite some time now.

[1] https://launchpad.net/ubuntu/+mirror/ubuntu.mirrors.adc.am-release

Revision history for this message
tafrikya (mirrors-adc) wrote : Re: [Bug 252840] Re: Ubuntu mirror disable because of Bad response code: 503

OK, thanks for your support.

Tigran.

Guilherme Salgado wrote:
> That could've been a problem on our side, but the Ubuntu mirror admins
> have left a comment on the whiteboard[1] stating that they had problems
> when browsing the mirror.
>
> Anyway, the check has been successful for quite some time now.
>
> [1] https://launchpad.net/ubuntu/+mirror/ubuntu.mirrors.adc.am-release
>
>

Changed in launchpad:
assignee: salgado → nobody
importance: High → Undecided
status: New → Invalid
Revision history for this message
tafrikya (mirrors-adc) wrote : Re: [Bug 252840] Re: Ubuntu mirror disable because of Bad response code: 503

Hi,

My server is again removed from list , and again with Bad response code:
503 for this time I assure that SERVER was up and running for 100 % ,
could you please describe the meaning of 503 Error code ? could it be
long TTL issue ?

Tigran.

Mirrors@ADC wrote:
> OK, thanks for your support.
>
> Tigran.
>
> Guilherme Salgado wrote:
>> That could've been a problem on our side, but the Ubuntu mirror admins
>> have left a comment on the whiteboard[1] stating that they had problems
>> when browsing the mirror.
>>
>> Anyway, the check has been successful for quite some time now.
>>
>> [1] https://launchpad.net/ubuntu/+mirror/ubuntu.mirrors.adc.am-release
>>
>>
>

Revision history for this message
Guilherme Salgado (salgado) wrote : Re: [Bug 252840] Re: Ubuntu mirror disable because of Bad response code: 503

The 503 error code means "Service unavailable"[1]. Can you check your
logs to see if the requests were received? That may help you find out
why your server answered with a 503.

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Revision history for this message
tafrikya (mirrors-adc) wrote : Re: [Bug 252840] Re: Ubuntu mirror disable because of Bad response code: 503

could you please give me the source IP address ?

Tigran.

Guilherme Salgado wrote:
> The 503 error code means "Service unavailable"[1]. Can you check your
> logs to see if the requests were received? That may help you find out
> why your server answered with a 503.
>
>
> [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
>

Revision history for this message
Guilherme Salgado (salgado) wrote : Re: [Bug 252840] Re: Ubuntu mirror disable because of Bad response code: 503

Right now that's 91.189.90.174, but this may change in the future.

Revision history for this message
Fumihito YOSHIDA (hito) wrote :

I can confirm this problem(but example are not enough,changing to new.).

I'm administrator of ubuntu mirror server 'ubuntu-ashisuto.ubuntulinux.jp'.
It is registered at https://launchpad.net/ubuntu/+mirror/ubuntu-ashisuto.ubuntulinux.jp

I recieved automated failure notice from Launchpad that from below probers error at 2008-08-21
http://launchpadlibrarian.net/16964954/ubuntu-ashisuto.ubuntulinux.jp-probe-logfile.txt

But mirror server is fine, and *does not* logging any probers behavior.
So, mirror checker output 503 respond without any access. It looks like the proxy/http-client error.

In good case, mirror-prober that from 91.189.90.174(druzhnaya.canonical.com)., comming with HTTP: "HEAD /ubuntu//dists/<release-name>/<repo-type>/binary-<arch>/Packages.gz HTTP/1.0".
our mirror server logged below.
91.189.90.174 - - [08/May/2008:09:17:31 +0900] "HEAD /ubuntu//dists/intrepid/restricted/binary-i386/Packages.gz HTTP/1.0" 200 - "-" "-"

But, adove "Bad response code: 503" are not logging by ubuntu-ashisuto.ubuntulinux.jp.
I cannot found any other probers' log from httpd's logfiles(includinig errorlog file).

May be mirror-prober does not come at 2008-08-21..., but it logged bogus 503 error. (Of cource, I calculated the time difference of UTC=>JST)

Please check....

Changed in launchpad:
status: Invalid → New
Curtis Hovey (sinzui)
affects: launchpad-foundations → launchpad-registry
Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Jonathan Davies (jpds)
tags: added: mirror
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.