#294 Proxy Error on trying to update mirror
Closed: Fixed None Opened 16 years ago by kanarip.

Apparently some logic is causing private mirrors to fall off the map; and thus causing me to develop stuff over a very, very thin line. Anyway, trying to update the modules my local mirror is carrying, I get the following:

[jmeeuwen@elwood client]$ ./report_mirror -c report_mirror.conf
Traceback (most recent call last):
File "./report_mirror", line 278, in <module>
main()
File "./report_mirror", line 274, in main
print server.checkin(data)
File "/usr/lib/python2.5/xmlrpclib.py", line 1150, in call
return self.__send(self.__name, args)
File "/usr/lib/python2.5/xmlrpclib.py", line 1440, in __request
verbose=self.__verbose
File "/usr/lib/python2.5/xmlrpclib.py", line 1194, in request
headers
xmlrpclib.ProtocolError: <ProtocolError for admin.fedoraproject.org/mirrormanager/xmlrpc: 502 Proxy Error>


Has this started happening in the last couple weeks? If so, it is possible that it's related to ticket:281

K, this is a proxy issue and is related to communication between the application server and the database. Testing needs to be done to determine whether this is an openvpn problem, a mirrormanager problem or a network bandwidth problem.

I'm leaning towards it being not enough bandwidth or too much latency. This, unfortunately, leaves us with few options. We can try to make the apps more efficient but that will only go so far. We may just have to increase the proxy timeout.

I'm not actively working on this but want to leave it open.

I just did some updates last week that might have fixed this. Thought I'd check in, still going on?

Chris Adams (hiiway.net mirror admin) is reporting failures again over the last day or so.

I just converted this to wsgi. It should be smarter about not sending requests to heavily utilized servers that might timeout.

Also we're going to work to convert mirrormanager to wsgi which has had benefits for our other applications.

Hey, mirrormanager has been converted to wsgi for a while now - is this still going on?

Looks like it's been almost another year :-) I'm going to close this ticket out - please feel free to open a new one if you run into MM issues.

Login to comment on this ticket.

Metadata