FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-31-2010, 05:43 AM
Sthu Deus
 
Default Postgres server does not start.

Good day.


Please, help me to run my postgres DB.

Here is problem description.

I have 2 instances in /var/lib/postgresql/8.3:

main
mine

When I start postgres server w/ command:

/etc/init.d/postgresql-8.3 start

I get:

Starting PostgreSQL 8.3 database server: main mineThe PostgreSQL server failed to start. Please check the log output. failed!
failed!

In the appropriate logs I have:

for the main:

2010-01-31 13:31:00 GMT-7 LOG: could not load root certificate file "root.crt": no SSL error reported
2010-01-31 13:31:00 GMT-7 DETAIL: Will not verify client certificates.
2010-01-31 13:31:00 GMT-7 LOG: test message did not get through on socket for statistics collector
2010-01-31 13:31:00 GMT-7 LOG: disabling statistics collector for lack of working socket
2010-01-31 13:31:00 GMT-7 WARNING: autovacuum not started because of misconfiguration
2010-01-31 13:31:00 GMT-7 HINT: Enable the "track_counts" option.
2010-01-31 13:31:00 GMT-7 LOG: database system was shut down at 2010-01-31 13:10:52 GMT-7
2010-01-31 13:31:00 GMT-7 LOG: incomplete startup packet
2010-01-31 13:31:00 GMT-7 LOG: database system is ready to accept connections

and for the mine:

2010-01-31 13:31:03 GMT-7 LOG: could not load root certificate file "root.crt": no SSL error reported
2010-01-31 13:31:03 GMT-7 DETAIL: Will not verify client certificates.
2010-01-31 13:31:03 GMT-7 LOG: could not bind IPv4 socket: Address already in use
2010-01-31 13:31:03 GMT-7 HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2010-01-31 13:31:03 GMT-7 WARNING: could not create listen socket for "localhost"
2010-01-31 13:31:03 GMT-7 FATAL: could not create any TCP/IP sockets

So, I can not connect to the databases from "mine".
From the logs I do understand that "mine" have a concurrency w/ the "main" - but I did not change postgres configuration - as far as I remember, - and since I installed postgres I used both - main and mine - w/o any concurrency.

So, what is wrong? Or how I can fix it?


PS Reading of the install and run chapters of the postgres documentation gave me no ideas, as well as searching on Internet - relating to my problem.

Thanks for Your time.

PS Please, reply to the list.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-31-2010, 09:19 PM
 
Default Postgres server does not start.

On 2010-01-31 13:43, Sthu Deus wrote:
> 2010-01-31 13:31:03 GMT-7 LOG: could not bind IPv4 socket: Address already in use
> 2010-01-31 13:31:03 GMT-7 HINT: Is another postmaster already
> running on port 5432? If not, wait a few seconds and retry.
> 2010-01-31 13:31:03 GMT-7 WARNING: could not create listen socket for "localhost"
> 2010-01-31 13:31:03 GMT-7 FATAL: could not create any TCP/IP sockets

Most likely the cluster 'main' is already listening on port 5432. Try
configuring either 'main' or 'mine' to listen on another port, say
5433, by editing the cluster's postgresql.conf.
--
Nick


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-03-2010, 06:13 AM
Sthu Deus
 
Default Postgres server does not start.

Thank You for Your time and answer, debuser@acrasis.net:

>On 2010-01-31 13:43, Sthu Deus wrote:
>> 2010-01-31 13:31:03 GMT-7 LOG: could not bind IPv4 socket: Address already in use
>> 2010-01-31 13:31:03 GMT-7 HINT: Is another postmaster already
>> running on port 5432? If not, wait a few seconds and retry.
>> 2010-01-31 13:31:03 GMT-7 WARNING: could not create listen socket for "localhost"
>> 2010-01-31 13:31:03 GMT-7 FATAL: could not create any TCP/IP sockets
>
>Most likely the cluster 'main' is already listening on port 5432. Try
>configuring either 'main' or 'mine' to listen on another port, say
>5433, by editing the cluster's postgresql.conf.

Yes, it did the trick w/ changing socket dir. to /tmp. And it works, still, I'm sure, I did not change it. Weird it went this way.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 08:16 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org