Closed
Bug 568491
Opened 14 years ago
Closed 14 years ago
[amo] Lost connection/can't connect to MySQL server
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbalogh, Unassigned)
Details
Lots of these errors after the move from phx, still happening this morning: OperationalError: (2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 104") OperationalError: (2003, "Can't connect to MySQL server on '10.2.70.20' (110)")
Comment 1•14 years ago
|
||
I suspect the errors were just slow coming in, but they all happened last night during the move. We saw the same thing when it went to phx.
Comment 2•14 years ago
|
||
I'm going to wrap this into the issues we saw with the Cisco ACE load balancer. We're not using it for amo db connections now. Calling fixed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 3•14 years ago
|
||
What did we switch to? I thought we were using zeus.
Comment 4•14 years ago
|
||
the db connections were going through the Cisco ACE. Now they're going through the Netscaler. Web hits are through Zeus.
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•