PostgreSQL (Cannot add new user or database). It will return "User/DB added successfully" but no new user or database is added.
root@server [~]# rpm -qa | grep postgre
postgresql-devel-8.1.4-3PGDG
postgresql-contrib-8.1.4-3PGDG
postgresql-8.1.4-3PGDG
postgresql-server-8.1.4-3PGDG
postgresql-libs-8.1.4-3PGDG
postgresql-python-8.1.4-3PGDG
I've already compiled apache after postgres was upgraded months ago.
I'm using cpanel 10x
I have a server running Cpanel and I have added postgres through /scripts/installpostgres, also I have set it over WHM and can access phppgadmin but I got this error when connecting throug a script
Fatal error: Call to undefined function: pg_connect() in /home/rer1223/public_html/process/Connection.php on line 4
I checked and postgres is not listed in phpinfo output.
I have installed postgres over my cpanel account but I am unable to find php_pgsql.so file
I am running Centos 4 Apache 1.3 PHP 4.3 Postgres 7.3
This seemed like the most appropriate place so I decided to post here.
SYSTEM:
Fedora Core 4, 3GHz, 2GB RAM
Postgres 8, Apache 2, PHP 4
The issue is that I have with me a 1.5GB SQL dump from Postgres 8 which I extracted using pg_dump.
Restoring it seems to be an issue on this PC. I've tried modifying memory directives in postgresql.conf as well as the kernels SHMAX value but no go.
I tried a bunch of other things such as gzipping the file so that it was only 100mb and doing:
Code:
gunzip -c dump.sql.gz | psql my_db
But I recieved many errors saying "invalid command N" and I also got a syntax error notice and the process terminated.
I tried to at least try and enter some data manually but vim is incredibly slow since this is a 1.5GB file.
Is there a way I could perhaps split up my db dump and then import them into the db one by one?
I was hoping someone could shed some light on a cron related issue I'm having.
I've been using linux for a while...but never really used crons.
My cron is supposed to dump a postgres db in tar.gz format every minute (for testing purposes) but it doesn't.
I opened my cron in vim via:
Code:
postgres@myhost:~$ crontab -e
And here's the cron:
Code:
* * * * * /usr/bin/pg_dump -D warranty_1_6_test | gzip -c > /var/www/test/postgres/backup$(date +"%Y%m%d_%H%M").tar.gz
Also:
Code:
postgres@myhost:~$ ls -lah /var/www/test/postgres/
total 8.0K
drwxrwxrwx 2 postgres postgres 4.0K 2007-06-14 12:01 .
drwxr-xr-x 3 user user 4.0K 2007-06-14 11:47 ..
Running the backup command via CLI works fine.
i had to do a file system back up because of the size of my database.
i shutdown postmaster and tar'd the files.
i recently reloaded my OS and now i'm attempting to restore the backups. i first shut down postmaster, restored the backups to the data folder and restarted postmaster.
i then su'd from root to postgres user:
Code:
[postgres@austin1 pgsql]$ psql service_2_3
psql: FATAL: database "service_2_3" does not exist
DETAIL: The database subdirectory "base/16385" is missing.
the backups had a database named service_2_3 but upon restoring the backups, it doesn't seem to be available.
my data directory is /var/pgsql/data.
Code:
[postgres@austin1 pgsql]$ ls -lahR /var/pgsql/ | grep 16385
but that yielded nothing.
have i done something wrong while backing up? i don't think i have since i followed the postgres manual when backing up. but the administrators have not been very thorough with how they've set the system up for me.
how i can resolve this issue if you have the time.
I just reloaded the OS on our production server and I'm having issues configuring postgres.
the user postgres exists in the system (i.e. 'su postgres' switches me to that user)
i attempted to connect to my database 'service_2_3' via CLI:
Code:
$ su postgres
$ psql service_2_3
and i recieved the following error:
Code:
psql: FATAL: IDENT authentication failed for user "postgres@service_2_3"
the database is installed on the machine on which i was attempting to connect to it with.
therefore, i edited my pg_hba.conf so that it looks like this:
Code:
# TYPE DATABASE USER CIDR-ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all ident sameuser
# IPv4 local connections:
host all all 127.0.0.1/32 ident sameuser
# IPv6 local connections:
host all all ::1/128 ident sameuser
host all all 0.0.0.0 0.0.0.0 password
and reloaded with (as user postgres):
Code:
bash-3.00$ pg_ctl reload -D /var/lib/pgsql/data -l /var/lib/pgsql/data/temp.log
but i still get the same error. am i editing the wrong file, perhaps?
how would i know which is the correct pg_hba.conf file?
locate pg_hba.conf seems to give me a few results.
When I update servers via CLI autoinstaller, I always (afair) get this mysqldump error message:
Code:
Stopping psa... * Stopping Plesk engine pool manager sw-engine-fpm
...done.
done
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
mysqldump: Got error: 1049: Unknown database 'atmail' when selecting the database
===> Cumulative APS controller database (apsc) upgrade has been started.
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
Reading package lists...
There is no database "atmail" on any of our Plesk servers. Simple solution should be to first check if the DB exists before performing actions on it.As a bonus, perhaps it would be possible to suppress the warning about mysql.event.
I've just built a new LAMP server and I'm having a little issue where Apache doesn't serve a simple non-database webpage, instead, I get an error on all my virtual-host in the browser: Database Error: Unable to connect to the Database: Could not connect to MySQL.
I've googled the problem but since the error mentions MySql, everything I find is related to connecting to MySql, which I'm not trying to connect... and I've contacted my Linux mentor about this issue... This is something I've never seen before... don't know why Apache thinks I'm trying connect to MySQL on every browser call to the server...
However, MySQL is accessible via telnet, and all my permissions are correct...