Thread: Re: pgAdmin 4 v1.6 Released!
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?
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:
Download: https://www.pgadmin.org/downlo
ad
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
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 On 14 July 2017 at 01:00, 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? > > 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: >> >> >> >> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html >> >> >> >> Download: https://www.pgadmin.org/download >> >> >> >> >> >> -- >> >> Dave Page >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake > > > >
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 On 14 July 2017 at 01:00, 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? > > 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: >> >> >> >> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html >> >> >> >> Download: https://www.pgadmin.org/download >> >> >> >> >> >> -- >> >> Dave Page >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake > > > >
On Fri, Jul 14, 2017 at 7:53 AM, Pawel Hadam <hadzio@gmail.com> 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?
One change in 1.6 was that we use 127.0.0.1 as the server address instead of 'localhost'. That was because we found that resolution of 'localhost' to an address can actually be quite slow on Windows in a Qt app. Do you have any kind of unusual network setup where 127.0.0.1 wouldn't work? E.g. *only* IPv6?
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Jul 14, 2017 at 7:53 AM, Pawel Hadam <hadzio@gmail.com> 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?
One change in 1.6 was that we use 127.0.0.1 as the server address instead of 'localhost'. That was because we found that resolution of 'localhost' to an address can actually be quite slow on Windows in a Qt app. Do you have any kind of unusual network setup where 127.0.0.1 wouldn't work? E.g. *only* IPv6?
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Jul 14, 2017 at 12:23 PM, Pawel Hadam <hadzio@gmail.com> 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?
I faced similar issue, by moving the pgadmin4.db file to another location (or can rename) worked for me.
Thanks and regards
Pawel
On 14 July 2017 at 01:00, 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?
>
> 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:
>>
>>
>>
>> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html
>>
>>
>>
>> Download: https://www.pgadmin.org/download
>>
>>
>>
>>
>>
>> --
>>
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>
>
>
>
On Fri, Jul 14, 2017 at 12:23 PM, Pawel Hadam <hadzio@gmail.com> 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?
I faced similar issue, by moving the pgadmin4.db file to another location (or can rename) worked for me.
Thanks and regards
Pawel
On 14 July 2017 at 01:00, 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?
>
> 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:
>>
>>
>>
>> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html
>>
>>
>>
>> Download: https://www.pgadmin.org/download
>>
>>
>>
>>
>>
>> --
>>
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>
>
>
>
On Fri, Jul 14, 2017 at 1:55 PM, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote:
On Fri, Jul 14, 2017 at 12:23 PM, Pawel Hadam <hadzio@gmail.com> 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?I faced similar issue, by moving the pgadmin4.db file to another location (or can rename) worked for me.
If you are on windows, then you can find the file at C:\Users\username\AppData\Roaming\pgAdmin location.
Thanks and regards
Pawel
On 14 July 2017 at 01:00, 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?
>
> 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:
>>
>>
>>
>> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html
>>
>>
>>
>> Download: https://www.pgadmin.org/download
>>
>>
>>
>>
>>
>> --
>>
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>
>
>
>
On Fri, Jul 14, 2017 at 1:55 PM, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote:
On Fri, Jul 14, 2017 at 12:23 PM, Pawel Hadam <hadzio@gmail.com> 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?I faced similar issue, by moving the pgadmin4.db file to another location (or can rename) worked for me.
If you are on windows, then you can find the file at C:\Users\username\AppData\Roaming\pgAdmin location.
Thanks and regards
Pawel
On 14 July 2017 at 01:00, 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?
>
> 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:
>>
>>
>>
>> Docs: https://www.pgadmin.org/docs/pgadmin4/dev/index.html
>>
>>
>>
>> Download: https://www.pgadmin.org/download
>>
>>
>>
>>
>>
>> --
>>
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>
>
>
>
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...
Thank you and kind regards
Pawel
On 14 July 2017 at 09:15, Dave Page <dpage@pgadmin.org> wrote:
On Fri, Jul 14, 2017 at 7:53 AM, Pawel Hadam <hadzio@gmail.com> 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?One change in 1.6 was that we use 127.0.0.1 as the server address instead of 'localhost'. That was because we found that resolution of 'localhost' to an address can actually be quite slow on Windows in a Qt app. Do you have any kind of unusual network setup where 127.0.0.1 wouldn't work? E.g. *only* IPv6?--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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...
Thank you and kind regards
Pawel
On 14 July 2017 at 09:15, Dave Page <dpage@pgadmin.org> wrote:
On Fri, Jul 14, 2017 at 7:53 AM, Pawel Hadam <hadzio@gmail.com> 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?One change in 1.6 was that we use 127.0.0.1 as the server address instead of 'localhost'. That was because we found that resolution of 'localhost' to an address can actually be quite slow on Windows in a Qt app. Do you have any kind of unusual network setup where 127.0.0.1 wouldn't work? E.g. *only* IPv6?--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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 localhostPinging ogrodowa [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms4) 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 LISTENINGTCP 127.0.0.1:3213 ogrodowa:0 LISTENINGTCP 127.0.0.1:4370 ogrodowa:0 LISTENINGTCP 127.0.0.1:4371 ogrodowa:0 LISTENINGTCP 127.0.0.1:4380 ogrodowa:0 LISTENINGTCP 127.0.0.1:4381 ogrodowa:0 LISTENINGTCP 127.0.0.1:5037 ogrodowa:0 LISTENINGTCP 127.0.0.1:9990 ogrodowa:0 LISTENINGTCP 127.0.0.1:30000 ogrodowa:0 LISTENINGTCP 127.0.0.1:49674 ogrodowa:0 LISTENING7) ping to 127.0.0.1 works well:$ ping 127.0.0.1Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Not 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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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 localhostPinging ogrodowa [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms4) 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 LISTENINGTCP 127.0.0.1:3213 ogrodowa:0 LISTENINGTCP 127.0.0.1:4370 ogrodowa:0 LISTENINGTCP 127.0.0.1:4371 ogrodowa:0 LISTENINGTCP 127.0.0.1:4380 ogrodowa:0 LISTENINGTCP 127.0.0.1:4381 ogrodowa:0 LISTENINGTCP 127.0.0.1:5037 ogrodowa:0 LISTENINGTCP 127.0.0.1:9990 ogrodowa:0 LISTENINGTCP 127.0.0.1:30000 ogrodowa:0 LISTENINGTCP 127.0.0.1:49674 ogrodowa:0 LISTENING7) ping to 127.0.0.1 works well:$ ping 127.0.0.1Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Not 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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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
2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py
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 localhostPinging ogrodowa [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms4) 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 LISTENINGTCP 127.0.0.1:3213 ogrodowa:0 LISTENINGTCP 127.0.0.1:4370 ogrodowa:0 LISTENINGTCP 127.0.0.1:4371 ogrodowa:0 LISTENINGTCP 127.0.0.1:4380 ogrodowa:0 LISTENINGTCP 127.0.0.1:4381 ogrodowa:0 LISTENINGTCP 127.0.0.1:5037 ogrodowa:0 LISTENINGTCP 127.0.0.1:9990 ogrodowa:0 LISTENINGTCP 127.0.0.1:30000 ogrodowa:0 LISTENINGTCP 127.0.0.1:49674 ogrodowa:0 LISTENING7) ping to 127.0.0.1 works well:$ ping 127.0.0.1Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Not 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 modeDEBUG = True# LogCONSOLE_LOG_LEVEL = DEBUGFILE_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
Attachment
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
2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py
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 localhostPinging ogrodowa [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms4) 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 LISTENINGTCP 127.0.0.1:3213 ogrodowa:0 LISTENINGTCP 127.0.0.1:4370 ogrodowa:0 LISTENINGTCP 127.0.0.1:4371 ogrodowa:0 LISTENINGTCP 127.0.0.1:4380 ogrodowa:0 LISTENINGTCP 127.0.0.1:4381 ogrodowa:0 LISTENINGTCP 127.0.0.1:5037 ogrodowa:0 LISTENINGTCP 127.0.0.1:9990 ogrodowa:0 LISTENINGTCP 127.0.0.1:30000 ogrodowa:0 LISTENINGTCP 127.0.0.1:49674 ogrodowa:0 LISTENING7) ping to 127.0.0.1 works well:$ ping 127.0.0.1Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Not 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 modeDEBUG = True# LogCONSOLE_LOG_LEVEL = DEBUGFILE_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