Re: [Sqlgrey-users] 2 more (small) issues with SQLGrey 1.4.0

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

HaJo Schatz wrote the following on 12/24/04 05:39 :

>Hi Lionel,
>
>Just discovered two start-up issues with sqlgrey while doing a reboot of 
>my mail server:
>
>- During boot, sqlgrey couldn't access postgresql yet (DBI returned "db 
>is starting up"). sqlgrey then tried to create the from_awl table, 
>failed (db still starting up) and died silently (rather than, what would 
>IMO have been correct, retrying after a while). I have attached the 
>relevant part of the log below fyi.
>
>  
>

I'll have to see if I can make sqlgrey exit with an error, this is the 
most desirable behaviour as scripts launching sqlgrey could then detect 
the problem and output an error on the console.
Retrying after a while is IMHO not worth it (it can't decide on its own 
how much time it has to sleep). SQLgrey must be started after the 
database and this is the administrator's job to configure the system 
accordingly.

>- I accidentially started sqlgrey (thorugh /etc/init.d/sqlgrey start) as 
>non-root user. The init-script said:
>
>'Starting SQLgrey: Pid_file "/var/run/sqlgrey.pid" already exists. 
>Overwriting!'
>
>and then '[ OK ]'. However, it was of course not OK, sqlgrey died with a 
>  permission-denied on the PID file, did not tell me however...
>
>  
>

This is related to the problem above, SQLgrey doesn't exit with an error 
today, I'll have to look if I can make the appropriate checks *before* 
it forks to daemonize itself.

Thanks for the bug-reports,

I hope all of you found pleasant surprises under the tree, enjoyed some 
good time and delicious meals :-)

Lionel (back from numerous enjoyable and delicious meals).