Rails连接PostgreSQL错误：psql:致命错误:用户“postgres”Ident认证失败

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了Rails连接PostgreSQL错误：psql:致命错误:用户“postgres”Ident认证失败，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含4443字，纯文字阅读大概需要7分钟。

内容图文

Rails连接PostgreSQL错误：psql: 致命错误: 用户 postgres Ident 认证失败

psql: 致命错误: 用户 "postgres" Ident 认证失败

1安装好postgresql数据库后需要初始化及一些配置rails项目才能连接postgresql

安装好postgresql数据后（yum命令直接安装的）

第一步：初始化数据库

#service postgresql initdb

（说明：初始化后默认postgresql数据库有一个默认的用户postgres（密码为空）和一个默认创建的postgres数据库）

第二步：启动数据库

#service postgresql start

如果这个命令不能使用请使用：#systemctl start postgresql.service

来启动数据库，，为修改密码条件

第三步：切换用户修改密码

#su postgres

#psql

#alter user postgres with password 'kuange' ;

(修改postgres用户密码为kuange,这个密码随你自己修改)

# \q

第四步：修改认证文件/var/lib/pgsql/data/pg_hba.conf，登陆使用密码。

#vi /var/lib/pgsql/data/pg_hba.conf

把这个配置文件中的认证 METHOD的ident修改为trust，可以实现用账户和密码来访问数据库，

即解决psql: 致命错误: 用户 "postgres" Ident 认证失败 这个问题）

第五步：重启postgresql服务器使设置生效

#service postgresql restart

或者

#systemctl restart postgresql.service

这样问题就解决了，数据库可以正常被rails项目访问了

pg_hba.conf这个文件的完整代码如下：

#=========================================

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file. A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
# local DATABASE USER METHOD [OPTIONS]
# host DATABASE USER ADDRESS METHOD [OPTIONS]
# hostssl DATABASE USER ADDRESS METHOD [OPTIONS]
# hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# ADDRESS specifies the set of hosts the record matches. It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask. A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts. Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
# "krb5", "ident", "peer", "pam", "ldap", "radius" or "cert". Note that
# "password" sends passwords in clear text; "md5" is preferred since
# it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE. The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted. Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can
# use "pg_ctl reload" to do that.

内容总结

以上是互联网集市为您收集整理的Rails连接PostgreSQL错误：psql:致命错误:用户“postgres”Ident认证失败全部内容，希望文章能够帮你解决Rails连接PostgreSQL错误：psql:致命错误:用户“postgres”Ident认证失败所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端