Thread: [pgadmin-support] 4th Try: pgadmin4 install, launch fail

Please don't take my note as complaint; you guys are a tremendous asset
to the pg world. pgadmin3 has been brilliant for me.


This is my 4th attempt to install and launch pgadmin4.

I started with a clean VM Fedora 25.

I installed the pgdg yum repo.

I installed pgadmin4-v1. No issues.

I followed the notes on pgadmin 4.1.1 Documentation Getting Started,
created config_local.py.

The stuff below is what happened.



ran python setup.py  - fail. (note, the clean install put it in
python3.5 - why are we seeing 2.7 below?)

python setup.py
Traceback (most recent call last):
  File "setup.py", line 21, in <module>
    from flask import Flask
  File "/usr/lib/python2.7/site-packages/flask/__init__.py", line 17,
in <module>
    from werkzeug.exceptions import abort
ImportError: No module named werkzeug.exceptions

>> I had manually installed Flash due to a previous error, but the
above then occurred.


ran pgAdmin4.py  - fail.

[xxxxxxxx pgadmin4-web]$ ./pgAdmin4.py
./pgAdmin4.py: line 12: $'This is the main application entry point for pgAdmin 4. If running on\na webserver, this will
providethe WSGI interface, otherwise, we\'re going\nto start a web server.': command not found
 
./pgAdmin4.py: line 14: import: command not found
./pgAdmin4.py: line 15: import: command not found
./pgAdmin4.py: line 19: syntax error near unexpected token `('
./pgAdmin4.py: line 19: `root = os.path.dirname(os.path.realpath(__file__))'


I tried simply launching the executable in the run dir, but it could not find pgAdmin4.py. I altered the .ini file to
pointexactly to the dir where pgAgmin4.py is, but same error.
 

I see similar feedback when searching for ideas.


Regards,

Stan

Hi

On Mon, Jan 30, 2017 at 1:23 AM, stancs3 <scruise56@gmail.com> wrote:
> Please don't take my note as complaint; you guys are a tremendous asset
> to the pg world. pgadmin3 has been brilliant for me.
>
>
> This is my 4th attempt to install and launch pgadmin4.
>
> I started with a clean VM Fedora 25.
>
> I installed the pgdg yum repo.
>
> I installed pgadmin4-v1. No issues.
>
> I followed the notes on pgadmin 4.1.1 Documentation Getting Started,
> created config_local.py.
>
> The stuff below is what happened.

Note that the RPMs are still a WIP at this point, but...

> ran python setup.py  - fail. (note, the clean install put it in
> python3.5 - why are we seeing 2.7 below?)
>
> python setup.py
> Traceback (most recent call last):
>   File "setup.py", line 21, in <module>
>     from flask import Flask
>   File "/usr/lib/python2.7/site-packages/flask/__init__.py", line 17,
> in <module>
>     from werkzeug.exceptions import abort
> ImportError: No module named werkzeug.exceptions

Presumably "python" on your system points to a 2.7 interpreter. You
should try "python3 setup.py" or whatever is appropriate.

>>> I had manually installed Flash due to a previous error, but the
> above then occurred.
>
>
> ran pgAdmin4.py  - fail.
>
> [xxxxxxxx pgadmin4-web]$ ./pgAdmin4.py
> ./pgAdmin4.py: line 12: $'This is the main application entry point for pgAdmin 4. If running on\na webserver, this
willprovide the WSGI interface, otherwise, we\'re going\nto start a web server.': command not found
 
> ./pgAdmin4.py: line 14: import: command not found
> ./pgAdmin4.py: line 15: import: command not found
> ./pgAdmin4.py: line 19: syntax error near unexpected token `('
> ./pgAdmin4.py: line 19: `root = os.path.dirname(os.path.realpath(__file__))'

You need to run "python3 pgAdmin4.py" as there's no hashbang line in
the script (which was intentional, but I don't suppose it would hurt
to add one).

> I tried simply launching the executable in the run dir, but it could not find pgAdmin4.py. I altered the .ini file to
pointexactly to the dir where pgAgmin4.py is, but same error.
 

The .ini file is for configuring the desktop runtime. It won't have
any effect on the Python code.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Many thanks for the reply Dave! I feel a bit like that message that
Firefox diplays after crashing, the embarrassment one.

Anyway here is what I did:

xxxxxxxxxx pgadmin4-web]$ python3 setup.py
pgAdmin 4 - Application Initialisation
======================================


