Обсуждение: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error
Hello,
After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an error dialog box. This is a pgadmin3 client on Windows. The error says:
--------------------------------------------------------------
An error has occurred:After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an error dialog box. This is a pgadmin3 client on Windows. The error says:
--------------------------------------------------------------
ERROR: could not access file "$libdir/adminpack": No such file or directory
--------------------------------------------------------------
Brian
Re: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error
От
Albe Laurenz
Дата:
Brian Wong wrote: > After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an > error dialog box. This is a pgadmin3 client on Windows. The error says: > > -------------------------------------------------------------- > An error has occurred: > ERROR: could not access file "$libdir/adminpack": No such file or directory > -------------------------------------------------------------- > > What's strange is that the same upgrade was done on another box and that box doesn't have the same > problem. > > Any one has any idea? I went into Postgresql and I was able to see adminpack's objects still there. You mean the objects were there on the SQL level? That's what I would expect when I see the error message. You should check if the shared object (adminpack.so or adminpack.dll) is in the library directory on the server. Compare with a server where things are working. Yours, Laurenz Albe
I meant I went into there with psql and was able to see the adminpack's objects.
I checked the location of the Postgresql server software(/opt/Postgresql/9.1.9/lib) and couldn't find adminpack.so. On a server for which there's no such an error, I see the same files and those 2 files aren't there either.
These servers were installed/patched the same way, so I don't expect any difference in terms of files and directories...I checked the location of the Postgresql server software(/opt/Postgresql/9.1.9/lib) and couldn't find adminpack.so. On a server for which there's no such an error, I see the same files and those 2 files aren't there either.
Brian
On Tue, Aug 6, 2013 at 12:10 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
You mean the objects were there on the SQL level?Brian Wong wrote:
> After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an
> error dialog box. This is a pgadmin3 client on Windows. The error says:
>
> --------------------------------------------------------------
> An error has occurred:
> ERROR: could not access file "$libdir/adminpack": No such file or directory
> --------------------------------------------------------------
>
> What's strange is that the same upgrade was done on another box and that box doesn't have the same
> problem.
>
> Any one has any idea? I went into Postgresql and I was able to see adminpack's objects still there.
That's what I would expect when I see the error message.
You should check if the shared object (adminpack.so or adminpack.dll) is
in the library directory on the server.
Compare with a server where things are working.
Yours,
Laurenz Albe
Re: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error
От
Albe Laurenz
Дата:
Brian Wong wrote: >>> After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an >>> error dialog box. This is a pgadmin3 client on Windows. The error says: >>> >>> -------------------------------------------------------------- >>> An error has occurred: >>> ERROR: could not access file "$libdir/adminpack": No such file or directory >>> -------------------------------------------------------------- >>> >>> What's strange is that the same upgrade was done on another box and that box doesn't have the same >>> problem. >>> >>> Any one has any idea? I went into Postgresql and I was able to see adminpack's objects still there. >> You mean the objects were there on the SQL level? >> That's what I would expect when I see the error message. >> >> You should check if the shared object (adminpack.so or adminpack.dll) is >> in the library directory on the server. >> Compare with a server where things are working. > I meant I went into there with psql and was able to see the adminpack's objects. That's expected. Otherwise you'd get a message like: ERROR: function whatever() does not exist > I checked the location of the Postgresql server software(/opt/Postgresql/9.1.9/lib) and couldn't find > adminpack.so. On a server for which there's no such an error, I see the same files and those 2 files > aren't there either. > > These servers were installed/patched the same way, so I don't expect any difference in terms of files > and directories... If adminpack.so isn't there, you've got a problem. Which operating system are you on anyway? One explanation why adminpack might work even though the code is gone would be that it was already loaded when the file got removed. Try and restart the server and see if it still works. Yours, Laurenz Albe
I'm on Oracle Enterprise Linux.
The server was already restarted after upgrading from 9.1.1 to 9.1.9. The server comes up just fine. And on either versions on the box(9.1.1 and 9.1.9), adminpack.so isn't there.Brian
On Tue, Aug 6, 2013 at 11:49 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
Brian Wong wrote:
>>> After upgrading postgresql from 9.1.1 to 9.1.9, launching pgadmin3's server status window gives an
>>> error dialog box. This is a pgadmin3 client on Windows. The error says:
>>>
>>> --------------------------------------------------------------
>>> An error has occurred:
>>> ERROR: could not access file "$libdir/adminpack": No such file or directory
>>> --------------------------------------------------------------
>>>
>>> What's strange is that the same upgrade was done on another box and that box doesn't have the same
>>> problem.
>>>
>>> Any one has any idea? I went into Postgresql and I was able to see adminpack's objects still there.
>> You mean the objects were there on the SQL level?
>> That's what I would expect when I see the error message.
>>
>> You should check if the shared object (adminpack.so or adminpack.dll) is
>> in the library directory on the server.
>> Compare with a server where things are working.> I meant I went into there with psql and was able to see the adminpack's objects.That's expected.
Otherwise you'd get a message like:
ERROR: function whatever() does not existIf adminpack.so isn't there, you've got a problem.
> I checked the location of the Postgresql server software(/opt/Postgresql/9.1.9/lib) and couldn't find
> adminpack.so. On a server for which there's no such an error, I see the same files and those 2 files
> aren't there either.
>
> These servers were installed/patched the same way, so I don't expect any difference in terms of files
> and directories...
Which operating system are you on anyway?
One explanation why adminpack might work even though the code is gone
would be that it was already loaded when the file got removed.
Try and restart the server and see if it still works.
Yours,
Laurenz Albe
Re: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error
От
Albe Laurenz
Дата:
Brian Wong wrote: >>>> -------------------------------------------------------------- >>>> An error has occurred: >>>> ERROR: could not access file "$libdir/adminpack": No such file or directory >>>> -------------------------------------------------------------- > I'm on Oracle Enterprise Linux. > > The server was already restarted after upgrading from 9.1.1 to 9.1.9. The server comes up just fine. > And on either versions on the box(9.1.1 and 9.1.9), adminpack.so isn't there. > > I looked on any postgresql box we have, adminpack.so just isn't there anywhere. > > And for some reason, this box is the only box for which pgadmin3 complains about it. Are the objects there on all machines? What do you get for "\dx+ adminpack" in psql? Yours, Laurenz Albe
Actually it is kinda complicated:
dev(9.1.9, for which pgadmin3 complains w/ that error)postgres=# \dx+ adminpack
Objects in extension "adminpack"
Object Description
-------------------------------------------
function pg_file_length(text)
function pg_file_read(text,bigint,bigint)
function pg_file_rename(text,text)
function pg_file_rename(text,text,text)
function pg_file_unlink(text)
function pg_file_write(text,text,boolean)
function pg_logdir_ls()
function pg_logfile_rotate()
(8 rows)
postgres=# \dx+ adminpack
Did not find any extension named "adminpack".
postgres=# \dx+ adminpack
Did not find any extension named "adminpack".
Brian
On Fri, Aug 9, 2013 at 12:27 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
Brian Wong wrote:
>>>> --------------------------------------------------------------
>>>> An error has occurred:
>>>> ERROR: could not access file "$libdir/adminpack": No such file or directory
>>>> --------------------------------------------------------------> I'm on Oracle Enterprise Linux.Are the objects there on all machines?
>
> The server was already restarted after upgrading from 9.1.1 to 9.1.9. The server comes up just fine.
> And on either versions on the box(9.1.1 and 9.1.9), adminpack.so isn't there.
>
> I looked on any postgresql box we have, adminpack.so just isn't there anywhere.
>
> And for some reason, this box is the only box for which pgadmin3 complains about it.
What do you get for "\dx+ adminpack" in psql?
Yours,
Laurenz Albe
Any one has any clue how to fix this? ~ Brian
On Mon, Aug 12, 2013 at 1:47 PM, Brian Wong <bwong@imageworks.com> wrote:
Not sure what created these differences, but I used the same procedures to set them up. But these nodes went through different patches/upgrades, so maybe that's why.prod(9.1.1)dw(9.1.9)Actually it is kinda complicated:dev(9.1.9, for which pgadmin3 complains w/ that error)
postgres=# \dx+ adminpack
Objects in extension "adminpack"
Object Description
-------------------------------------------
function pg_file_length(text)
function pg_file_read(text,bigint,bigint)
function pg_file_rename(text,text)
function pg_file_rename(text,text,text)
function pg_file_unlink(text)
function pg_file_write(text,text,boolean)
function pg_logdir_ls()
function pg_logfile_rotate()
(8 rows)
postgres=# \dx+ adminpack
Did not find any extension named "adminpack".
postgres=# \dx+ adminpack
Did not find any extension named "adminpack".
BrianOn Fri, Aug 9, 2013 at 12:27 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:Brian Wong wrote:
>>>> --------------------------------------------------------------
>>>> An error has occurred:
>>>> ERROR: could not access file "$libdir/adminpack": No such file or directory
>>>> --------------------------------------------------------------> I'm on Oracle Enterprise Linux.Are the objects there on all machines?
>
> The server was already restarted after upgrading from 9.1.1 to 9.1.9. The server comes up just fine.
> And on either versions on the box(9.1.1 and 9.1.9), adminpack.so isn't there.
>
> I looked on any postgresql box we have, adminpack.so just isn't there anywhere.
>
> And for some reason, this box is the only box for which pgadmin3 complains about it.
What do you get for "\dx+ adminpack" in psql?
Yours,
Laurenz Albe
Brian Wong <bwong@imageworks.com> writes: > Any one has any clue how to fix this? ~ Brian Well, you don't have adminpack installed in two out of those three databases. Does it show up in the pg_available_extensions view? If so, you just need "CREATE EXTENSION adminpack". If not, you probably forgot to install the postgresql-contrib package (or local equivalent). regards, tom lane