From: | Reid Thompson <Reid(dot)Thompson(at)ateb(dot)com> |
---|---|
To: | dennis jenkins <dennis(dot)jenkins(dot)75(at)gmail(dot)com> |
Cc: | reid(dot)thompson(at)ateb(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Solaris 10u9, PG 8.4.6, 'c' lang function, fails on 1 of 5 servers |
Date: | 2011-09-29 17:48:19 |
Message-ID: | 1317318511.8404.124.camel@raker.ateb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2011-09-29 at 12:08 -0500, dennis jenkins wrote:
> ERROR: could not load library "/db/pgsql_micr_parser_64.so": ld.so.1:
> postgres: fatal: /db/pgsql_micr_parser_64.so: Permission denied
for a different shared object, but may provide clues...
Error: "- adding iplike database function... <snip>
org.postgresql.util.PSQLException: ERROR: could not access file
'<snip>/lib/iplike.so': Permission denied"
The PostgreSQL server cannot access the iplike.so file. This could be
due to the file itself not having appropriate permissions for the user
that PostgreSQL runs as and
/or one or more of the parent directories of the iplike.so not having
appropriate permissions.
Error: "- adding iplike database function... <snip>
org.postgresql.util.PSQLException: ERROR: could not load library ..."
The latter part of the error could be something like "<path>/iplike.so:
cannot open shared object file: No such file or directory" or "ld.so.1:
postgres: fatal: <path>/iplike.so: wrong ELF class: ELFCLASS32".
The PostgreSQL server cannot load the iplike.so file. This is almost
always caused by the PostgreSQL server and the iplike.so file being
compiled for different processor instruction sets.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-09-29 17:50:18 | Re: PDT but not WEST |
Previous Message | Igor Neyman | 2011-09-29 17:38:43 | Re: Rules going away |