The configuration database - '/home/xxxxxx/.pgadmin/pgadmin4.db' does
not exist.
Entering initial setup mode...
NOTE: Configuring authentication for DESKTOP mode.

The configuration database has been created at
/home/xxxxxx/.pgadmin/pgadmin4.db

xxxxxxxxx pgadmin4-web]$ python3 ./pgAdmin4.py
Starting pgAdmin 4. Please navigate to http://localhost:5050 in your
browser.

>> And it works nicely in the web browser <<

Maybe I should just be happy, but I was trying to get it working as a
desktop app.

I tried changing the exec in the desktop app launcher to be prefixed
with python3 but that did not help. The error is:

"An error occurred initialising the application server:

Failed to locate pgAdmin5.py, terminating server thread."

I feel I am so close .... is there some further advice on this last
part.


Thanks again,

Stan


On Mon, 2017-01-30 at 10:10 +0000, Dave Page wrote:
> Hi
> 
> On Mon, Jan 30, 2017 at 1:23 AM, stancs3 <scruise56@gmail.com> wrote:
> > 
> > Please don't take my note as complaint; you guys are a tremendous
> > asset
> > to the pg world. pgadmin3 has been brilliant for me.
> > 
> > 
> > This is my 4th attempt to install and launch pgadmin4.
> > 
> > I started with a clean VM Fedora 25.
> > 
> > I installed the pgdg yum repo.
> > 
> > I installed pgadmin4-v1. No issues.
> > 
> > I followed the notes on pgadmin 4.1.1 Documentation Getting
> > Started,
> > created config_local.py.
> > 
> > The stuff below is what happened.
> Note that the RPMs are still a WIP at this point, but...
> 
> > 
> > ran python setup.py  - fail. (note, the clean install put it in
> > python3.5 - why are we seeing 2.7 below?)
> > 
> > python setup.py
> > Traceback (most recent call last):
> >   File "setup.py", line 21, in <module>
> >     from flask import Flask
> >   File "/usr/lib/python2.7/site-packages/flask/__init__.py", line
> > 17,
> > in <module>
> >     from werkzeug.exceptions import abort
> > ImportError: No module named werkzeug.exceptions
> Presumably "python" on your system points to a 2.7 interpreter. You
> should try "python3 setup.py" or whatever is appropriate.
> 
> > 
> > > 
> > > > 
> > > > I had manually installed Flash due to a previous error, but the
> > above then occurred.
> > 
> > 
> > ran pgAdmin4.py  - fail.
> > 
> > [xxxxxxxx pgadmin4-web]$ ./pgAdmin4.py
> > ./pgAdmin4.py: line 12: $'This is the main application entry point
> > for pgAdmin 4. If running on\na webserver, this will provide the
> > WSGI interface, otherwise, we\'re going\nto start a web server.':
> > command not found
> > ./pgAdmin4.py: line 14: import: command not found
> > ./pgAdmin4.py: line 15: import: command not found
> > ./pgAdmin4.py: line 19: syntax error near unexpected token `('
> > ./pgAdmin4.py: line 19: `root =
> > os.path.dirname(os.path.realpath(__file__))'
> You need to run "python3 pgAdmin4.py" as there's no hashbang line in
> the script (which was intentional, but I don't suppose it would hurt
> to add one).
> 
> > 
> > I tried simply launching the executable in the run dir, but it
> > could not find pgAdmin4.py. I altered the .ini file to point
> > exactly to the dir where pgAgmin4.py is, but same error.
> The .ini file is for configuring the desktop runtime. It won't have
> any effect on the Python code.
> 

Hi,

On Mon, 2017-01-30 at 15:34 -0700, stancs3 wrote:
> "An error occurred initialising the application server:
>
> Failed to locate pgAdmin5.py, terminating server thread."
>
> I feel I am so close .... is there some further advice on this last
> part.

Typo somewhere? It should be pgAdmin4.py

Regards,
--
Devrim Gündüz
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

If I launch via:

/usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py

it launches the web app, and says to got to localhost:5050. This works.


If I launch via the Desktop app launcher, it sends the command:

/usr/pgadmin4-v1/runtime/pgAdmin4

This results in the error in email below. I have tried all combinations
of different commands in the launcher, even the first one above, and it
produces the same error. The runtime pgAdmin4 does not have a .py
extension. If I run the runtime/pgAdmin4 directly, same error.


If there was some way to run: 

/usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py, and have it
launch the desktop version, that would do it.


Stan



On Tue, 2017-01-31 at 01:47 +0300, Devrim Gündüz wrote:
> Hi,
> 
> On Mon, 2017-01-30 at 15:34 -0700, stancs3 wrote:
> > 
> > "An error occurred initialising the application server:
> > 
> > Failed to locate pgAdmin5.py, terminating server thread."
> > 
> > I feel I am so close .... is there some further advice on this last
> > part.
> Typo somewhere? It should be pgAdmin4.py
> 
> Regards,

On Tue, Jan 31, 2017 at 12:39 AM, stancs3 <scruise56@gmail.com> wrote:
>
> If I launch via:
>
> /usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py
>
> it launches the web app, and says to got to localhost:5050. This works.
>
>
> If I launch via the Desktop app launcher, it sends the command:
>
> /usr/pgadmin4-v1/runtime/pgAdmin4
>
> This results in the error in email below. I have tried all combinations
> of different commands in the launcher, even the first one above, and it
> produces the same error. The runtime pgAdmin4 does not have a .py
> extension. If I run the runtime/pgAdmin4 directly, same error.
>
>
> If there was some way to run:
>
> /usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py, and have it
> launch the desktop version, that would do it.

I assume the runtime is failing and popping up the dialog box asking
for the python and app paths. What are in those fields?



-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attached is the desktop launcher copied from /usr/share/applications/.
This was created from the install.

Error resulting:

"An error occurred initialising the application server:

Failed to locate pgAdmin5.py, terminating server thread."


This does not give you much further info. I can provide more debug info
if it will help; I am game to be coached on what/how to collect.

Your previous comment re a WIP for repo install: if it would simply be
better if I was to go the compile route, I am fine with this. I did it
for pgadmin3 a few months ago ... and it was good. On the other hand, a
nice repo install is likely the goal for us user dudes :).


Stan


On Tue, 2017-01-31 at 09:15 +0000, Dave Page wrote:
> On Tue, Jan 31, 2017 at 12:39 AM, stancs3 <scruise56@gmail.com>
> wrote:
> > 
> > 
> > If I launch via:
> > 
> > /usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py
> > 
> > it launches the web app, and says to got to localhost:5050. This
> > works.
> > 
> > 
> > If I launch via the Desktop app launcher, it sends the command:
> > 
> > /usr/pgadmin4-v1/runtime/pgAdmin4
> > 
> > This results in the error in email below. I have tried all
> > combinations
> > of different commands in the launcher, even the first one above,
> > and it
> > produces the same error. The runtime pgAdmin4 does not have a .py
> > extension. If I run the runtime/pgAdmin4 directly, same error.
> > 
> > 
> > If there was some way to run:
> > 
> > /usr/lib/python3.5/site-packages/pgadmin4-web/pgAdmin4.py, and have
> > it
> > launch the desktop version, that would do it.
> I assume the runtime is failing and popping up the dialog box asking
> for the python and app paths. What are in those fields?
> 
> 
> 
-- 
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support

Hi

On Tue, Jan 31, 2017 at 6:49 PM, stancs3 <scruise56@gmail.com> wrote:
> Attached is the desktop launcher copied from /usr/share/applications/.
> This was created from the install.
>
> Error resulting:
>
> "An error occurred initialising the application server:
>
> Failed to locate pgAdmin5.py, terminating server thread."

Does it really say pgAdmin5.py? If so, that's not our code.

> This does not give you much further info. I can provide more debug info
> if it will help; I am game to be coached on what/how to collect.

When you click OK on the message above (assuming it does actually say
pgAdmin4.py, not pgAdmin5.py), it should prompt you for the paths.
Does it not do that?

> Your previous comment re a WIP for repo install: if it would simply be
> better if I was to go the compile route, I am fine with this. I did it
> for pgadmin3 a few months ago ... and it was good. On the other hand, a
> nice repo install is likely the goal for us user dudes :).

Devrim and I will be spending some time, probably next week, fixing
the RPMs. We've had a small re-org at work which make it much easier
to allocate some of his time for this :-).

Unfortunately I doubt the compile route will help here. The Python
code and the runtime are independent pieces of code - the runtime
should locate the Python code based on it's configuration, not any
build settings.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Yes that's a typo (the only time I didn't do a copy/paste).

The sequence is:

