Re: sslv3 alert illegal parameter [SOLVED]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Albe,

Txs for replying.

I did all the necessary mods to the postgresql.conf and put as much
info as I could in the logs.

The 'culprit' was localhost .... with no discernible reason whatsoever
... :O

Anyway, after exausting all possbilities and learning that openssl
0.9.8b as memory leaks issues :-( the only thing left for me was
restarting the server and go figure: it went way on its on! :O

So as much as I'd love to know the reason I guess I'll just be happy
that the thing resolved itself with a sort of a
sword-dangling-over-my-head feeling ...

Best regards,

Pedro Doria Meunier
GSM: +351 96 17 20 188
Skype: pdoriam

Albe Laurenz wrote:
> Pedro Doria Meunier wrote:
>> My server started spitting this out every second!
>>
>> LOG: could not accept SSL connection: sslv3 alert illegal
>> parameter
>>
>> "PostgreSQL 8.3.7 on x86_64-redhat-linux-gnu, compiled by GCC gcc
>> (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)"
>>
>> Server key in place..
>>
>> What can I do about it?!
>
> Several ideas:
>
> You say "started spitting": that suggests that this is a new
> phenomenon. What changes have there been since before it started?
>
> Every second: Try to find out what tries to connect every second.
> Set "log_connections" to "on" and find out the IP address.
>
> Once you have found the culprit, figure out how it tries to
> connect.
>
> Yours, Laurenz Albe
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFKVb6a2FH5GXCfxAsRAmBfAJ46fR1jOrSphHPxL5icYVum/EU1xQCgvTew
INQgVjKv4fOXvw7Ic82XNM4=
=oR5w
-----END PGP SIGNATURE-----