Thread: pgAdmin 4 v1.6 Released!

pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

Notable changes in this release include:

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

For more information, checkout the online documentation, and of course the download page: 




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

Re: pgAdmin 4 v1.6 Released!

From
Anthony DeBarros
Date:
Congrats to the team. This one seems like a milestone! 

To the Pivotal team: Great work on the design!


On July 13, 2017 at 11:18:05 AM, Dave Page (dpage@pgadmin.org) wrote:

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

Notable changes in this release include:

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

For more information, checkout the online documentation, and of course the download page: 




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

Re: pgAdmin 4 v1.6 Released!

From
Anthony DeBarros
Date:
Congrats to the team. This one seems like a milestone! 

To the Pivotal team: Great work on the design!


On July 13, 2017 at 11:18:05 AM, Dave Page (dpage@pgadmin.org) wrote:

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

Notable changes in this release include:

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

For more information, checkout the online documentation, and of course the download page: 




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

RE: pgAdmin 4 v1.6 Released!

From
"Lazaro Garcia"
Date:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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

RE: pgAdmin 4 v1.6 Released!

From
"Lazaro Garcia"
Date:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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

Re: pgAdmin 4 v1.6 Released!

From
Neel Patel
Date:
Hi,


Thanks,
Neel Patel

On Jul 14, 2017 5:31 AM, "Shira Bezalel" <shira@sfei.org> wrote:
I downloaded the Windows pgAdmin 1.6 version, and after launching it, it simply shows a black display. My colleague also on Windows 10 had the same experience. 

Does this sound like a known problem?

It is not an issue with 1.6. This is due to previous "ActiveQt" testing build using different zoom level.
To resolve the issue press Ctrl 0.


Shira

On Thu, Jul 13, 2017 at 11:18 AM, Lazaro Garcia <lazaro3487@gmail.com> wrote:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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


​ 
 

Re: pgAdmin 4 v1.6 Released!

From
Neel Patel
Date:
Hi,


Thanks,
Neel Patel

On Jul 14, 2017 5:31 AM, "Shira Bezalel" <shira@sfei.org> wrote:
I downloaded the Windows pgAdmin 1.6 version, and after launching it, it simply shows a black display. My colleague also on Windows 10 had the same experience. 

Does this sound like a known problem?

It is not an issue with 1.6. This is due to previous "ActiveQt" testing build using different zoom level.
To resolve the issue press Ctrl 0.


Shira

On Thu, Jul 13, 2017 at 11:18 AM, Lazaro Garcia <lazaro3487@gmail.com> wrote:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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


​ 
 

Re: pgAdmin 4 v1.6 Released!

From
Darren Duncan
Date:
This is just speculation, but could any vestiges of the old version's server 
still be running and are interfering with the new one, such as by trying to use 
the same server port?  I'd say make sure the old version is shut down first? 
Restart Windows if necessary. -- Darren Duncan

On 2017-07-13 11:53 PM, Pawel Hadam wrote:
> Hi,
>
> I have also installed "pgadmin4-1.6-x86.exe" on Windows 10 PRO (AMD
> FX, 6 cores, 16 GB RAM, SSD) and tried to run it. After 1min 58 sec I
> got a message saying "The application server could not be contacted".
>
> pgAdmin 4 v 1.5 was starting successfully in 55-60 sec. before I did
> this installation. Nothing else has changed, just reinstalled pgAdmin.
>
> Anybody had the same error and any ideas what's wrong?
>
> Thanks and regards
> Pawel



Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
Thanks, fixed.

On Thu, Jul 13, 2017 at 7:18 PM, Lazaro Garcia <lazaro3487@gmail.com> wrote:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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




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

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

Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
Thanks, fixed.

On Thu, Jul 13, 2017 at 7:18 PM, Lazaro Garcia <lazaro3487@gmail.com> wrote:

The download links are wrong, the links downloads 1.5 and not 1.6.

 

Regards.

 

De: Dave Page [mailto:dpage@pgadmin.org]
Enviado el: jueves, 13 de julio de 2017 11:18 a. m.
Para: pgAdmin Support; pgadmin-hackers
Asunto: pgAdmin 4 v1.6 Released!

 

The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.6. This release of pgAdmin 4 includes over 70 bug fixes and a dozen new features. For details, please see the release notes (https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_1_6.html).

 