1. Make sure no pgAdmin4 processes are running.
2. Make sure no python processes are running.
3. Launch pgAdmin4 from Applications menu.
4. pgAdmin4 splash appears - the nice blue one.
5. The Fatal Error window appears with text below with pgAdmin4.py
6. Note that a process is running called pgAdmin4 and showing a command
of: /usr/pgAdmin4-v1/runtime/pgAdmin4. This aligns with what is coded
into /usr/share/applications/pgAdmin4-v1.desktop. This is stock from
the install.
7. Note that no python process is running. (as one would expect given
the error message).
8. Then I hit the OK button in the Fatal Error window.
9. It all goes away, including the process in step 6 above.
10. When this happens an abrt-hook-ccpp log is generated, which I can
send if it will help. 
11. I confirm that there is no prompt for paths.


My sincere apologies for the typo below; it is unhelpful to add errors
into debug data.

Anyway, I am at your service for further debug attempts.


Stan



On Wed, 2017-02-01 at 09:25 +0000, Dave Page wrote:
> Hi
> 
> On Tue, Jan 31, 2017 at 6:49 PM, stancs3 <scruise56@gmail.com> wrote:
> > 
> > Attached is the desktop launcher copied from
> > /usr/share/applications/.
> > This was created from the install.
> > 
> > Error resulting:
> > 
> > "An error occurred initialising the application server:
> > 
> > Failed to locate pgAdmin5.py, terminating server thread."
> Does it really say pgAdmin5.py? If so, that's not our code.
> 
> > 
> > This does not give you much further info. I can provide more debug
> > info
> > if it will help; I am game to be coached on what/how to collect.
> When you click OK on the message above (assuming it does actually say
> pgAdmin4.py, not pgAdmin5.py), it should prompt you for the paths.
> Does it not do that?
> 
> > 
> > Your previous comment re a WIP for repo install: if it would simply
> > be
> > better if I was to go the compile route, I am fine with this. I did
> > it
> > for pgadmin3 a few months ago ... and it was good. On the other
> > hand, a
> > nice repo install is likely the goal for us user dudes :).
> Devrim and I will be spending some time, probably next week, fixing
> the RPMs. We've had a small re-org at work which make it much easier
> to allocate some of his time for this :-).
> 
> Unfortunately I doubt the compile route will help here. The Python
> code and the runtime are independent pieces of code - the runtime
> should locate the Python code based on it's configuration, not any
> build settings.
> 

Just an additional note:

I am not a mousey-clicky guy and insist on the Application launcher to
work. Any CLI is great in fact much better. I am only harping on this
because the sequence of use from a stock install will tell something
about what is going on.

And of course it will be nice to see the desktop version :).


On Wed, 2017-02-01 at 12:07 -0700, stancs3 wrote:
> Yes that's a typo (the only time I didn't do a copy/paste).
> 
> The sequence is:
> 
> 1. Make sure no pgAdmin4 processes are running.
> 2. Make sure no python processes are running.
> 3. Launch pgAdmin4 from Applications menu.
> 4. pgAdmin4 splash appears - the nice blue one.
> 5. The Fatal Error window appears with text below with pgAdmin4.py
> 6. Note that a process is running called pgAdmin4 and showing a
> command
> of: /usr/pgAdmin4-v1/runtime/pgAdmin4. This aligns with what is coded
> into /usr/share/applications/pgAdmin4-v1.desktop. This is stock from
> the install.
> 7. Note that no python process is running. (as one would expect given
> the error message).
> 8. Then I hit the OK button in the Fatal Error window.
> 9. It all goes away, including the process in step 6 above.
> 10. When this happens an abrt-hook-ccpp log is generated, which I can
> send if it will help. 
> 11. I confirm that there is no prompt for paths.
> 
> 
> My sincere apologies for the typo below; it is unhelpful to add
> errors
> into debug data.
> 
> Anyway, I am at your service for further debug attempts.
> 
> 
> Stan
> 
> 
> 
> On Wed, 2017-02-01 at 09:25 +0000, Dave Page wrote:
> > 
> > Hi
> > 
> > On Tue, Jan 31, 2017 at 6:49 PM, stancs3 <scruise56@gmail.com>
> > wrote:
> > > 
> > > 
> > > Attached is the desktop launcher copied from
> > > /usr/share/applications/.
> > > This was created from the install.
> > > 
> > > Error resulting:
> > > 
> > > "An error occurred initialising the application server:
> > > 
> > > Failed to locate pgAdmin5.py, terminating server thread."
> > Does it really say pgAdmin5.py? If so, that's not our code.
> > 
> > > 
> > > 
> > > This does not give you much further info. I can provide more
> > > debug
> > > info
> > > if it will help; I am game to be coached on what/how to collect.
> > When you click OK on the message above (assuming it does actually
> > say
> > pgAdmin4.py, not pgAdmin5.py), it should prompt you for the paths.
> > Does it not do that?
> > 
> > > 
> > > 
> > > Your previous comment re a WIP for repo install: if it would
> > > simply
> > > be
> > > better if I was to go the compile route, I am fine with this. I
> > > did
> > > it
> > > for pgadmin3 a few months ago ... and it was good. On the other
> > > hand, a
> > > nice repo install is likely the goal for us user dudes :).
> > Devrim and I will be spending some time, probably next week, fixing
> > the RPMs. We've had a small re-org at work which make it much
> > easier
> > to allocate some of his time for this :-).
> > 
> > Unfortunately I doubt the compile route will help here. The Python
> > code and the runtime are independent pieces of code - the runtime
> > should locate the Python code based on it's configuration, not any
> > build settings.
> > 

