搭建Ruby on Rails(PostgreSQL)项目时执行rake db:create遇冲突及连接失败问题求助

Hey there! Let's work through each of these problems step by step to get your project up and running. I'll start with the most critical issue first, then tackle the warnings.

1. PostgreSQL Connection Failure (The Root Cause of rake aborted!) #

This is the error that's actually stopping your database creation. Let's fix it first:

• Check if PostgreSQL is running
  On Linux (systemd-based systems like Ubuntu), run:

  sudo systemctl status postgresql
  

  If it's not active, start the service:

  sudo systemctl start postgresql
  

  On macOS (if you installed via Homebrew), check status with:

  pg_ctl status -D /usr/local/var/postgres
  

  Start it if needed:

  pg_ctl start -D /usr/local/var/postgres
  

• Verify the Unix Socket Path
  The error says it can't find the socket at /var/run/postgresql/.s.PGSQL.5432. To find where PostgreSQL is actually creating its socket:

  1. Look at the PostgreSQL process arguments:

     ps aux | grep postgres
     

     Look for -k or unix_socket_directories in the output.
  2. Or check your PostgreSQL config file (location varies by OS—common paths are /etc/postgresql/<version>/main/postgresql.conf or /usr/local/var/postgres/postgresql.conf) for the unix_socket_directories setting.
  3. Update your config/database.yml to use the correct socket path. For example:

     development:
       adapter: postgresql
       database: your_app_name_development
       socket: /path/to/your/socket/.s.PGSQL.5432
     

• Validate Your database.yml Config
  Make sure your development environment settings are correct. A basic setup might look like this (adjust to match your system):

  development:
    adapter: postgresql
    encoding: unicode
    database: my_rails_app_development
    pool: 5
    username: your_system_username # Usually matches your OS username
    password: <%= ENV['MY_APP_DB_PASSWORD'] %> # Omit if you don't have a password set
  

• Check PostgreSQL User Permissions
  If you can't connect via psql postgres, create a superuser for your system account:

  createuser -s your_system_username
  

2. Rake Executable Conflict Warning #

This warning happens because multiple gems (redis-rack and the core rake gem) provide a rake executable, and the system isn't sure which to use. Fix it with either:

• Use bundle exec for all rake commands
  Run your database creation command like this instead:

  bundle exec rake db:create
  

  This ensures you're using the rake version specified in your Gemfile.

• Generate project-specific binstubs
  For a longer-term fix, create a local binstub for rake:

  bundle binstub rake
  

  Now you can run commands directly with:

  ./bin/rake db:create
  

  If you run into conflicts with other executables later, repeat the command with the gem name (e.g., bundle binstub redis-rack).

3. Skylight Development Mode Warning #

This is just an informational message, not an error. Skylight is a performance monitoring tool, and it's telling you it won't report data in development mode. To turn off the warning permanently, run:

skylight disable_dev_warning

Once you fix the PostgreSQL connection issue, running bundle exec rake db:create should work without aborting. The other two warnings are just noise that you can resolve to keep your terminal output clean.

内容的提问来源于stack exchange，提问作者Riya Yadav