Re: [Sqlgrey-users] Bug report

[Lionel B. <lio...@bo...>]

Jim Richardson wrote the following on 01.05.2005 16:21 :

> I had a vpn hiccup last night that lasted about 10 minutes. Sqlgrey
> reported the Lost DB, but then died.
> The logs contain the entries below if it helps. I am running 1.5.4
>
> May  1 05:53:48 server23 sqlgrey: Error: couldn't get now() from DB:
> Lost connection to MySQL server during query
> May  1 05:53:48 server23 sqlgrey: Forked cleanup child (16690)
> May  1 05:56:57 server23 sqlgrey: Can't connect to DB: Can't connect
> to MySQL server on 'server82.vpn.domain.tld' (110)
> May  1 05:56:57 server23 sqlgrey: Can't connect to DB: Can't connect
> to MySQL server on 'server82.vpn.domain.tld' (110)
> May  1 05:57:16 server23 sqlgrey: fatal: Can't call method
> "prepare_cached" on unblessed reference at /usr/sbin/sqlgrey line 203.
> May  1 06:00:25 server23 sqlgrey: Can't connect to DB: Can't connect
> to MySQL server on 'server82.vpn.domain.tld' (110)
> May  1 06:00:25 server23 sqlgrey: fatal: Can't call method "do" on
> unblessed reference at /usr/sbin/sqlgrey line 177.
>

Seems I found the problem (createdb was accessing the database handler
without checking it was sane and automaticaly created one non-blessed
hash in the process).
This bug should only be triggered with MySQL and SQLite (although being
disconnect from a SQLite DB should be quite uncommon :-)).

The fix is in my tree, I'll probably release 1.5.6 with it, IPv6 and
optin/optout this evening (GMT time).

Lionel.