FYI - this hasn't been forgotten. Devrim and I were travelling most of
last week, and have PostgreSQL releases to deal with this week. We're
planning to meet tomorrow to work on the RPMs.

On Wed, Feb 1, 2017 at 7:11 PM, stancs3 <scruise56@gmail.com> wrote:
> Just an additional note:
>
> I am not a mousey-clicky guy and insist on the Application launcher to
> work. Any CLI is great in fact much better. I am only harping on this
> because the sequence of use from a stock install will tell something
> about what is going on.
>
> And of course it will be nice to see the desktop version :).
>
>
> On Wed, 2017-02-01 at 12:07 -0700, stancs3 wrote:
>> Yes that's a typo (the only time I didn't do a copy/paste).
>>
>> The sequence is:
>>
>> 1. Make sure no pgAdmin4 processes are running.
>> 2. Make sure no python processes are running.
>> 3. Launch pgAdmin4 from Applications menu.
>> 4. pgAdmin4 splash appears - the nice blue one.
>> 5. The Fatal Error window appears with text below with pgAdmin4.py
>> 6. Note that a process is running called pgAdmin4 and showing a
>> command
>> of: /usr/pgAdmin4-v1/runtime/pgAdmin4. This aligns with what is coded
>> into /usr/share/applications/pgAdmin4-v1.desktop. This is stock from
>> the install.
>> 7. Note that no python process is running. (as one would expect given
>> the error message).
>> 8. Then I hit the OK button in the Fatal Error window.
>> 9. It all goes away, including the process in step 6 above.
>> 10. When this happens an abrt-hook-ccpp log is generated, which I can
>> send if it will help.
>> 11. I confirm that there is no prompt for paths.
>>
>>
>> My sincere apologies for the typo below; it is unhelpful to add
>> errors
>> into debug data.
>>
>> Anyway, I am at your service for further debug attempts.
>>
>>
>> Stan
>>
>>
>>
>> On Wed, 2017-02-01 at 09:25 +0000, Dave Page wrote:
>> >
>> > Hi
>> >
>> > On Tue, Jan 31, 2017 at 6:49 PM, stancs3 <scruise56@gmail.com>
>> > wrote:
>> > >
>> > >
>> > > Attached is the desktop launcher copied from
>> > > /usr/share/applications/.
>> > > This was created from the install.
>> > >
>> > > Error resulting:
>> > >
>> > > "An error occurred initialising the application server:
>> > >
>> > > Failed to locate pgAdmin5.py, terminating server thread."
>> > Does it really say pgAdmin5.py? If so, that's not our code.
>> >
>> > >
>> > >
>> > > This does not give you much further info. I can provide more
>> > > debug
>> > > info
>> > > if it will help; I am game to be coached on what/how to collect.
>> > When you click OK on the message above (assuming it does actually
>> > say
>> > pgAdmin4.py, not pgAdmin5.py), it should prompt you for the paths.
>> > Does it not do that?
>> >
>> > >
>> > >
>> > > Your previous comment re a WIP for repo install: if it would
>> > > simply
>> > > be
>> > > better if I was to go the compile route, I am fine with this. I
>> > > did
>> > > it
>> > > for pgadmin3 a few months ago ... and it was good. On the other
>> > > hand, a
>> > > nice repo install is likely the goal for us user dudes :).
>> > Devrim and I will be spending some time, probably next week, fixing
>> > the RPMs. We've had a small re-org at work which make it much
>> > easier
>> > to allocate some of his time for this :-).
>> >
>> > Unfortunately I doubt the compile route will help here. The Python
>> > code and the runtime are independent pieces of code - the runtime
>> > should locate the Python code based on it's configuration, not any
>> > build settings.
>> >



