PG::ConnectionBad (Could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGsql.5432"? ):
My Dockerfile
FROM phusion/passenger-customizableMAINTAINER VodkaMD <support@nyvur.com>ENV RACK_ENV="production" RAILS_ENV="production" SECRET_KEY_BASE="e09afa8b753cb175bcef7eb5f737accd02a4c16d9b6e5d475943605abd4277cdf47c488812d21d9c7117efd489d876f34be52f7ef7e88b21759a079339b198ce"ENV HOME /rootCMD ["/sbin/my_init"]RUN /pd_build/utilitIEs.shRUN /pd_build/ruby2.2.shRUN /pd_build/python.shRUN /pd_build/nodeJs.sh# Custom instructionsRUN apt-get update && apt-get install -y vim nano dialog net-tools build-essential wgetRUN apt-get install -y postgresql-clIEnt --no-install-recommendsRUN apt-get clean && rm -rf /var/lib/apt/Lists/* /tmp/* /var/tmp/*# Generate SSL CertificateRUN mkdir /etc/Nginx/ssl# RUN openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/Nginx/ssl/Nginx.key -out /etc/Nginx/ssl/Nginx.crt# Enable Nginx and PassengerRUN rm -f /etc/service/Nginx/down# Enable RedisRUN rm -f /etc/service/redis/down# Enable SSHRUN rm -f /etc/service/sshd/down# Enable PostgresRUN rm -f /etc/service/postgres/down# Install bundle of gemsworkdir /tmpADD Gemfile /tmp/ADD Gemfile.lock /tmp/RUN bundle install# copy application folderRUN mkdir /home/app/NyvurADD . /home/app/NyvurRUN chown -R app:app /home/app/Nyvurworkdir /home/app/NyvurRUN bundle exec rake assets:precompile# Add a virtual host entryRUN rm /etc/Nginx/sites-enabled/defaultcopY config/Nginx_configs.conf /etc/Nginx/sites-enabled/Nyvur.confADD config/postgres-env.conf /etc/Nginx/main.d/postgres-env.confRUN mkdir -p /var/www/Nyvur/tmp/pIDsRUN mkdir -p /var/www/Nyvur/tmp/socketsRUN mkdir -p /var/www/Nyvur/logRUN apt-get clean && rm -rf /var/lib/apt/Lists/* /tmp/* /var/tmp/*EXPOSE 80 443RUN bundle exec passenger start -p 80 -e production
My docker-compose
postgres: restart: always image: postgres:9.4.4 ports: - "5432:5432" # Bind host port 5432 to Postgresql port 5432 volumes: - ./db/dumps:/app-db-dumps - ./db/postgres-setup.sql/docker-entrypoint-initdb.d/setup.sql environment: LC_ALL: C.UTF-8 POSTGRES_PASSWORD: 3x1mpl3mongo: image: mongo:3.0.7 ports: - "27017:27017" command: --smallfiles --rest --authredis: image: redis:3.0.4 ports: - "6379:6379" # Bind host port 6379 to Redis port 6379web: &app_base build: . ports: - "80:80" volumes: - .:/Nyvur links: &app_links - postgres:postgres.local - redis:redis.local environment: &app_environment # Postgresql Development Database: # DATABASE_URL: postgres://postgres:3x1mpl3@postgres.local:5432/App_production?pool=25&enCoding=unicode&schema_search_path=public REdis_URL: redis://redis.local:6379 SIDEKIQ_CONCURRENCY: 5 SIDEKIQ_TIMEOUT: 10 ENABLE_DEBUG_SERVER: true RACK_ENV: production RAILS_ENV: productionworker: <<: *app_base ports: [] command: sIDekiq -c 25 -e production -q default environment: SECRET_KEY_BASE: e09afa8b753cb175bcef7eb5f737accd02a4c16d9b6e5d475943605abd4277cdf47c488812d21d9c7117efd489d876f34be52f7ef7e88b21759a079339b198ce environment: # SECRET_KEY_BASE: RAILS_ENV: production
Full error log
=============== Phusion Passenger Standalone web server started ===============PID file: /home/app/Nyvur/passenger.80.pIDLog file: /home/app/Nyvur/log/passenger.80.logEnvironment: productionAccessible via: http://0.0.0.0/You can stop Phusion Passenger Standalone by pressing Ctrl-C.Problems? Check https://www.phusionpassenger.com/library/admin/standalone/troubleshooting/===============================================================================App 107 stderr: stdin: is not a ttyApp 107 stdout:App 107 stdout: I,[2015-12-17T17:34:39.223372 #107] INFO -- : ** [Raven] Raven 0.12.3 ready to catch errorsI,[2015-12-17T17:34:40.413454 #127] INFO -- : Started head "/" for 127.0.0.1 at 2015-12-17 17:34:40 +0000App 127 stdout:F,[2015-12-17T17:34:41.543651 #127] FATAL -- :PG::ConnectionBad (Could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGsql.5432"?): activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `initialize' activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `new' activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `connect' activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:568:in `initialize' activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new' activerecord (4.1.2) lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in `new_connection' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:445:in `checkout_new_connection' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `acquire_connection' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout' /usr/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' /usr/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrIEve_connection' activerecord (4.1.2) lib/active_record/connection_handling.rb:113:in `retrIEve_connection' activerecord (4.1.2) lib/active_record/connection_handling.rb:87:in `connection' activerecord (4.1.2) lib/active_record/query_cache.rb:51:in `restore_query_cache_settings' activerecord (4.1.2) lib/active_record/query_cache.rb:43:in `rescue in call' activerecord (4.1.2) lib/active_record/query_cache.rb:32:in `call' activerecord (4.1.2) lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call' actionpack (4.1.2) lib/action_dispatch/mIDdleware/callbacks.rb:29:in `block in call' activesupport (4.1.2) lib/active_support/callbacks.rb:82:in `run_callbacks' actionpack (4.1.2) lib/action_dispatch/mIDdleware/callbacks.rb:27:in `call' actionpack (4.1.2) lib/action_dispatch/mIDdleware/remote_ip.rb:76:in `call' actionpack (4.1.2) lib/action_dispatch/mIDdleware/deBUG_exceptions.rb:17:in `call' actionpack (4.1.2) lib/action_dispatch/mIDdleware/show_exceptions.rb:30:in `call' railtIEs (4.1.2) lib/rails/rack/logger.rb:38:in `call_app' railtIEs (4.1.2) lib/rails/rack/logger.rb:20:in `block in call' activesupport (4.1.2) lib/active_support/tagged_logging.rb:68:in `block in tagged' activesupport (4.1.2) lib/active_support/tagged_logging.rb:26:in `tagged' activesupport (4.1.2) lib/active_support/tagged_logging.rb:68:in `tagged' railtIEs (4.1.2) lib/rails/rack/logger.rb:20:in `call' request_store (1.1.0) lib/request_store/mIDdleware.rb:8:in `call' actionpack (4.1.2) lib/action_dispatch/mIDdleware/request_ID.rb:21:in `call' rack (1.5.2) lib/rack/methodoverrIDe.rb:21:in `call' rack (1.5.2) lib/rack/runtime.rb:17:in `call' activesupport (4.1.2) lib/active_support/cache/strategy/local_cache_mIDdleware.rb:26:in `call' rack (1.5.2) lib/rack/sendfile.rb:112:in `call' sentry-raven (0.12.3) lib/raven/integrations/rack.rb:61:in `call' railtIEs (4.1.2) lib/rails/engine.rb:514:in `call' railtIEs (4.1.2) lib/rails/application.rb:144:in `call' passenger (5.0.22) src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request' passenger (5.0.22) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in `accept_and_process_next_request' passenger (5.0.22) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in `main_loop' passenger (5.0.22) src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in `block (3 levels) in start_threads' passenger (5.0.22) src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'I,[2015-12-17T17:34:41.559638 #127] INFO -- : Rendered /var/lib/gems/2.2.0/gems/actionpack-4.1.2/lib/action_dispatch/mIDdleware/templates/rescues/_source.erb (0.6ms)I,[2015-12-17T17:34:41.566011 #127] INFO -- : Rendered /var/lib/gems/2.2.0/gems/actionpack-4.1.2/lib/action_dispatch/mIDdleware/templates/rescues/_trace.HTML.erb (1.1ms)I,[2015-12-17T17:34:41.572608 #127] INFO -- : Rendered /var/lib/gems/2.2.0/gems/actionpack-4.1.2/lib/action_dispatch/mIDdleware/templates/rescues/_request_and_response.HTML.erb (0.9ms)I,[2015-12-17T17:34:41.572727 #127] INFO -- : Rendered /var/lib/gems/2.2.0/gems/actionpack-4.1.2/lib/action_dispatch/mIDdleware/templates/rescues/diagnostics.erb within rescues/layout (20.2ms)^CERROR:Aborting.
任何帮助都非常感谢,我仍然掌握着Docker并致力于生产.
解决方法 它试图连接到Unix域套接字的事实指向Rails应用程序中的配置问题.您的docker-compose.yml中包含DATABASE_URL,但它已被注释掉 – 取消注释至少应该更接近(应用程序至少应该尝试开始连接到postgres.local而不是本地Unix域套接字,而不是因为Postgres在一个单独的容器中运行所以存在. 总结以上是内存溢出为你收集整理的ruby-on-rails – Docker – PG :: ConnectionBad全部内容,希望文章能够帮你解决ruby-on-rails – Docker – PG :: ConnectionBad所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)