Project

General

Profile

Actions

Feature #10289

closed

Don't exit when database is not ready

Added by Brice Beaumesnil about 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix

Description

If we start our redmine after our postgresql server, we have an error and the rails server stop.

It could be useful to keep rails server alive (for example, if we stop postgresql during rails execution we have errors but no crash : it's better like that).

trace :

active_record/connection_adapters/postgresql_adapter.rb:941:in `initialize': could not connect to server: Connection refused (PG::Error)
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/postgresql_adapter.rb:941:in `new'
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/postgresql_adapter.rb:941:in `connect'
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/postgresql_adapter.rb:217:in `initialize'
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/postgresql_adapter.rb:37:in `new'
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/postgresql_adapter.rb:37:in `postgresql_connection'
from /ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract/connection_pool.rb:223:in `new_connection'
...

Actions #1

Updated by Jean-Philippe Lang about 12 years ago

  • Tracker changed from Defect to Feature
  • Subject changed from Crash when database is not ready to Don't exit when database is not ready
  • Category set to Database
  • Status changed from New to Closed
  • Resolution set to Wont fix

This is the standard behaviour for a Rails application.
I don't think it will be changed in Redmine.

Actions

Also available in: Atom PDF