-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Great, thanks Dave. I figured I would let it rest to allow you to
prioritize. 

As indicated before I am willing to do debug cases if it will help. The
one key fact is that since I started trying to launch a desktop
version, it has not been successful even once. Again, not a complaint,
just a data point; if I am the only one then it must be my problem
staring me in the face - wouldn't be the first time .....

Stan

On Thu, 2017-02-09 at 09:59 +0000, Dave Page wrote:
> FYI - this hasn't been forgotten. Devrim and I were travelling most
> of
> last week, and have PostgreSQL releases to deal with this week. We're
> planning to meet tomorrow to work on the RPMs.
> 
> On Wed, Feb 1, 2017 at 7:11 PM, stancs3 <scruise56@gmail.com> wrote:
> > 
> > Just an additional note:
> > 
> > I am not a mousey-clicky guy and insist on the Application launcher
> > to
> > work. Any CLI is great in fact much better. I am only harping on
> > this
> > because the sequence of use from a stock install will tell
> > something
> > about what is going on.
> > 
> > And of course it will be nice to see the desktop version :).
> > 
> > 
> > On Wed, 2017-02-01 at 12:07 -0700, stancs3 wrote:
> > > 
> > > Yes that's a typo (the only time I didn't do a copy/paste).
> > > 
> > > The sequence is:
> > > 
> > > 1. Make sure no pgAdmin4 processes are running.
> > > 2. Make sure no python processes are running.
> > > 3. Launch pgAdmin4 from Applications menu.
> > > 4. pgAdmin4 splash appears - the nice blue one.
> > > 5. The Fatal Error window appears with text below with
> > > pgAdmin4.py
> > > 6. Note that a process is running called pgAdmin4 and showing a
> > > command
> > > of: /usr/pgAdmin4-v1/runtime/pgAdmin4. This aligns with what is
> > > coded
> > > into /usr/share/applications/pgAdmin4-v1.desktop. This is stock
> > > from
> > > the install.
> > > 7. Note that no python process is running. (as one would expect
> > > given
> > > the error message).
> > > 8. Then I hit the OK button in the Fatal Error window.
> > > 9. It all goes away, including the process in step 6 above.
> > > 10. When this happens an abrt-hook-ccpp log is generated, which I
> > > can
> > > send if it will help.
> > > 11. I confirm that there is no prompt for paths.
> > > 
> > > 
> > > My sincere apologies for the typo below; it is unhelpful to add
> > > errors
> > > into debug data.
> > > 
> > > Anyway, I am at your service for further debug attempts.
> > > 
> > > 
> > > Stan
> > > 
> > > 
> > > 
> > > On Wed, 2017-02-01 at 09:25 +0000, Dave Page wrote:
> > > > 
> > > > 
> > > > Hi
> > > > 
> > > > On Tue, Jan 31, 2017 at 6:49 PM, stancs3 <scruise56@gmail.com>
> > > > wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > Attached is the desktop launcher copied from
> > > > > /usr/share/applications/.
> > > > > This was created from the install.
> > > > > 
> > > > > Error resulting:
> > > > > 
> > > > > "An error occurred initialising the application server:
> > > > > 
> > > > > Failed to locate pgAdmin5.py, terminating server thread."
> > > > Does it really say pgAdmin5.py? If so, that's not our code.
> > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > This does not give you much further info. I can provide more
> > > > > debug
> > > > > info
> > > > > if it will help; I am game to be coached on what/how to
> > > > > collect.
> > > > When you click OK on the message above (assuming it does
> > > > actually
> > > > say
> > > > pgAdmin4.py, not pgAdmin5.py), it should prompt you for the
> > > > paths.
> > > > Does it not do that?
> > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Your previous comment re a WIP for repo install: if it would
> > > > > simply
> > > > > be
> > > > > better if I was to go the compile route, I am fine with this.
> > > > > I
> > > > > did
> > > > > it
> > > > > for pgadmin3 a few months ago ... and it was good. On the
> > > > > other
> > > > > hand, a
> > > > > nice repo install is likely the goal for us user dudes :).
> > > > Devrim and I will be spending some time, probably next week,
> > > > fixing
> > > > the RPMs. We've had a small re-org at work which make it much
> > > > easier
> > > > to allocate some of his time for this :-).
> > > > 
> > > > Unfortunately I doubt the compile route will help here. The
> > > > Python
> > > > code and the runtime are independent pieces of code - the
> > > > runtime
> > > > should locate the Python code based on it's configuration, not
> > > > any
> > > > build settings.
> > > > 
> 
> 

