Mario Splivalo writes:
> Reading the docs, it shouldn't use SSL when connecting.
I think you're misreading the docs. There's nothing in your
configuration that *forbids* an SSL connection, and libpq will try SSL
first unless configured otherwise. Try adding sslmode=disable.
On 02/02/2012 05:15 PM, Mario Splivalo wrote:
> On 02/02/2012 05:16 PM, Tom Lane wrote:
>> Mario Splivalo writes:
>>> I have these errors in my log files, occurring very often:
>>> 2012-02-02 01:05:53 CST [4103]: [2-1] user=,db= FATAL: could not
>>> receive data from WAL stream: SSL error: sslv3
On 02/02/2012 05:16 PM, Tom Lane wrote:
> Mario Splivalo writes:
>> I have these errors in my log files, occurring very often:
>> 2012-02-02 01:05:53 CST [4103]: [2-1] user=,db= FATAL: could not
>> receive data from WAL stream: SSL error: sslv3 alert unexpected message
>
> Google suggests that t
Mario Splivalo writes:
> I have these errors in my log files, occurring very often:
> 2012-02-02 01:05:53 CST [4103]: [2-1] user=,db= FATAL: could not
> receive data from WAL stream: SSL error: sslv3 alert unexpected message
Google suggests that this might be caused by version or configuration
m
I have these errors in my log files, occurring very often:
2012-02-02 01:05:53 CST [4103]: [2-1] user=,db= FATAL: could not
receive data from WAL stream: SSL error: sslv3 alert unexpected message
2012-02-02 01:05:58 CST [20507]: [301-1] user=,db= LOG: invalid magic
number in log fi
