Re: pgAdmin 4 v1.6 Released!

Поиск
Список
Период
Сортировка
От Pawel Hadam
Тема Re: pgAdmin 4 v1.6 Released!
Дата
Msg-id CAPZL3N21hzF1ELgdOLnRvCyrqp_omj_oAQoZYt46z-nwwS4-9w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgAdmin 4 v1.6 Released!  (Dave Page <dpage@pgadmin.org>)
Ответы Re: pgAdmin 4 v1.6 Released!  (Dave Page <dpage@pgadmin.org>)
Re: pgAdmin 4 v1.6 Released!  (Dave Page <dpage@pgadmin.org>)
Список pgadmin-hackers
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

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Akshay Joshi
Дата:
Сообщение: [pgAdmin4][Patch]: Fix RM #2566 Pause/Resume Replay of WAL files arenot working with PostgreSQL 10
Следующее
От: Ashesh Vashi
Дата:
Сообщение: pgAdmin 4 commit: [PostgreSQL 10] Fixed the Pause/Resume Replay ofWAL