I use Zabbix a lot. There is very nice template for Postgres
http://pg-monz.github.io/pg_monz/index-en.html
On Sun, Dec 14, 2014 at 12:13 PM, Tim Smith
wrote:
> Try http://brendangregg.com/
>
> Lots of great tidbits there from a guy who really knows his performance
> stuff (ex-Sun, now Netflix)
Hello,
I have a master multi slave streaming replication setup. One master and two
slaves. I need to do some maintenance on one of the slaves as one of the
drives died however there is some other weird things going on in that array
that I would need to investigate. So I am expecting the machine to
On Mon, Dec 15, 2014 at 9:12 AM, Joseph Kregloh wrote:
> Hello,
>
> I have a master multi slave streaming replication setup. One master and two
> slaves. I need to do some maintenance on one of the slaves as one of the
> drives died however there is some other weird things going on in that array
>
On Mon, Dec 15, 2014 at 12:59 PM, Patrick Krecker
wrote:
> On Mon, Dec 15, 2014 at 9:12 AM, Joseph Kregloh
> wrote:
> > Hello,
> >
> > I have a master multi slave streaming replication setup. One master and
> two
> > slaves. I need to do some maintenance on one of the slaves as one of the
> > dr
On Mon, Dec 15, 2014 at 10:29 AM, Joseph Kregloh
wrote:
>
>
> On Mon, Dec 15, 2014 at 12:59 PM, Patrick Krecker
> wrote:
>>
>> On Mon, Dec 15, 2014 at 9:12 AM, Joseph Kregloh
>> wrote:
>> > Hello,
>> >
>> > I have a master multi slave streaming replication setup. One master and
>> > two
>> > sla
On 12/15/2014 11:12 AM, Joseph Kregloh wrote:
Hello,
I have a master multi slave streaming replication setup. One master and
two slaves. I need to do some maintenance on one of the slaves as one of
the drives died however there is some other weird things going on in
that array that I would need
I am trying to connect using SSL in Windows 7 and Postgres v9.3. The console
output error message is "Failed to establish a connection to 127.0.0.1" The
error message from the pg_log is:
---
2014-12-15 19:20:24 GMT FATAL: connection require
On Mon, Dec 15, 2014 at 2:18 PM, Patrick Krecker
wrote:
> On Mon, Dec 15, 2014 at 10:29 AM, Joseph Kregloh
> wrote:
> >
> >
> > On Mon, Dec 15, 2014 at 12:59 PM, Patrick Krecker
> > wrote:
> >>
> >> On Mon, Dec 15, 2014 at 9:12 AM, Joseph Kregloh <
> jkreg...@sproutloud.com>
> >> wrote:
> >> >
On 12/15/2014 11:41 AM, harpagornis wrote:
I am trying to connect using SSL in Windows 7 and Postgres v9.3. The console
output error message is "Failed to establish a connection to 127.0.0.1" The
error message from the pg_log is:
---
2014-
Yes, I set the CN to 127.0.0.1 for all certificates. I verified that for all
certificates using openssl verify. I can connect o.k. without the SSL.
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5830768.html
Sent from the Pos
On 12/15/2014 01:13 PM, harpagornis wrote:
Yes, I set the CN to 127.0.0.1 for all certificates. I verified that for all
certificates using openssl verify. I can connect o.k. without the SSL.
The CN needs to be the user not the IP address. Take a look at the link
I sent earlier, it is a great
I changed the CN in all the certificates from 127.0.0.1 "my_role", which is
the user id. Now the pg_log contains this:
---
2014-12-15 22:28:04 GMT LOG: database system was shut down at 2014-12-15
22:28:01 GMT
2014
harpagornis wrote
> I changed the CN in all the certificates from 127.0.0.1 "my_role", which
> is the user id. Now the pg_log contains this:
> ---
> 2014-12-15 22:28:04 GMT LOG: database system was shut down at 20
On 12/15/2014 02:36 PM, harpagornis wrote:
I changed the CN in all the certificates from 127.0.0.1 "my_role", which is
the user id. Now the pg_log contains this:
---
2014-12-15 22:28:04 GMT LOG: database system
Yes, I did intend for only SSL connections. The console app must be the
SYSTEM user then, directly or maybe indirectly through the Windows
Certificate Store. I already added root.crt to the trusted certificates
through Windows MMC. Here is my console app, in which I provide the
certificate, so w
harpagornis wrote
> The console app must be the SYSTEM user then, directly or maybe indirectly
> through the Windows Certificate Store.
Doubtful.
The log also shows the attempt is to access the "postgres" database while
your provided connection string accesses "dbname"
You should probably start
Adrian Klaver writes:
> On 12/15/2014 02:36 PM, harpagornis wrote:
>> 2014-12-15 22:28:06 GMT FATAL: connection requires a valid client
>> certificate
>> 2014-12-15 22:28:06 GMT FATAL: no pg_hba.conf entry for host "127.0.0.1",
>> user "SYSTEM", database "postgres", SSL off
> Well something is
On 12/15/2014 03:25 PM, harpagornis wrote:
Yes, I did intend for only SSL connections. The console app must be the
SYSTEM user then, directly or maybe indirectly through the Windows
Certificate Store. I already added root.crt to the trusted certificates
through Windows MMC. Here is my console
On 12/15/2014 03:49 PM, Tom Lane wrote:
Adrian Klaver writes:
On 12/15/2014 02:36 PM, harpagornis wrote:
2014-12-15 22:28:06 GMT FATAL: connection requires a valid client
certificate
2014-12-15 22:28:06 GMT FATAL: no pg_hba.conf entry for host "127.0.0.1",
user "SYSTEM", database "postgres",
On 16 Dec 2014 01:13, "Joseph Kregloh" wrote:
>
> Hello,
>
> I have a master multi slave streaming replication setup. One master and
two slaves. I need to do some maintenance on one of the slaves as one of
the drives died however there is some other weird things going on in that
array that I would
Thank you all. Would something like Wireshark, WinPcap or WFetch show me
more about the SYSTEM connection?
--
View this message in context:
http://postgresql.nabble.com/SSL-Certificates-in-Windows-7-Postgres-9-3-tp5830749p5830806.html
Sent from the PostgreSQL - general mailing list archive at
Ah! I figured out the pg_log error about "No pg_hba.conf entry for host
"127.0.0.1", user "SYSTEM", database "postgres", SSL off." That error
occurs when I go into Windows Component Services and restart postgres.
But, after I delete that pg_log file, there still is no connection and no
other p
22 matches
Mail list logo
