... btw, were you able to resolve your original problem? What was it?
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Oliver Elphick writes:
> On 9 August 2013 02:49, Tom Lane wrote:
>> I wonder whether we shouldn't change the syslogger to emit something to
>> stderr when it takes over logging, saying "logging is now redirected to
>> ".
> Shouldn't you also, or instead, log to stderr just before leaving it, in
On 9 August 2013 02:49, Tom Lane wrote:
>
> I wonder whether we shouldn't change the syslogger to emit something to
> stderr when it takes over logging, saying "logging is now redirected to
> ".
>
>
Shouldn't you also, or instead, log to stderr just before leaving it, in
case the configuration of
On 9 August 2013 01:02, Oliver Elphick wrote:
Since I have maximum logging enabled, I don't think it is getting
as far as reading the configuration files - that is not mentioned
in the log.
I regularly run into problems when some editor adds a UTF-8 BOM to
pg_hba.conf or postgres
Oliver Elphick writes:
> Linux Mint (from Ubuntu) version 9.1.
> Postgres will no longer start, but I cannot find out why.
> Command line:
> $ /usr/lib/postgresql/9.1/bin/pg_ctl start -D /home/postgresql/9.1/main -l
> /var/log/postgresql/postgresql-9.1-main.log -s -w -o '-c
> config_file="/etc/po
On 08/08/2013 04:02 PM, Oliver Elphick wrote:
To start with, it worked but the pg_hba.conf entry appeared to be wrong.
I tried changing that and then the current problem started. I tried
"listen_addresses = '*'"; then back to just 'localhost'.
Since I have maximum logging enabled, I don't thi
To start with, it worked but the pg_hba.conf entry appeared to be wrong. I
tried changing that and then the current problem started. I tried
"listen_addresses = '*'"; then back to just 'localhost'.
Since I have maximum logging enabled, I don't think it is getting as far as
reading the configurat
On 08/08/2013 03:17 PM, Oliver Elphick wrote:
I tried to change the listen_addresses line in postgresql.conf, by
adding an IPv6 address. On meeting problems I tried changing it back.
What problems?
Have you run ps to see if there is another instance of Postgres running?
Currently it says:
On 08/08/2013 03:02 PM, Oliver Elphick wrote:
Linux Mint (from Ubuntu) version 9.1.
Postgres will no longer start, but I cannot find out why.
So anything happen between the last time it started and now?:
Upgrade of Postgres?
Upgrade of Mint?
Something else?
Command line:
$ /usr/lib/postgre
Linux Mint (from Ubuntu) version 9.1.
Postgres will no longer start, but I cannot find out why.
Command line:
$ /usr/lib/postgresql/9.1/bin/pg_ctl start -D /home/postgresql/9.1/main -l
/var/log/postgresql/postgresql-9.1-main.log -s -w -o '-c
config_file="/etc/postgresql/9.1/main/postgresql.conf"'
On Sun, Oct 10, 2010 at 12:08:13AM -0700, Mike Christensen wrote:
> While I do appreciate the vote of confidence, rest assured you will
> never see a post from me that starts with "So I've been hacking the pg
> code and..."
Actually, we get *plenty* of those.
Cheers,
David.
--
David Fetter http
Postgres cannot run as root.
On Sun, Oct 10, 2010 at 9:40 AM, Rob Sargent wrote:
> Does postgres run as root or as the postgres user. I suspect you want
> postgres to own that file.
>
> Mike Christensen wrote:
>>
>> Hi, I'm trying to require SSL for Postgres connections from certain
>> IPs.. Thi
Does postgres run as root or as the postgres user. I suspect you want
postgres to own that file.
Mike Christensen wrote:
Hi, I'm trying to require SSL for Postgres connections from certain
IPs.. This is on Postgres 9.0.
First, I've followed the directions at:
http://www.postgresql.org/docs/9
coh乡w
Mike Christensen 编写:
>While I do appreciate the vote of confidence, rest assured you will
>never see a post from me that starts with "So I've been hacking the pg
>code and..."
>
>On Sat, Oct 9, 2010 at 11:54 PM, Scott Marlowe wrote:
>> On Sat, Oct 9, 2010 at 10:04 PM, Darren Duncan
>> wr
While I do appreciate the vote of confidence, rest assured you will
never see a post from me that starts with "So I've been hacking the pg
code and..."
On Sat, Oct 9, 2010 at 11:54 PM, Scott Marlowe wrote:
> On Sat, Oct 9, 2010 at 10:04 PM, Darren Duncan
> wrote:
>> The owner of these new files
On Sat, Oct 9, 2010 at 10:04 PM, Darren Duncan wrote:
> The owner of these new files needs to be the same as that of your Pg data
> dir in general or postgresql.conf specifically, and that owner be the same
> as the process that runs the Pg server. Are you running Pg as root? (In
> any event, yo
Yup, my bad.. I should have noticed all the other files were owned by
postgres (and I assume that's what the process is running under)..
I'm still a Unix newbie, but learning quickly..
Everything's working, and to my surprise pgAdmin connected using SSL
on the first try.. No need to mess with an
The owner of these new files needs to be the same as that of your Pg data dir in
general or postgresql.conf specifically, and that owner be the same as the
process that runs the Pg server. Are you running Pg as root? (In any event,
you should have another user; running programs or servers as r
Sweet! That fixed it.. Rock on..
Of course now let's see if I can connect from my Mac client :)
On Sat, Oct 9, 2010 at 9:00 PM, Ben Carbery wrote:
> The private keys needs to be readable by the same user the server runs
> under. This is distribution-dependent and may not be 'root'.
> In my cas
The private keys needs to be readable by the same user the server runs
under. This is distribution-dependent and may not be 'root'.
In my case I run Red Hat which uses the 'postgres' user, so:
chown postgres.postgres /var/lib/pgsql/data/server.*
On Sun, Oct 10, 2010 at 2:52 PM, Mike Christensen
Hi, I'm trying to require SSL for Postgres connections from certain
IPs.. This is on Postgres 9.0.
First, I've followed the directions at:
http://www.postgresql.org/docs/9.0/static/ssl-tcp.html
I've created the files server.crt and server.key. I've also removed
the passphrase from the key so P
> I know, from IRC, the problem has been solved, there was no space on the
> disk ...
>
> Unfortunately, i haven't logs.
>
Yes. Thanks to everybody on the IRC who helped me out.
The suggestion that was most helpful was to call the posgres binary
directly. /usr/lib/postgresql/8.3/bin/postgres. Cal
Tim Uckun wrote:
> Unfortunately there is nothing anywhere telling me what the problem
> is. The log file is empty, there is nothing in the /var/log/messages
> or /var/log/syslog either. The only output I get is this.
>
> * Starting PostgreSQL 8.3 database server
> * The PostgreSQL server faile
aucune responsabilité
pour le contenu fourni.
> Subject: Re: [GENERAL] Postgres won't start. Nothing in the log.
> From: dev...@gunduz.org
> To: timuc...@gmail.com
> CC: pgsql-general@postgresql.org
> Date: Mon, 5 Oct 2009 17:16:00 +0300
>
> On Mon, 2009-10-05 at 17:
On Mon, 2009-10-05 at 17:39 +1300, Tim Uckun wrote:
> Unfortunately there is nothing anywhere telling me what the problem
> is. The log file is empty, there is nothing in the /var/log/messages
> or /var/log/syslog either. The only output I get is this.
>
> * Starting PostgreSQL 8.3 database serve
"Markus Wollny" writes:
> pgsql-general-ow...@postgresql.org wrote:
>> Unfortunately there is nothing anywhere telling me what the
>> problem is. The log file is empty, there is nothing in the
>> /var/log/messages or /var/log/syslog either. The only output
>> I get is this.
>>
>> * Starting Postg
2009/10/5 Markus Wollny
> Hi!
>
> pgsql-general-ow...@postgresql.org wrote:
> > Unfortunately there is nothing anywhere telling me what the
> > problem is. The log file is empty, there is nothing in the
> > /var/log/messages or /var/log/syslog either. The only output
> > I get is this.
> >
> > *
Hi!
pgsql-general-ow...@postgresql.org wrote:
> Unfortunately there is nothing anywhere telling me what the
> problem is. The log file is empty, there is nothing in the
> /var/log/messages or /var/log/syslog either. The only output
> I get is this.
>
> * Starting PostgreSQL 8.3 database server
>
I just did an upgrade on two of my servers (the main and the
failover). The main went OK but the postgres on the failover won't
start.
Unfortunately there is nothing anywhere telling me what the problem
is. The log file is empty, there is nothing in the /var/log/messages
or /var/log/syslog either.
29 matches
Mail list logo