Closed
Bug 765828
Opened 13 years ago
Closed 13 years ago
basket.mozilla.com throwing "SAXReaderNotAvailable: No parsers found"
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlong, Assigned: nmaul)
Details
I'm getting tons of error emails from basket.mozilla.com now:
File "/data/www/basket.mozilla.org/basket/vendor/packages/suds/suds/bindings/binding.py", line 145, in get_reply
replyroot = sax.parse(string=reply)
File "/data/www/basket.mozilla.org/basket/vendor/packages/suds/suds/sax/parser.py", line 127, in parse
sax, handler = self.saxparser()
File "/data/www/basket.mozilla.org/basket/vendor/packages/suds/suds/sax/parser.py", line 111, in saxparser
p = make_parser()
File "/usr/lib64/python2.6/xml/sax/__init__.py", line 93, in make_parser
raise SAXReaderNotAvailable("No parsers found", None)
SAXReaderNotAvailable: No parsers found
What has changed?
| Reporter | ||
Updated•13 years ago
|
Severity: normal → blocker
Updated•13 years ago
|
Assignee: server-ops → afernandez
| Reporter | ||
Comment 1•13 years ago
|
||
jakem is helping look into this in #webdev as well
| Reporter | ||
Comment 2•13 years ago
|
||
This looks to be fixed now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•13 years ago
|
||
Puppet rolled out an update to python and python-libs today. This broke a number of sites (but not basket) in odd ways, until Apache was restarted. That restart appears to be what broke basket (based on timing information from jlongster).
We have rolled back the python update to the genericrhel6 cluster, and pinned it there until a better solution can be found.
| Assignee | ||
Updated•13 years ago
|
Assignee: afernandez → nmaul
Severity: blocker → normal
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•7 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
•