From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Peter Juhasz <pjuhasz(at)uhusystems(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
Subject: | Re: PgAdmin4 STILL not usable when installed from RPMs on Fedora linux |
Date: | 2016-11-23 15:36:36 |
Message-ID: | CA+OCxoy0kiSvXj=VKzH93my3jiXimVrPCUX8OyTS8gngR0eJ3g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Adding Devrim...
On Wed, Nov 23, 2016 at 1:12 PM, Peter Juhasz <pjuhasz(at)uhusystems(dot)com> wrote:
> Dear PgAdmin4 maintainers,
>
> I've installed the latest pgadmin4-v1 package from the PGDG repository.
> Unfortunately, it still does not work.
>
> Now (as oppossed to the previous version of the package) there is a
> pgadmin4 binary in the path, starting it results in the familiar "An
> error occurred initialising the application server: Failed to locate
> pgAdmin4.py, terminating server thread." message box and (usually) a
> segmentation fault.
>
> The reason for this is that the application does not know where to find
> the python server backend. On my machine, it tries the following
> locations:
>
> stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
> stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
> stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
>
> Not knowing the correct path it tries /usr/pgadmin4-
> v1/runtime/pgAdmin4.py and even /pgAdmin4.py, then eventually gives up.
>
> The package installs a pgadmin4.ini next to the pgAdmin4 binary,
> containing the correct path, but this file is never accessed.
>
> The reason for this is that QSettings is used in the pgadmin4 program
> with default settings, which causes Qt to try the locations mentioned
> above. This behavior is documented at e.g. http://doc.qt.io/archives/qt
> -4.7/qsettings.html#platform-specific-notes .
>
> Something is still wrong, though, because the application does not
> start even after manually copying the provided pgadmin4.ini to one of
> the previously mentioned locations.
>
> I'd also like to mention that directory names with spaces and capital
> letters are discouraged (to put it lightly) in Linux.
>
>
> I can access the webapp from a browser after running "systemctl start
> pgadmin4-v1.service", but
> - this is not documented (AFAIK),
> - this is not something I want to do,
> - for users that don't have root permissions this might not be an
> option.
>
> Best regards,
> Peter Juhasz
>
>
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Murawski | 2016-11-23 17:43:45 | Re: pgAdmin 4.x vs pgAdmin 3.x |
Previous Message | Tomek | 2016-11-23 14:54:50 | pgAdmin 4.x vs pgAdmin 3.x |