SupportSages » PostgreSQL http://www.supportsages.com/blog Technical Support and Server Management : Musings in the fox hole. Fri, 16 Jul 2010 02:47:40 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 cPanel, postgresql and a default database issue with 8.4.x versions of postgres http://www.supportsages.com/blog/2010/05/cpanel-postgresql-and-a-default-database-issues-with-8-4-x-versions-of-postgres/ http://www.supportsages.com/blog/2010/05/cpanel-postgresql-and-a-default-database-issues-with-8-4-x-versions-of-postgres/#comments Sun, 23 May 2010 20:18:01 +0000 arnold http://www.supportsages.com/blog/?p=614 Issue reported in the phppGAdmin page was [plain] FATAL: password authentication failed for user "cPanel_username" FATAL: permission denied for database "template1" DETAIL: User does not have CONNECT privilege. [/plain] Solution [bash] # su - postgres -bash-3.2$ psql psql (8.4.2) Type "help" for help. postgres=# alter user cPanel_username with password 'password_here'; ALTER ROLE postgres=# alter user cPanelusername_username with password 'password_here'; [/bash] Check for issues in /var/lib/pgsql/pgstartup.log . That is where postgreSQL throws out errors which will be helpful in debugging the issues. In prior releases, template1 was used both as a default connection for utilities like ...]]> The issue was there, because customer wanted a latest version of Postgresql, latest than what cPanel support by default.

Issue reported in the phppGAdmin page was

FATAL:  password authentication failed for user "cPanel_username"
FATAL:  permission denied for database "template1"
DETAIL:  User does not have CONNECT privilege.

Solution

# su - postgres
-bash-3.2$ psql
psql (8.4.2)
Type "help" for help.

postgres=# alter user cPanel_username with password 'password_here';
ALTER ROLE
postgres=# alter user cPanelusername_username with password 'password_here';

Check for issues in /var/lib/pgsql/pgstartup.log . That is where postgreSQL throws out errors which will be helpful in debugging the issues.

In prior releases, template1 was used both as a default connection for utilities like createuser, and as a template for new databases. This caused CREATE DATABASE to sometimes fail, because a new database cannot be created if anyone else is in the template database. With this change, the default connection database is now postgres, meaning it is much less likely someone will be using template1 during CREATE DATABASE.

Also, do change the postgresql configuration file of cPanel installation, /usr/local/cpanel/base/3rdparty/phpPgAdmin/conf/config.inc.php

Look for

$conf['servers'][0]['defaultdb'] = 'template1';

and change it to

$conf['servers'][0]['defaultdb'] = 'postgres';

Don’t forget to chattr also. BTW now a days, cPanel is intelligent enough to detect and remove the chattrs also :D .

Post to Twitter Tweet This Post

]]> http://www.supportsages.com/blog/2010/05/cpanel-postgresql-and-a-default-database-issues-with-8-4-x-versions-of-postgres/feed/ 0 Postgresql issues with a cPanel server http://www.supportsages.com/blog/2010/01/postgresql-issues-with-a-cpanel-server/ http://www.supportsages.com/blog/2010/01/postgresql-issues-with-a-cpanel-server/#comments Sun, 17 Jan 2010 02:30:34 +0000 Sam http://www.supportsages.com/blog/?p=612 Cpanel::AdminBin::adminrun(postgres) set error in context postgres [2010-01-16 12:24:18 -0500] warn [postgres::listdbs] Encountered error in postgres::listdbs: Error from postgres wrapper: PostgreSQL has not been configured by the administrator. Unable to locate pgpass file. This was fixed by doing these, Login to WHM => SQL Services => Postgres Config => Click on “Install Config”. Login to WHM => SQL Services => Postgres Config ...]]> Recently with a cPanel server, we had this issue of not being able to create postgresql database even after the postgresql package is installed and database server is running. Fixing of one issue lead to another there by needing to fix all the errors.

Cpanel::AdminBin::adminrun(postgres) set error in context postgres
[2010-01-16 12:24:18 -0500] warn [postgres::listdbs] Encountered error in postgres::listdbs: Error from postgres wrapper: PostgreSQL has not been configured by the administrator. Unable to locate pgpass file.

This was fixed by doing these,

Login to WHM => SQL Services => Postgres Config => Click on “Install Config”.
Login to WHM => SQL Services => Postgres Config => “Set a Postgresql password also”

No error in cPanel after doing above. However that followed by an issue of created DBs not being appeared in the List DB page of Postgresql databases. Went to shell. Logged in as root . Switched to postgres. “su – postgres” . Ran the command “psql” and then

-bash-3.2$ psql
Welcome to psql 8.1.18, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

postgres=# \l
List of databases
Name | Owner | Encoding
-----------+----------+----------
postgres | postgres | UTF8
template0 | postgres | UTF8
template1 | postgres | UTF8
(3 rows)

postgres=# \q

No DB was created. Checked the logs /usr/local/cpanel/logs/error_log and it had entries like ERROR: role “username” does not exist which meant, no roles to create the database.

cd /var/cpanel/users && for x in *; do su -c "createuser -S -D -R $x" postgres; done

Post to Twitter Tweet This Post

]]> http://www.supportsages.com/blog/2010/01/postgresql-issues-with-a-cpanel-server/feed/ 0