[SR-Users] 503 on DB Error

[Alex Hermann]

On Monday 12 December 2011, Daniel-Constantin Mierla wrote:
> On 12/10/11 11:36 AM, Olle E. Johansson wrote:
> > I have been thinking about this as well. We could implement a db_ping
> > function so we could test in the routing script before calling functions
> > that use the DB. It's harder with stuff that happens in the background,
> > like ACC and SIPTRACE. I don't know what happens with them if the
> > database fails.
> 
> one option would be to set a config env variable, like db_error, which
> is set by the db modules on error. Then can be checked in the config and
> act accordingly. This will require touching the db modules.
> 
> Alternative is to propagate some return codes up to config file, but
> this will require changes in all modules interacting with database,
> including the db modules.

How about calling an error_route block when a DB error occurs. Maybe with the 
proper return stack setup so the admin is able to return to the statement 
following the failed db query if he doesn't want to end the processing with 
some failure reply.

-- 
Greetings,

Alex Hermann