'pg_ctl status' returns 'neither postmaster nor postgres running'.
Looking for help restart postgres.
Thanks
On Wed, Mar 3, 2010 at 9:58 AM, Major Services wrote:
> Where to look for postmaster.pid?
> It is not in the data directory. There is one file postmaster.opts there.
>
> Should I try run
Where to look for postmaster.pid?
It is not in the data directory. There is one file postmaster.opts there.
Should I try running 'pg_ctl start -l logfile' ?
On Tue, Mar 2, 2010 at 10:24 PM, Paul Anderson wrote:
> After verifying that the postmaster was not running you did remove the
> postmaster
On Tue, Mar 2, 2010 at 12:20 PM, Scott Marlowe wrote:
> On Tue, Mar 2, 2010 at 8:43 AM, Arnold, Sandra wrote:
>> I am currently using the pg_hotbackup Perl script to backup my production
>> PostgreSQL database. However, the next production database is going to be
>> close to a terrabyte in size.
FYI, here's the conversations on the subject of LVM and write barriers
from last year about this time:
http://www.redhat.com/archives/linux-lvm/2009-March/msg00025.html
http://archives.postgresql.org/pgsql-general/2009-03/msg00204.php
Note that it's also considered bad form to post the same quest
On Tue, Mar 2, 2010 at 8:43 AM, Arnold, Sandra wrote:
> I am currently using the pg_hotbackup Perl script to backup my production
> PostgreSQL database. However, the next production database is going to be
> close to a terrabyte in size. We feel that a tar cvzf command is not the
> correct OS ba
Arnold, Sandra wrote:
I am currently using the pg_hotbackup Perl script to backup my
production PostgreSQL database. However, the next production database
is going to be close to a terrabyte in size. We feel that a tar cvzf
command is not the correct OS backup solution to use. Instead we
wo
Hi
There is a nice entry at the Postgres archive.
http://archives.postgresql.org/pgsql-general/2004-08/msg01624.php
did you remove the /tmp/.s.PGSQL.5432.lock files??
Maybee it helps
Greets
ho
-Ursprüngliche Nachricht-
Von: [email protected]
[mailto:pgsql-admin-ow...@pos
After verifying that the postmaster was not running you did remove the
postmaster.pid file, right?
FATAL: lock file "postmaster.pid"already exists
On 3/2/10 11:43 AM, Major Services wrote:
Help me start the server.
As I mentioned in an earlier post today (subject: password
authentication fail
Help me start the server.
As I mentioned in an earlier post today (subject: password
authentication failed for user postgres), 'service postgresql restart'
had stopped the server but *server
start failed*.
Step wise list of commands to be given would be great!
Do I need to login as postgres?
Bei
I am currently using the pg_hotbackup Perl script to backup my production
PostgreSQL database. However, the next production database is going to be
close to a terrabyte in size. We feel that a tar cvzf command is not the
correct OS backup solution to use. Instead we would like to use lvmsnaps
Ok, made it
listen_addresses = '*'
Now, can you please help me start the server. ( As I mentioned in earlier
post, 'service postgresql restart' had stopped the server but *server
start failed*.)
Step wise list of commands to be given would be great!
Do I need to login as postgres?
Thanks
On Tu
You cannot have a '*' in listen_addresses with anything else.
That already means bind to EVERY available interface. When you
added localhost, it tried to re-bind localhost twice. Try just
using '*'.
Cheers,
Ken
On Tue, Mar 02, 2010 at 07:19:47PM +0530, Major Services wrote:
> pgstartup.log:
>
>
pgstartup.log:
The files belonging to this database system will be owned by user
"postgres".
Success. You can now start the database server using:
/usr/bin/postmaster -D /var/lib/pgsql/data
or
/usr/bin/pg_ctl -D /var/lib/pgsql/data -1 logfile start
FATAL: lock file "postmaster.pid"alrea
Ah... ok.
In /var/lib/pgsql you will find a file called pgstartup.log
Could you post here last lines of this file ?
-Original Message-
From: Major Services
To: Iñigo Martinez Lasala
Cc: [email protected]
Subject: Re: [ADMIN] password authentication failed for user postgres
Date
But the server restart has failed; I am yet to make the changes suggested by
you in the first instance.
On Tue, Mar 2, 2010 at 4:32 PM, Iñigo Martinez Lasala <
[email protected]> wrote:
> Try with these parameters in pg_hba.conf. Perhaps your postgres-redhat
> compilation does not have i
Thank you for your message. But am in another problem now.
In between I also tried to restart the server with 'service postgresql
restart'
It stopped the server, but then *server start failed*.
Had restarted earlier also, without a problem.
What should I do?
On Tue, Mar 2, 2010 at 2:44 PM, Iñigo
In order to lauch createuser you don't need to modify listen_address
since you can use unix sockets. But anyway it's a requirement if you are
goint to access remotely.
Add this line in first place to your pg_hba.conf
local all postgres ident sameuser
Reload pos
Hi,
1. I have added listen_addresses = '*' ; in postgresql.conf
2. And have made the following changes to pg_hba.conf
local DATABASEUSER METHOD
localsamegroup all password
hostDATABASEUSERCIDR-ADDRESS METHOD [OPTION]
host all all
18 matches
Mail list logo
