Started GET "/" for 8.25.197.27 at 2015-06-06 19:05:51 +0000 PG::ConnectionBad (FATAL: the database system is shutting down ): config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets' config/initializers/silence_logger.rb:26:in `call' lib/middleware/request_tracker.rb:64:in `call' This is the failure I see the production.log. I could not restart the postgresql database too. Any suggestions for troubleshooting and fixing this? I dont have a backup, yet. Here is more information from the apache error log. App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `initialize' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `new' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `connect' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:568:in `initialize' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in `new_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:445:in `checkout_new_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `acquire_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrieve_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_handling.rb:113:in `retrieve_connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_handling.rb:87:in `connection' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/associations/join_dependency.rb:96:in `initialize' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:355:in `new' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:355:in `construct_join_dependency' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/finder_methods.rb:286:in `exists?' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/lib/permalink_constraint.rb:4:in `matches?' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:37:in `block in matches?' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `each' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `all?' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:36:in `matches?' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:45:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:73:in `block in call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `each' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:678:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:46:in `render_exception' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:35:in `rescue in call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:38:in `call_app' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:22:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/config/initializers/silence_logger.rb:26:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/request_id.rb:21:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/mini_profiler/profiler.rb:193:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/lib/middleware/request_tracker.rb:64:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:514:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `public_send' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `method_missing' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each' App 28223 stderr: /opt/bitnami/apps/discourse/htdocs/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/rack/thread_handler_extension.rb:85:in `process_request' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler/thread_handler.rb:149:in `accept_and_process_next_request' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler/thread_handler.rb:110:in `main_loop' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phusion_passenger/request_handler.rb:414:in `block (3 levels) in start_threads' App 28223 stderr: /opt/bitnami/ruby/lib/ruby/gems/2.0.0/gems/passenger-5.0.6/lib/phus App 28223 stderr: ion_passenger/utils.rb:111:in `block in create_thread_and_abort_on_exception' App 28223 stderr: Error during failsafe response: FATAL: the database system is shutting down

What changes did you make and is this a Docker based install, because that is the only kind we can support.

Hello Jeff. Sorry, this is not a Docker based install. I used bitnami on google cloud. Since I saw the exception coming from change in the values of mene items from Basic Setup Configuration, I thought, I will post it here. I removed all the entries in the Top Menu and I tried to save it. If it is instance specific, I will take it up with Bitnami forums (where one of suggestions is to reinstall the setup). I wanted some more details on this.

I made some changes to settings and then my site wont be up

Product Support Self-hosting

codinghorror (Jeff Atwood) 7 Junho , 2015 02:47 4

Sorry, we can only support the Docker based install due to limited resources. My apologies.

Tópico		Respostas	Vistas
UPGRADE OF POSTGRES FAILED - I've tried everything Self-hosting	17	2908	25 Agosto , 2020
Upgrade failed due to unclean database shutdown Self-hosting	20	4498	30 Dezembro , 2016
Manual upgrade failure due to postgres error Self-hosting	1	537	28 Outubro , 2020
Help! Upgrade led to complete fail Self-hosting	7	1571	9 Março , 2021
Discourse Bad Gateway after reboot Self-hosting	15	2392	2 Julho , 2020

I made some changes to settings and then my site wont be up

Related topics