Comment 1 for bug 578338

Just a bit of info from when I tried to look into this on Friday:

On Fri, May 7, 2010 at 5:47 PM, Michael Nelson <email address hidden> wrote:
> So I've been playing with r9336 production stable, and running the
> buildd-manager with a non-local postgres connection (and killing my
> local psql), and I cannot reproduce this without removing the host
> option for the db config.
>
> So far, I cannot see why we are trying to connect to a local postgres
> intsance on cesium, or why the issue disappears after a restart, nor
> reproduce the issue :/
>
> The possibilities:
> 1) LPCONFIG env. variable was not set during first run - unlikely but possible?
> 2) A change to some of the dbconfig loading options (there were some
> during the 10.04 cycle) introduced some kind of config loading issue -
> very unlikely.
>
> I'd recommend that we ask a losa to re-update cesium to
> production-stable and restart again (and find out exactly what command
> they run to restart it - the wiki only has examples for the old slave
> scanner/buildd-sequencer).

It would have been nice to be able to test the above using the same startup script used in production.