Notable changes in this release include:

 

* Significant performance improvements on Windows, massively reducing initial load time and improving UI response for the vast majority of users during testing.

 

* Enhancements to the Query Tool enabling the viewing of large query resultsets far more quickly. For example, a simple test query with 96K rows rendered results within 1 second vs. 22 seconds in pgAdmin III during testing!

 

* A major rewrite of the Query History tab allows browsing of queries executed in the query tool with full details including the entire query, in a much nicer user interface.

 

* The Desktop Runtime now supports detachable tabs, allowing the Query Tool and Debugger to be opened in new tabs and then moved to alternate displays (from 1.5 this was possible in web mode only)

 

* The Query Tool's Results Grid has been overhauled with a new, sleek look an feel supporting selection of arbitrary rows, columns or blocks of cells with full copy support and column sizing retention.

 

* The Dashboard tab can now be closed if desired, to minimise query traffic resulting from graph updates.

 

For more information, checkout the online documentation, and of course the download page: 

 

 

 

 

--

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




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

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

Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian 
Jessie), and I've got as far as:
   python setup.py

I don't have a python environment set up, so I'm apt-getting my way 
through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):  File "setup.py", line 23, in <module>    from pgadmin import create_app  File
"/var/www/pgadmin/pgadmin/__init__.py",line 19, in <module>    from flask_htmlmin import HTMLMIN
 
ImportError: No module named flask_htmlmin


I can't find any corresponding Debian package for flask_htmlmin - what 
should I be looking for?

Thanks,

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian 
Jessie), and I've got as far as:
   python setup.py

I don't have a python environment set up, so I'm apt-getting my way 
through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):  File "setup.py", line 23, in <module>    from pgadmin import create_app  File
"/var/www/pgadmin/pgadmin/__init__.py",line 19, in <module>    from flask_htmlmin import HTMLMIN
 
ImportError: No module named flask_htmlmin


I can't find any corresponding Debian package for flask_htmlmin - what 
should I be looking for?

Thanks,

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Khushboo Vashi
Date:

On Fri, Jul 14, 2017 at 4:18 PM, Raymond O'Donnell <rod@iol.ie> wrote:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian Jessie), and I've got as far as:

   python setup.py

I don't have a python environment set up, so I'm apt-getting my way through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):
  File "setup.py", line 23, in <module>
    from pgadmin import create_app
  File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
    from flask_htmlmin import HTMLMIN
ImportError: No module named flask_htmlmin



Please refer README file for the proper installation steps (Configuring Python Environment section) .

I can't find any corresponding Debian package for flask_htmlmin - what should I be looking for?

Thanks,

Ray.

--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Khushboo Vashi
Date:

On Fri, Jul 14, 2017 at 4:18 PM, Raymond O'Donnell <rod@iol.ie> wrote:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian Jessie), and I've got as far as:

   python setup.py

I don't have a python environment set up, so I'm apt-getting my way through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):
  File "setup.py", line 23, in <module>
    from pgadmin import create_app
  File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
    from flask_htmlmin import HTMLMIN
ImportError: No module named flask_htmlmin



Please refer README file for the proper installation steps (Configuring Python Environment section) .

I can't find any corresponding Debian package for flask_htmlmin - what should I be looking for?

Thanks,

Ray.

--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Christoph Berg
Date:
Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian
Jessie), and I've got as far as:

python setup.py

I don't have a python environment set up, so I'm apt-getting my way
through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):
File "setup.py", line 23, in <module>
from pgadmin import create_app
File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
from flask_htmlmin import HTMLMIN
ImportError: No module named flask_htmlmin


I can't find any corresponding Debian package for flask_htmlmin - what
should I be looking for?

Thanks,

Ray.

We are working on packaging the missing Python modules for Debian stretch and Jessie. Should be ready over the next weeks, including pgadmin4 packages on apt.postgresql.org.

Re: pgAdmin 4 v1.6 Released!

From
Christoph Berg
Date:
Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
Hi all,

I'm trying to install pgAdmin4 in server mode on my laptop (Debian
Jessie), and I've got as far as:

python setup.py

I don't have a python environment set up, so I'm apt-getting my way
through various unmet dependencies, and one has defeated me:

Traceback (most recent call last):
File "setup.py", line 23, in <module>
from pgadmin import create_app
File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
from flask_htmlmin import HTMLMIN
ImportError: No module named flask_htmlmin


I can't find any corresponding Debian package for flask_htmlmin - what
should I be looking for?

Thanks,

Ray.

We are working on packaging the missing Python modules for Debian stretch and Jessie. Should be ready over the next weeks, including pgadmin4 packages on apt.postgresql.org.

Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
On 14/07/17 13:04, Christoph Berg wrote:
> Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
> 
>     Hi all,
> 
>     I'm trying to install pgAdmin4 in server mode on my laptop (Debian
>     Jessie), and I've got as far as:
> 
>          pythonsetup.py <http://setup.py>
> 
>     I don't have a python environment set up, so I'm apt-getting my way
>     through various unmet dependencies, and one has defeated me:
> 
>     Traceback (most recent call last):
>         File "setup.py <http://setup.py>", line 23, in <module>
>           from pgadmin import create_app
>         File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
>           from flask_htmlmin import HTMLMIN
>     ImportError: No module named flask_htmlmin
> 
> 
>     I can't find any corresponding Debian package for flask_htmlmin - what
>     should I be looking for?
> 
>     Thanks,
> 
>     Ray.
> 
> 
> We are working on packaging the missing Python modules for Debian 
> stretch and Jessie. Should be ready over the next weeks, including 
> pgadmin4 packages on apt.postgresql.org <http://apt.postgresql.org>.

Thanks, Christoph - delighted to hear that there's a package on the way 
- that'll make life a lot easier for non-Python people like me.

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
On 14/07/17 13:04, Christoph Berg wrote:
> Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
> 
>     Hi all,
> 
>     I'm trying to install pgAdmin4 in server mode on my laptop (Debian
>     Jessie), and I've got as far as:
> 
>          pythonsetup.py <http://setup.py>
> 
>     I don't have a python environment set up, so I'm apt-getting my way
>     through various unmet dependencies, and one has defeated me:
> 
>     Traceback (most recent call last):
>         File "setup.py <http://setup.py>", line 23, in <module>
>           from pgadmin import create_app
>         File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
>           from flask_htmlmin import HTMLMIN
>     ImportError: No module named flask_htmlmin
> 
> 
>     I can't find any corresponding Debian package for flask_htmlmin - what
>     should I be looking for?
> 
>     Thanks,
> 
>     Ray.
> 
> 
> We are working on packaging the missing Python modules for Debian 
> stretch and Jessie. Should be ready over the next weeks, including 
> pgadmin4 packages on apt.postgresql.org <http://apt.postgresql.org>.

Thanks, Christoph - delighted to hear that there's a package on the way 
- that'll make life a lot easier for non-Python people like me.

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
On 14/07/17 12:52, Khushboo Vashi wrote:
> 
> On Fri, Jul 14, 2017 at 4:18 PM, Raymond O'Donnell <rod@iol.ie 
> <mailto:rod@iol.ie>> wrote:
> 
>     Hi all,
> 
>     I'm trying to install pgAdmin4 in server mode on my laptop (Debian
>     Jessie), and I've got as far as:
> 
>         python setup.py
> 
>     I don't have a python environment set up, so I'm apt-getting my way
>     through various unmet dependencies, and one has defeated me:
> 
>     Traceback (most recent call last):
>        File "setup.py", line 23, in <module>
>          from pgadmin import create_app
>        File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
>          from flask_htmlmin import HTMLMIN
>     ImportError: No module named flask_htmlmin
> 
> 
> 
> Please refer README file for the proper installation steps (Configuring 
> Python Environment section) .

Thanks Khushboo, but I was trying to get it running under Apache by 
following the online documentation - sorry, I should have said that in 
my previous email. The README doesn't address requirements for this.

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Raymond O'Donnell
Date:
On 14/07/17 12:52, Khushboo Vashi wrote:
> 
> On Fri, Jul 14, 2017 at 4:18 PM, Raymond O'Donnell <rod@iol.ie 
> <mailto:rod@iol.ie>> wrote:
> 
>     Hi all,
> 
>     I'm trying to install pgAdmin4 in server mode on my laptop (Debian
>     Jessie), and I've got as far as:
> 
>         python setup.py
> 
>     I don't have a python environment set up, so I'm apt-getting my way
>     through various unmet dependencies, and one has defeated me:
> 
>     Traceback (most recent call last):
>        File "setup.py", line 23, in <module>
>          from pgadmin import create_app
>        File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
>          from flask_htmlmin import HTMLMIN
>     ImportError: No module named flask_htmlmin
> 
> 
> 
> Please refer README file for the proper installation steps (Configuring 
> Python Environment section) .

Thanks Khushboo, but I was trying to get it running under Apache by 
following the online documentation - sorry, I should have said that in 
my previous email. The README doesn't address requirements for this.

Ray.

-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

Re: pgAdmin 4 v1.6 Released!

From
Johann Spies
Date:
pts rule name              description---- ----------------------
---------------------------------------------------1.0ALL_TRUSTED            Passed through trusted hosts only via SMTP
0.5RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain 2.5 BAYES_50               BODY: Bayes
spamprobability is 40 to 60%                            [score: 0.5000]
 
X-Pg-Spam-Score: -4.2 (----)

On Wed, Jul 19, 2017 at 09:12:12AM +0100, Dave Page wrote:

> That certainly screams of 'messed up installation'. It gets that number
> from config.py.

I stopped using pgadmin4 after the first few versions and will probably
try it out again.  One of the things that makes me less enthusiastic
about trying out again is the installation process.  I do not want to go
through all the "README"'s and installation instructions again every
time there is a new version just to get it working.

Fortunately I have seen somewhere there is a promise of a package for
Debian.  I will wait for it.

Making the installation process (or at least the update process) easier
should be a prioirity.

Regards
Johann
-- 
Johann Spies                            Telefoon: 021-808 4699
Databestuurder /  Data manager        Faks: 021-883 3691

Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie
Centre for Research on Evaluation, Science and Technology 
Universiteit Stellenbosch.

The integrity and confidentiality of this email is governed by these terms / Hierdie terme bepaal die integriteit en
vertroulikheidvan hierdie epos. http://www.sun.ac.za/emaildisclaimer
 


Re: pgAdmin 4 v1.6 Released!

From
Pawel Hadam
Date:
Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

Attachment

Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>

Re: pgAdmin 4 v1.6 Released!

From
Pawel Hadam
Date:
Hi Dave,

I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.

I suspect, that those two environments may disturb each other, but cannot see see how.

Also:
1) when v1.6 launched from the installer it works well.
2) when v1.6 launched from a shortcut it starts v1.5.
3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path.

I will do some checks on another PC today.

Thank you and kind regards
Pawel


On 21 July 2017 at 00:28, Dave Page <dpage@pgadmin.org> wrote:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>

Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
Hi

On Fri, Jul 21, 2017 at 7:14 AM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.

I suspect, that those two environments may disturb each other, but cannot see see how.

No, they're designed to be completely independent. The only thing they would share would be registry settings for zoom level and geometry.
 

Also:
1) when v1.6 launched from the installer it works well.
2) when v1.6 launched from a shortcut it starts v1.5.

What does the shortcut point to for the working directory? If you run it, then press Alt+Shift+P, are there any settings shown?
 
3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path.

I will do some checks on another PC today.

Thank you and kind regards
Pawel


On 21 July 2017 at 00:28, Dave Page <dpage@pgadmin.org> wrote:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>




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

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

Re: pgAdmin 4 v1.6 Released!

From
Pawel Hadam
Date:
Hi Dave,

I have only 2 versions of pgAdmin4.exe:

$ find . -name "pgAdmin4.exe"
./Program Files/PostgreSQL/9.6/pgAdmin 4/bin/pgAdmin4.exe
./Program Files (x86)/pgAdmin 4/v1/runtime/pgAdmin4.exe

The first one is definitely v1.3 and works well when started by running the exec itself.

When installer started v1.6, the process was pointing to the second exec.

When I start the second exec from cygwin bash it starts v1.6 - what is good, and a kind of a workaround and a kind of a hint, as well. So I added to the shortcut "Run as administrator" and now it starts v1.6 correctly. So the issue is solved - thank you Dave!

But where is the v1.5 that starts from the "non-administrator" shortcut, that's another question...

Thanks and regards
Pawel


On 21 July 2017 at 09:27, Dave Page <dpage@pgadmin.org> wrote:
Hi

On Fri, Jul 21, 2017 at 7:14 AM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.

I suspect, that those two environments may disturb each other, but cannot see see how.

No, they're designed to be completely independent. The only thing they would share would be registry settings for zoom level and geometry.
 

Also:
1) when v1.6 launched from the installer it works well.
2) when v1.6 launched from a shortcut it starts v1.5.

What does the shortcut point to for the working directory? If you run it, then press Alt+Shift+P, are there any settings shown?
 
3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path.

I will do some checks on another PC today.

Thank you and kind regards
Pawel


On 21 July 2017 at 00:28, Dave Page <dpage@pgadmin.org> wrote:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>




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

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

Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
Hi

On Fri, Jul 21, 2017 at 9:52 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I have only 2 versions of pgAdmin4.exe:

$ find . -name "pgAdmin4.exe"
./Program Files/PostgreSQL/9.6/pgAdmin 4/bin/pgAdmin4.exe
./Program Files (x86)/pgAdmin 4/v1/runtime/pgAdmin4.exe

The first one is definitely v1.3 and works well when started by running the exec itself.

When installer started v1.6, the process was pointing to the second exec.

When I start the second exec from cygwin bash it starts v1.6 - what is good, and a kind of a workaround and a kind of a hint, as well. So I added to the shortcut "Run as administrator" and now it starts v1.6 correctly. So the issue is solved - thank you Dave!

Well, that's good, but I really like to get to the bottom of things :-)
 

But where is the v1.5 that starts from the "non-administrator" shortcut, that's another question...

You could try searching for files containing one of these lines:

APP_REVISION = 5
APP_VERSION_INT = 15001

That should (I hope) find the config.py that is setup for 1.5.
 

Thanks and regards
Pawel


On 21 July 2017 at 09:27, Dave Page <dpage@pgadmin.org> wrote:
Hi

On Fri, Jul 21, 2017 at 7:14 AM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.

I suspect, that those two environments may disturb each other, but cannot see see how.

No, they're designed to be completely independent. The only thing they would share would be registry settings for zoom level and geometry.
 

Also:
1) when v1.6 launched from the installer it works well.
2) when v1.6 launched from a shortcut it starts v1.5.

What does the shortcut point to for the working directory? If you run it, then press Alt+Shift+P, are there any settings shown?
 
3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path.

I will do some checks on another PC today.

Thank you and kind regards
Pawel


On 21 July 2017 at 00:28, Dave Page <dpage@pgadmin.org> wrote:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>




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

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




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

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

Re: pgAdmin 4 v1.6 Released!

From
Pawel Hadam
Date:
Hi Dave,

Thank you. Unfortunately I cannot find those entries:



pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "con*py" | xargs grep "APP_REVISION" 2> /dev/null

pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "conf*py" | xargs grep "APP_VERSION_INT" 2> /dev/null



But I have found the following "config.py" files:


pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "config.py"
/cygdrive/c/cygwin64/home/pawelhadam/pythonpostgresql/PycharmProjects/intro-to-databases/venv/Lib/site-packages/setuptools/config.py
/cygdrive/c/cygwin64/lib/python2.7/distutils/command/config.py
/cygdrive/c/cygwin64/lib/python2.7/distutils/config.py
/cygdrive/c/cygwin64/lib/python2.7/logging/config.py
/cygdrive/c/cygwin64/lib/python3.4/distutils/command/config.py
/cygdrive/c/cygwin64/lib/python3.4/distutils/config.py
/cygdrive/c/cygwin64/lib/python3.4/logging/config.py
/cygdrive/c/DataStaxDDC/python/Lib/distutils/command/config.py
/cygdrive/c/DataStaxDDC/python/Lib/distutils/config.py
/cygdrive/c/DataStaxDDC/python/Lib/logging/config.py
/cygdrive/c/Program Files/JetBrains/PyCharm Community Edition 2017.1.3/helpers/coveragepy/coverage/config.py
/cygdrive/c/Program Files/JetBrains/PyCharm Community Edition 2017.1.3/helpers/pycharm/nose_helper/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/distutils/command/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/distutils/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/logging/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/site-packages/flask/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/site-packages/setuptools/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/venv/Lib/site-packages/sqlalchemy/testing/config.py
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/web/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/distutils/command/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/distutils/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/logging/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/site-packages/alembic/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/site-packages/alembic/testing/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/site-packages/flask/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/site-packages/setuptools/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/venv/Lib/site-packages/sqlalchemy/testing/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/web/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r10e/prebuilt/windows/lib/python2.7/distutils/command/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r10e/prebuilt/windows/lib/python2.7/distutils/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r10e/prebuilt/windows/lib/python2.7/logging/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/prebuilt/windows/lib/python2.7/distutils/command/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/prebuilt/windows/lib/python2.7/distutils/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/prebuilt/windows/lib/python2.7/logging/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/android/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/ndk/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK/android-ndk-r11c/sources/cxx-stl/llvm-libc++abi/libcxxabi/test/libcxxabi/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r10e/prebuilt/windows-x86_64/lib/python2.7/distutils/command/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r10e/prebuilt/windows-x86_64/lib/python2.7/distutils/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r10e/prebuilt/windows-x86_64/lib/python2.7/logging/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/prebuilt/windows-x86_64/lib/python2.7/distutils/command/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/prebuilt/windows-x86_64/lib/python2.7/distutils/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/prebuilt/windows-x86_64/lib/python2.7/logging/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/android/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/ndk/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/sources/cxx-stl/llvm-libc++/libcxx/test/libcxx/test/config.py
/cygdrive/c/ProgramData/Microsoft/AndroidNDK64/android-ndk-r11c/sources/cxx-stl/llvm-libc++abi/libcxxabi/test/libcxxabi/test/config.py
/cygdrive/c/Python27/Lib/distutils/command/config.py
/cygdrive/c/Python27/Lib/distutils/config.py
/cygdrive/c/Python27/Lib/logging/config.py
/cygdrive/c/Users/pawelhadam/.windows-build-tools/python27/Lib/distutils/command/config.py
/cygdrive/c/Users/pawelhadam/.windows-build-tools/python27/Lib/distutils/config.py
/cygdrive/c/Users/pawelhadam/.windows-build-tools/python27/Lib/logging/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python35/Lib/distutils/command/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python35/Lib/distutils/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python35/Lib/logging/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python36-32/Lib/distutils/command/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python36-32/Lib/distutils/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python36-32/Lib/idlelib/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/Programs/Python/Python36-32/Lib/logging/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/VirtualStore/Program Files (x86)/pgAdmin 4/v1/web/config.py



I wonder what else I can provide to help?

Thanks and regards
Pawel


On 21 July 2017 at 21:56, Dave Page <dpage@pgadmin.org> wrote:
Hi

On Fri, Jul 21, 2017 at 9:52 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I have only 2 versions of pgAdmin4.exe:

$ find . -name "pgAdmin4.exe"
./Program Files/PostgreSQL/9.6/pgAdmin 4/bin/pgAdmin4.exe
./Program Files (x86)/pgAdmin 4/v1/runtime/pgAdmin4.exe

The first one is definitely v1.3 and works well when started by running the exec itself.

When installer started v1.6, the process was pointing to the second exec.

When I start the second exec from cygwin bash it starts v1.6 - what is good, and a kind of a workaround and a kind of a hint, as well. So I added to the shortcut "Run as administrator" and now it starts v1.6 correctly. So the issue is solved - thank you Dave!

Well, that's good, but I really like to get to the bottom of things :-)
 

But where is the v1.5 that starts from the "non-administrator" shortcut, that's another question...

You could try searching for files containing one of these lines:

APP_REVISION = 5
APP_VERSION_INT = 15001

That should (I hope) find the config.py that is setup for 1.5.
 

Thanks and regards
Pawel


On 21 July 2017 at 09:27, Dave Page <dpage@pgadmin.org> wrote:
Hi

On Fri, Jul 21, 2017 at 7:14 AM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.

I suspect, that those two environments may disturb each other, but cannot see see how.

No, they're designed to be completely independent. The only thing they would share would be registry settings for zoom level and geometry.
 

Also:
1) when v1.6 launched from the installer it works well.
2) when v1.6 launched from a shortcut it starts v1.5.

What does the shortcut point to for the working directory? If you run it, then press Alt+Shift+P, are there any settings shown?
 
3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path.

I will do some checks on another PC today.

Thank you and kind regards
Pawel


On 21 July 2017 at 00:28, Dave Page <dpage@pgadmin.org> wrote:
You don't have the PostgreSQL installer from EDB or BigSQL on that machine do you? They have their own separate copies of pgAdmin.

Sent from my iPad

On 20 Jul 2017, at 23:53, Pawel Hadam <hadzio@gmail.com> wrote:

Thank you Dave,

Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.

2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...


However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:

2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...


Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\ 
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\


I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.


Thanks in advance for any more help and kind regards
Pawel


On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]

Hi

On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you for this advise.

Please find attached my files:

1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log

I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exe

That certainly screams of 'messed up installation'. It gets that number from config.py.
 

2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py

I'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.

Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).

Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4

Once the system is completely cleaned, try a fresh installation.

Regards, Dave.
 

Thank you and kind regards
Pawel


On 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:


On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Thank you Dave and Khushboo for advises.

1) (re)moving 'pgadmin4.db' - did not help.

2) I have disabled teredo - did not help.

3) localhost is resolved to IPv6 address:

$ ping localhost

Pinging ogrodowa [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

4) I DO use IPv4 as well.

5) No entries for localhost in hosts file.

6) On which address/port the server should be listening?

$ netstat -a | grep LISTEN | grep "127.0.0.1"
  TCP    127.0.0.1:3212         ogrodowa:0             LISTENING
  TCP    127.0.0.1:3213         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4370         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4371         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4380         ogrodowa:0             LISTENING
  TCP    127.0.0.1:4381         ogrodowa:0             LISTENING
  TCP    127.0.0.1:5037         ogrodowa:0             LISTENING
  TCP    127.0.0.1:9990         ogrodowa:0             LISTENING
  TCP    127.0.0.1:30000        ogrodowa:0             LISTENING
  TCP    127.0.0.1:49674        ogrodowa:0             LISTENING

7) ping to 127.0.0.1 works well:

$ ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128


Not sure what else I need to check...

In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :

====
from config import *

# Debug mode
DEBUG = True

# Log
CONSOLE_LOG_LEVEL = DEBUG
FILE_LOG_LEVEL = DEBUG
====

Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.

Thanks.

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

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




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

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

<config.py>
<pgadmin4.log>
<config_distro.py>
<config_local.py>




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

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




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

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

Re: pgAdmin 4 v1.6 Released!

From
Dave Page
Date:
Hi

On Wed, Jul 26, 2017 at 9:17 PM, Pawel Hadam <hadzio@gmail.com> wrote:
Hi Dave,

Thank you. Unfortunately I cannot find those entries:



pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "con*py" | xargs grep "APP_REVISION" 2> /dev/null

pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "conf*py" | xargs grep "APP_VERSION_INT" 2> /dev/null

Well that's weird. Those strings have been in every single pgAdmin 4 release, so at the very least I'd expect it to find the 2 installations you know are present.
 
But I have found the following "config.py" files:


pawelhadam@ogrodowa ~
$ find /cygdrive/c -type f -name "config.py"
/cygdrive/c/Program Files/PostgreSQL/9.6/pgAdmin 4/web/config.py
/cygdrive/c/Program Files (x86)/pgAdmin 4/v1/web/config.py
/cygdrive/c/Users/pawelhadam/AppData/Local/VirtualStore/Program Files (x86)/pgAdmin 4/v1/web/config.py

OK, so those all look like candidates. The last one looks quite odd to me - I wouldn't expect to see a copy of it in there.

Any of them contain 1.5 as the version?

Please note, I'm going on vacation from this weekend and won't be back until ~17th August (though I may have intermittent access to email only; i.e. no laptop). If I don't reply to emails in that time, that's why.

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

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

Re: pgAdmin 4 v1.6 Released!

