[mirror-admin] report_mirror problem - connection refused

Matt Domsch matt at domsch.com
Sat Apr 24 23:38:58 EDT 2010


On Wed, Apr 21, 2010 at 9:31 AM, Mike Iglesias <iglesias at uci.edu> wrote:
> On 04/20/2010 05:36 PM, Chris Adams wrote:
>> I'm getting an error when I run report_mirror: "Error checking in:
>> Connection refused.  Please try again later."
>
> I'm seeing this too.  It started sometime between 9:30am and 1:00pm PDT
> yesterday (4/20).

I've made a couple changes tonight to try to prevent this from happening.

1) increase the number of listening MirrorManager app instances, from
2 to 4, on each of the app servers.  This should allow more
simultaneous HTTP requests.  The report_mirror upload can take a
while, which would tie up one of the request slots.  We made a similar
change yesterday for the mirrorlists.

2) a better URL for the haproxy that fronts admin.fp.o/mirrormanager,
to ensure that the MM app itself is running and capable of talking to
the database, and not just apache able to serve up a static file.
This should catch the app server instances if they lose their
connection to the database somehow.

I'm hoping this will address the problems.  If you still see problems,
please let us know.

Thanks,
Matt

--



More information about the Mirror-admin mailing list