Hi Randall,
It looks like one of the Solaris patches has changed the behaviour of
ld, and this is causing it to not find the openssl 0.9.6 libraries when
PostgreSQL tries to load.
You'll probably have to take some time and read the info in each patch
to try and determine which patch caused the change in ld's behaviour,
then maybe either roll the patch back or see if there is some
recommended way of making ld work as before.
Would it also be possible to do something simple like export the
LD_LIBRARY_PATH variable (pointing towards openssl) before attempting to
start postmaster?
i.e.
As the postgres user :
$ LD_LIBRARY_PATH=/path/to/openssl:/path/to/other/things/if/needed
$ export LD_LIBRARY_PATH
$ /usr/local/pgsql/bin/postmaster -D /export/spare/home/postgres/data &
???
Regards and best wishes,
Justin Clift
Randall Perry wrote:
>
> Suddenly getting this error on start on a Solaris 8 system (after applying a
> bunch of patches)
>
> > /usr/local/pgsql/bin/postmaster -D /export/spare/home/postgres/data &
> ld.so.1: /usr/local/pgsql/bin/postmaster: fatal: libssl.so.0.9.6: open
> failed: No such file or directory
> [1] 1959
> [1] Killed /usr/local/pgsql/bin/postmaster -D
> /export/spare/home/postgres/data
>
> Help!
>
> --
> Randy Perry
> sysTame
> Mac Consulting/Sales
>
> phn 561.589.6449
> mobile email help@systame.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi