I received absolutely no reply to my question on the CentOS mailing
list so I have to turn to this venue again for help.
I note the following things:
postgresql-server.i386 8.4.4-2PGDG.el5
installed
openssl.i686 0.9.8e-12.el5_4.6
On Tue, 2010-12-07 at 16:54 -0500, James B. Byrne wrote:
I received absolutely no reply to my question on the CentOS mailing
list so I have to turn to this venue again for help.
I note the following things:
postgresql-server.i386 8.4.4-2PGDG.el5
installed
On Tue, December 7, 2010 16:56, Joshua D. Drake wrote:
No those lib differences are both still 32bit. You would have a
problem if one was 64bit. So you should be fine there.
Joshua D. Drake
Ok. How do I get postgresql to cough up more processing detail on
startup? The message that I
James B. Byrne byrn...@harte-lyne.ca writes:
Ok. How do I get postgresql to cough up more processing detail on
startup? The message that I presently get makes no sense at all to
me.
The message isn't coming from postgres --- it's openssl that you're
wishing would be more verbose.
What I'd
On Tue, Dec 07, 2010 at 05:15:45PM -0500, James B. Byrne wrote:
On Tue, December 7, 2010 16:56, Joshua D. Drake wrote:
No those lib differences are both still 32bit. You would have a
problem if one was 64bit. So you should be fine there.
Joshua D. Drake
Ok. How do I get
I have now tracked down and resolved the problem. There were clues
to the solution in the error message but I lacked sufficient
experience with ssl to realize it. The error was an uncommented
line in /etc/pki/tls/openssl.cnf that depended upon an environment
variable (ALTNAME) being set