From
Alasdair Campbell
Date:
On Fri 14 Jul 2017 14:04:53 GMT, Christoph Berg wrote:
> Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
> >Hi all,
> >
> >I'm trying to install pgAdmin4 in server mode on my laptop (Debian 
> >Jessie), and I've got as far as:
> >
> >    python setup.py
> >
> >I don't have a python environment set up, so I'm apt-getting my way 
> >through various unmet dependencies, and one has defeated me:
> >
> >Traceback (most recent call last):
> >   File "setup.py", line 23, in <module>
> >     from pgadmin import create_app
> >   File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
> >     from flask_htmlmin import HTMLMIN
> >ImportError: No module named flask_htmlmin
> >
> >
> >I can't find any corresponding Debian package for flask_htmlmin - what 
> >should I be looking for?
> >
> >Thanks,
> >
> >Ray.
> >
> >-- 
> >Raymond O'Donnell :: Galway :: Ireland
> >rod@iol.ie
> 
> We are working on packaging the missing Python modules for Debian stretch and Jessie. Should be ready over the next
weeks,including pgadmin4 packages on apt.postgresql.org.
 

Hi,

I was just wondering if packaging the missing Python modules for Debian
had been abandoned / forgotten about with the release of pgAdmin4 v2 and
PostgreSQL 10. Trent was trying to build a deb for pgAdmin4 and ran into
the same issue.  I suspect you've seen it Christoph due to the Debian
bug report, but for anyone else:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129#23

Al.



Re: pgAdmin 4 v1.6 Released!

From
Alasdair Campbell
Date:
On Fri 14 Jul 2017 14:04:53 GMT, Christoph Berg wrote:
> Am 14. Juli 2017 12:48:16 MESZ schrieb Raymond O'Donnell <rod@iol.ie>:
> >Hi all,
> >
> >I'm trying to install pgAdmin4 in server mode on my laptop (Debian 
> >Jessie), and I've got as far as:
> >
> >    python setup.py
> >
> >I don't have a python environment set up, so I'm apt-getting my way 
> >through various unmet dependencies, and one has defeated me:
> >
> >Traceback (most recent call last):
> >   File "setup.py", line 23, in <module>
> >     from pgadmin import create_app
> >   File "/var/www/pgadmin/pgadmin/__init__.py", line 19, in <module>
> >     from flask_htmlmin import HTMLMIN
> >ImportError: No module named flask_htmlmin
> >
> >
> >I can't find any corresponding Debian package for flask_htmlmin - what 
> >should I be looking for?
> >
> >Thanks,
> >
> >Ray.
> >
> >-- 
> >Raymond O'Donnell :: Galway :: Ireland
> >rod@iol.ie
> 
> We are working on packaging the missing Python modules for Debian stretch and Jessie. Should be ready over the next
weeks,including pgadmin4 packages on apt.postgresql.org.
 

Hi,

I was just wondering if packaging the missing Python modules for Debian
had been abandoned / forgotten about with the release of pgAdmin4 v2 and
PostgreSQL 10. Trent was trying to build a deb for pgAdmin4 and ran into
the same issue.  I suspect you've seen it Christoph due to the Debian
bug report, but for anyone else:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129#23

Al.



Re: pgAdmin 4 v1.6 Released!

From
Christoph Berg
Date:
Re: Alasdair Campbell 2017-10-10 <20171010113716.cesg7rwsm2a6o4q3@COLONEL-K>
> I was just wondering if packaging the missing Python modules for Debian
> had been abandoned / forgotten about with the release of pgAdmin4 v2 and
> PostgreSQL 10. Trent was trying to build a deb for pgAdmin4 and ran into
> the same issue.  I suspect you've seen it Christoph due to the Debian
> bug report, but for anyone else:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129#23

Sorry for the delay here, we've been busy with the PG 10 release and
getting all modules ready. Finishing pgadmin4 packaging is moving back
closer to the top of the TODO list now.

Christoph


Re: pgAdmin 4 v1.6 Released!

From
Christoph Berg
Date:
Re: Alasdair Campbell 2017-10-10 <20171010113716.cesg7rwsm2a6o4q3@COLONEL-K>
> I was just wondering if packaging the missing Python modules for Debian
> had been abandoned / forgotten about with the release of pgAdmin4 v2 and
> PostgreSQL 10. Trent was trying to build a deb for pgAdmin4 and ran into
> the same issue.  I suspect you've seen it Christoph due to the Debian
> bug report, but for anyone else:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129#23

Sorry for the delay here, we've been busy with the PG 10 release and
getting all modules ready. Finishing pgadmin4 packaging is moving back
closer to the top of the TODO list now.

Christoph