Hi

On Sat, Feb 11, 2017 at 6:10 PM, stancs3 <scruise56@gmail.com> wrote:
> Great, thanks Dave. I figured I would let it rest to allow you to
> prioritize.
>
> As indicated before I am willing to do debug cases if it will help. The
> one key fact is that since I started trying to launch a desktop
> version, it has not been successful even once. Again, not a complaint,
> just a data point; if I am the only one then it must be my problem
> staring me in the face - wouldn't be the first time .....

OK, so I got it working on F25 (sorry it wasn't earlier - this week
has been crazy busy).

Until the RPMs are updated, here's what you can do:

- Install the PGDG 9.6 repo:
https://download.postgresql.org/pub/repos/yum/9.6/fedora/fedora-25-x86_64/pgdg-fedora96-9.6-3.noarch.rpm

- Edit /etc/yum.repos.d/pgdg-96-fedora.repo and set all repos to have
"enabled=0" except for pgdg96-updates-testing, which should have
"enabled=1"

- As root, run:

dnf install pgadmin4-v1 python3-htmlmin

- As root, run:

cp -r /etc/pgadmin /etc/xdg/

On a clean installation of F25, I could then run pgAdmin in the
desktop runtime, either from the UI or by running /usr/bin/pgadmin4.

However, for reasons as-yet unknown to me, the UI seems to be
defaulting to Chinese. I suspect this is something to do with the way
Qt may have been built on this platform. Anyway, that can be easily
fixed by running this as root:

cat << EOF > /usr/lib/python3.5/site-packages/pgadmin4-web/config_local.py
LANGUAGES = {   'en': 'English'
}
EOF

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Many thanks! I will get to testing it very soon. 

I just got some pdns servers working (pg backend; and therefore a nice
pgadmin3 way of verifying what's going on). And, I just got my first
'shiny' free-ipa server up. Lot's to keep busy with.


Stan


On Fri, 2017-02-17 at 13:26 +0000, Dave Page wrote:
> Hi
> 
> On Sat, Feb 11, 2017 at 6:10 PM, stancs3 <scruise56@gmail.com> wrote:
> > 
> > Great, thanks Dave. I figured I would let it rest to allow you to
> > prioritize.
> > 
> > As indicated before I am willing to do debug cases if it will help.
> > The
> > one key fact is that since I started trying to launch a desktop
> > version, it has not been successful even once. Again, not a
> > complaint,
> > just a data point; if I am the only one then it must be my problem
> > staring me in the face - wouldn't be the first time .....
> OK, so I got it working on F25 (sorry it wasn't earlier - this week
> has been crazy busy).
> 
> Until the RPMs are updated, here's what you can do:
> 
> - Install the PGDG 9.6 repo:
> https://download.postgresql.org/pub/repos/yum/9.6/fedora/fedora-25-x8
> 6_64/pgdg-fedora96-9.6-3.noarch.rpm
> 
> - Edit /etc/yum.repos.d/pgdg-96-fedora.repo and set all repos to have
> "enabled=0" except for pgdg96-updates-testing, which should have
> "enabled=1"
> 
> - As root, run:
> 
> dnf install pgadmin4-v1 python3-htmlmin
> 
> - As root, run:
> 
> cp -r /etc/pgadmin /etc/xdg/
> 
> On a clean installation of F25, I could then run pgAdmin in the
> desktop runtime, either from the UI or by running /usr/bin/pgadmin4.
> 
> However, for reasons as-yet unknown to me, the UI seems to be
> defaulting to Chinese. I suspect this is something to do with the way
> Qt may have been built on this platform. Anyway, that can be easily
> fixed by running this as root:
> 
> cat << EOF > /usr/lib/python3.5/site-packages/pgadmin4-
> web/config_local.py
> LANGUAGES = {
>     'en': 'English'
> }
> EOF
>