Not handling administrative shutdown under Oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Gavin Panella | ||
Storm |
Fix Released
|
Critical
|
Gavin Panella |
Bug Description
On Oneiric I've been unable to run many tests. For example, when running "./bin/test lp.buildmaster.
psycopg2.
SSL connection has been closed unexpectedly
That's in the Librarian log. The test itself will then fail with something like:
UploadFailed: Server said: 500 Internal server error
I'm trying to paste the output, but gedit is having trouble with the file I dumped it into. And that reminds me: the Librarian log output on these failed test runs contains what look like blocks of null bytes, several kilobytes (but no particularly familiar number) at a time. The blocks seem to get longer with each successive test.
In "less," the chunks of librarian log look like: http://
I tried checking for running librarian instances and other twisted-based scripts with "ps -ef | grep twist" but none seem to be running. This is strange; I'm used to seeing at least a bunch of Librarian processes (both before and after I started having this problem).
Related branches
- Stuart Bishop (community): Disapprove
- Launchpad code reviewers: Pending requested
-
Diff: 56 lines (+18/-8)1 file modifiedlib/lp/services/database/__init__.py (+18/-8)
- Gavin Panella: Abstain
- Raphaël Badin: Approve (code)
- Stuart Bishop: Pending requested
-
Diff: 407 lines (+212/-32)9 files modifiedMANIFEST.in (+1/-1)
NEWS (+12/-1)
README (+11/-4)
setup.py (+4/-0)
storm/databases/postgres.py (+46/-15)
test (+2/-3)
tests/__init__.py (+9/-0)
tests/databases/postgres.py (+120/-1)
tests/tracer.py (+7/-7)
- Gavin Panella (community): Approve
-
Diff: 36 lines (+2/-6)2 files modifiedlib/canonical/librarian/tests/test_db_outage.py (+0/-4)
versions.cfg (+2/-2)
- Jeroen T. Vermeulen (community): Approve
-
Diff: 301 lines (+110/-82)4 files modified.bzrignore (+2/-0)
README (+14/-2)
pgbouncer/fixture.py (+64/-41)
pgbouncer/tests.py (+30/-39)
- Gavin Panella (community): Approve
-
Diff: 74 lines (+28/-7)2 files modifiedpgbouncer/fixture.py (+13/-7)
pgbouncer/tests.py (+15/-0)
- Free Ekanayaka (community): Approve
- Raphaël Badin: Approve (code*)
-
Diff: 661 lines (+446/-94)7 files modified.bzrignore (+3/-0)
Makefile (+9/-4)
README (+19/-2)
ez_setup.py (+284/-0)
setup.py (+33/-20)
test (+11/-68)
tests/__init__.py (+87/-0)
Changed in launchpad: | |
assignee: | nobody → Gavin Panella (allenap) |
Changed in storm: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Gavin Panella (allenap) |
Changed in storm: | |
status: | In Progress → Fix Committed |
Changed in launchpad: | |
status: | Invalid → In Progress |
Changed in launchpad: | |
status: | In Progress → Fix Released |
Changed in storm: | |
status: | Fix Committed → Fix Released |
I also tried starting a Librarian manually, with “bin/start_ librarian. ” That starts up happily, without any weirdness in the blog. I suppose things only start getting weird at the time of first use. It's not technically impossible though that those null bytes are just sitting in a buffer somewhere waiting to be flushed by the first error message.