pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
17+ messages / 6 participants
[nested] [flat]

* Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
@ 2019-08-12 21:08 Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  0 siblings, 1 reply; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-12 21:08 UTC (permalink / raw)
  To: pgsql-admin; +Cc: bikramma@gmail.com <bikramma@gmail.com>


Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 - but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image001.jpg@01D55128.1FF43F20]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image002.png@01D55128.1FF43F20]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

Attachments:

image001.jpg (image/jpeg, 29.9K) download view image
image002.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-12 21:24 ` Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Tim Scheurenbrand @ 2019-08-12 21:24 UTC (permalink / raw)
  To: Bikram MAJUMDAR <bikram.majumdar@aqsacom.com>; pgsql-admin; +Cc: bikramma@gmail.com

Hi Bikram




Have you checked your firewall settings?




Tim Scheurenbrand




On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:




















 


Hi ,


We need help in resolving connection issues using the pgadmin tool.


We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.


But, recently we had to change our postgres server port from 5433 to 5432 - 



And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).



 





 


 


Please help to resolve this issue.


 


Bikram Majumdar


Sr Software Developer/DBA, Aqsacom Inc.


c. 1.972.365.3737



e.
bikram.majumdar@aqsacom.com 



s. BIKRAM MAJUMDAR


 





 


Disclaimer.
This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
 BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message
 is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.
Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


 

Attachments:

image001.jpg (image/jpeg, 29.9K) download view image
image002.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
@ 2019-08-12 21:51   ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:09     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  0 siblings, 2 replies; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-12 21:51 UTC (permalink / raw)
  To: Tim Scheurenbrand <info@timscheurenbrand.de>; pgsql-admin; +Cc: bikramma@gmail.com <bikramma@gmail.com>

Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image004.png@01D5512E.33B1BF50]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand


On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image006.jpg@01D5512E.33B1BF50]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image008.png@01D5512E.33B1BF50]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



Attachments:

image004.png (image/png, 10.0K) download view image
image006.jpg (image/jpeg, 29.6K) download view image
image008.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-12 22:09     ` Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 22:18       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  1 sibling, 1 reply; 17+ messages in thread

From: Tim Scheurenbrand @ 2019-08-12 22:09 UTC (permalink / raw)
  To: Bikram MAJUMDAR <bikram.majumdar@aqsacom.com>; pgsql-admin; +Cc: bikramma@gmail.com

Hi Bikram,


I was thinking about the win10 firewall, as you mentioned having intalled pgadmin4 on win10. Haven't used this setup on my own, just know, some installers (pgadmin4?) open up specific ports during installation. Might be, your local firewall is configured not to allow all tcp outbound traffic and blocking 5433?


Best,


Tim Scheurenbrand 




On Mon, Aug 12, 2019 at 11:51 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:




















Hi Tim,


 


Thanks for your quick response.



Are you thinking port 5433 is not opened for listening on the postgres database server?



[root@cemtore01 ~]# systemctl status firewalld.service


â firewalld.service - firewalld - dynamic firewall daemon


   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)


   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago


     Docs: man:firewalld(1)


Main PID: 883 (firewalld)


   CGroup: /system.slice/firewalld.service


           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid


 


Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.


Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.


May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port


May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports


May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone


 



Bikram Majumdar


Sr Software Developer/DBA, Aqsacom Inc.


c. 1.972.365.3737


 





 


Disclaimer.
This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
 BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message
 is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.
Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



 




From: Tim Scheurenbrand <info@timscheurenbrand.de> 

Sent: Monday, August 12, 2019 4:25 PM

To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org

Cc: bikramma@gmail.com

Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)




 



Hi Bikram




Have you checked your firewall settings?




Tim Scheurenbrand











On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:




 


Hi ,


We need help in resolving connection issues using the pgadmin tool.


We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.


But, recently we had to change our postgres server port from 5433 to 5432 - 



And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).



 





 


 


Please help to resolve this issue.


 


Bikram Majumdar


Sr Software Developer/DBA, Aqsacom Inc.


c. 1.972.365.3737



e.
bikram.majumdar@aqsacom.com 



s. BIKRAM MAJUMDAR


 





 


Disclaimer.
This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
 BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message
 is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.
Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


 

Attachments:

image004.png (image/png, 10.0K) download view image
image006.jpg (image/jpeg, 29.6K) download view image
image008.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:09     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
@ 2019-08-12 22:18       ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  0 siblings, 0 replies; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-12 22:18 UTC (permalink / raw)
  To: Tim Scheurenbrand <info@timscheurenbrand.de>; pgsql-admin; +Cc: bikramma@gmail.com <bikramma@gmail.com>

Hi Tim,

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image001.png@01D55131.FA26C5B0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 5:09 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram,
I was thinking about the win10 firewall, as you mentioned having intalled pgadmin4 on win10. Haven't used this setup on my own, just know, some installers (pgadmin4?) open up specific ports during installation. Might be, your local firewall is configured not to allow all tcp outbound traffic and blocking 5433?
Best,
Tim Scheurenbrand


On Mon, Aug 12, 2019 at 11:51 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:
Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image002.png@01D55131.FA26C5B0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand



On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image003.jpg@01D55131.FA26C5B0]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image005.png@01D55131.FA26C5B0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



Attachments:

image001.png (image/png, 10.0K) download view image
image002.png (image/png, 10.0K) download view image
image003.jpg (image/jpeg, 29.2K) download view image
image005.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-12 22:14     ` Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:16       ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  1 sibling, 2 replies; 17+ messages in thread

From: Ron @ 2019-08-12 22:14 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running 
pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433

On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
>
> Hi Tim,
>
> Thanks for your quick response.
>
> Are you thinking port 5433 is not opened for listening on the postgres 
> database server?
>
> [root@cemtore01 ~]# systemctl status firewalld.service
>
> â firewalld.service - firewalld - dynamic firewall daemon
>
>    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; 
> vendor preset: enabled)
>
>    Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 
> days ago
>
>      Docs: man:firewalld(1)
>
> Main PID: 883 (firewalld)
>
>    CGroup: /system.slice/firewalld.service
>
> ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
>
> Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall 
> daemon.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 
> 'beyond-scope' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: 
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 
> 'failed-policy' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: 
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 
> 'reject-route' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: 
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
>
> May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
>
> May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.*1.972.365.3737
>
> <http://www.aqsacom.com/;
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL 
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED 
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED 
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the 
> Addressee(s) named herein. If you are not an Addressee, or the person 
> responsible for delivering this to an Addressee, you are hereby notified 
> that reading, copying, or distributing this message is prohibited. If you 
> have received this electronic mail message in error, please reply to the 
> sender and take the steps necessary to delete the message completely from 
> your computer system. Statement and opinions expressed in this e-mail are 
> those of the sender, and do not necessarily reflect those of AQSACOM. 
> AQSACOM accepts no liability for any damage caused by any virus/worms 
> transmitted by this email.
>
> *From:* Tim Scheurenbrand <info@timscheurenbrand.de>
> *Sent:* Monday, August 12, 2019 4:25 PM
> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; 
> pgsql-admin@postgresql.org
> *Cc:* bikramma@gmail.com
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the 
> postgres database server when the database is listening on port 5433 
> (instead of port 5432)
>
> Hi Bikram
>
> Have you checked your firewall settings?
>
> Tim Scheurenbrand
>
>
>
> On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" 
> <Bikram.Majumdar@aqsacom.com <mailto:Bikram.Majumdar@aqsacom.com>> wrote:
>
>     Hi ,
>
>     We need help in resolving connection issues using the pgadmin tool.
>
>     We had our pgadmin (pgadmin4) installed a few months back on windows
>     10 and we were able to use it for  our postgres server running on port
>     5432.
>
>     But, recently we had to change our postgres server port from 5433 to
>     5432 -
>
>     And accordingly, in pgadmin we changed the port also to 5433 – but we
>     are receiving connection timed out error in connecting to our server
>     (see below screen shot).
>
>     Please help to resolve this issue.
>
>     *Bikram Majumdar*
>
>     Sr Software Developer/DBA, Aqsacom Inc.
>
>     *c.*1.972.365.3737
>
>     *e.*bikram.majumdar@aqsacom.com <mailto:bikram.majumdar@aqsacom.com>
>
>     *s.*BIKRAM MAJUMDAR
>
>     <http://www.aqsacom.com/;
>
>     *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>     information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>     COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE
>     PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of
>     the Addressee(s) named herein. If you are not an Addressee, or the
>     person responsible for delivering this to an Addressee, you are hereby
>     notified that reading, copying, or distributing this message is
>     prohibited. If you have received this electronic mail message in
>     error, please reply to the sender and take the steps necessary to
>     delete the message completely from your computer system. Statement and
>     opinions expressed in this e-mail are those of the sender, and do not
>     necessarily reflect those of AQSACOM. AQSACOM accepts no liability for
>     any damage caused by any virus/worms transmitted by this email.
>

-- 
Angular momentum makes the world go 'round.

Attachments:

image004.png (image/png, 10.0K) download view image
image006.jpg (image/jpeg, 29.6K) download view image
image008.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
@ 2019-08-12 22:16       ` Tim Scheurenbrand <info@timscheurenbrand.de>
  1 sibling, 0 replies; 17+ messages in thread

From: Tim Scheurenbrand @ 2019-08-12 22:16 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org, Ron <ronljohnsonjr@gmail.com>

Hi Bikram,


Your last mail containes the state of the firewalld daemon but not its zone config nor allowed or blocked services/ports.


Could you check something like the following command for port 5433 on your postgresql server?


firewall-cmd --list-all-zones


Best,


Tim Scheurenbrand 




On Tue, Aug 13, 2019 at 12:14 AM +0200, "Ron" <ronljohnsonjr@gmail.com> wrote:











  
    
  
  
    There are more firewalls than just the one running (or not) on
    cemtore01.

    

    Keep things simple and just run a traceroute from the server running
    pgadmin4 to the server running postgres.

    

    If that works, then telnet to the server on port 5433

    

    On 8/12/19 4:51 PM, Bikram MAJUMDAR
      wrote:

    
    
      
      
      
      
      
        

Hi Tim,
        

 
        

Thanks for
            your quick response.
        
          

Are you
              thinking port 5433 is not opened for listening on the
              postgres database server?
        
        

[root@cemtore01
            ~]# systemctl status firewalld.service
        

â
            firewalld.service - firewalld - dynamic firewall daemon
        

   Loaded:
            loaded (/usr/lib/systemd/system/firewalld.service; enabled;
            vendor preset: enabled)
        

   Active:
            active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months
            11 days ago
        

     Docs:
            man:firewalld(1)
        

Main PID: 883
            (firewalld)
        

   CGroup:
            /system.slice/firewalld.service
        

          
            ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork
            --nopid
        

 
        

Apr 01
            05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic
            firewall daemon.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
            'beyond-scope' is not supported by the kernel for ipv6.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope:
            INVALID_ICMPTYPE: No supported ICMP type., ignoring for
            run-time.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
            'failed-policy' is not supported by the kernel for ipv6.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy:
            INVALID_ICMPTYPE: No supported ICMP type., ignoring for
            run-time.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
            'reject-route' is not supported by the kernel for ipv6.
        

Apr 01
            05:49:30 cemtore01 firewalld[883]: WARNING: reject-route:
            INVALID_ICMPTYPE: No supported ICMP type., ignoring for
            run-time.
        

May 22
            11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
        

May 22
            11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE:
            ports
        

May 22
            11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
        

 
        
          

Bikram
                Majumdar
          

Sr
              Software Developer/DBA, Aqsacom Inc.
          

c.
              1.972.365.3737
          

 
          


          

 
          

Disclaimer.
              This
              electronic mail message contains CONFIDENTIAL information
              which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
              COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR
              OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b)
              intended only for the use of the Addressee(s) named
              herein. If you are not an Addressee, or the person
              responsible for delivering this to an Addressee, you are
              hereby notified that reading, copying, or distributing
              this message is prohibited. If you have received this
              electronic mail message in error, please reply to the
              sender and take the steps necessary to delete the message
              completely from your computer system.
              Statement and opinions expressed
                in this e-mail are those of the sender, and do not
                necessarily reflect those of AQSACOM. AQSACOM accepts no
                liability for any damage caused by any virus/worms
                transmitted by this email.
        
        

 
        
          
            

From: Tim Scheurenbrand
              <info@timscheurenbrand.de> 

              Sent: Monday, August 12, 2019 4:25 PM

              To: Bikram MAJUMDAR
              <Bikram.Majumdar@aqsacom.com>;
              pgsql-admin@postgresql.org

              Cc: bikramma@gmail.com

              Subject: Re: Need help in establishing pgadmin4 to
              connect to the postgres database server when the database
              is listening on port 5433 (instead of port 5432)
          
        
        

 
        
          

Hi
              Bikram
        
        
          

Have
              you checked your firewall settings?
        
        
          

Tim
              Scheurenbrand
        
        



          

          
        
          

On Mon, Aug
            12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com>
            wrote:
          
            
              

 
              

Hi ,
              

We need
                  help in resolving connection issues using the pgadmin
                  tool.
              

We had
                  our pgadmin (pgadmin4) installed a few months back on
                  windows 10 and we were able to use it for  our
                  postgres server running on port 5432.
              

But,
                  recently we had to change our postgres server port
                  from 5433 to 5432 - 
                
              

And
                  accordingly, in pgadmin we changed the port also to
                  5433 – but we are receiving connection timed out error
                  in connecting to our server (see below screen shot).
                
              

 
              


              

 
              

 
              

Please
                  help to resolve this issue.
              

 
              

Bikram
                    Majumdar
              

Sr
                  Software Developer/DBA, Aqsacom Inc.
              

c.
                  1.972.365.3737
                
              

e.
                  bikram.majumdar@aqsacom.com
                
                
              

s. BIKRAM
                  MAJUMDAR
              

 
              


              

 
              

Disclaimer.
                  This
                  electronic mail message contains CONFIDENTIAL
                  information which is (a) CUSTOMER / SUPPLIER / PARTNER
                  PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN
                  NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE,
                  and (b) intended only for the use of the Addressee(s)
                  named herein. If you are not an Addressee, or the
                  person responsible for delivering this to an
                  Addressee, you are hereby notified that reading,
                  copying, or distributing this message is prohibited.
                  If you have received this electronic mail message in
                  error, please reply to the sender and take the steps
                  necessary to delete the message completely from your
                  computer system.
                  Statement and opinions
                    expressed in this e-mail are those of the sender,
                    and do not necessarily reflect those of AQSACOM.
                    AQSACOM accepts no liability for any damage caused
                    by any virus/worms transmitted by this email.
              

 
            
          
        
      
    
    

    -- 

      Angular momentum makes the world go 'round.
  

Attachments:

image004.png (image/png, 10.0K) download view image
image006.jpg (image/jpeg, 29.6K) download view image
image008.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
@ 2019-08-12 22:19       ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  1 sibling, 1 reply; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-12 22:19 UTC (permalink / raw)
  To: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Ron,

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

Thanks and regards,

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image005.png@01D55132.0FDF1330]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ron <ronljohnsonjr@gmail.com>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433
On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image006.png@01D55132.0FDF1330]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de><mailto:info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com><mailto:Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>
Cc: bikramma@gmail.com<mailto:bikramma@gmail.com>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand



On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image007.jpg@01D55132.0FDF1330]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image008.png@01D55132.0FDF1330]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


--
Angular momentum makes the world go 'round.


Attachments:

image005.png (image/png, 10.0K) download view image
image006.png (image/png, 10.0K) download view image
image007.jpg (image/jpeg, 29.2K) download view image
image008.png (image/png, 10.0K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-15 18:03         ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-15 18:03 UTC (permalink / raw)
  To: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Ron,

I still have some issues I need to resolve.
As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.
And, we can connect to port 5433.

But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.
And we are running pgpool on the same server where the database is running.
Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):

[cid:image008.png@01D55369.B4105B60]

But, connections from pg4admin are failing with pgpool running on port 5432:
IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool)

[cid:image012.png@01D55369.B4105B60]


Any idea?

Thanks and regards,
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image002.png@01D55369.C866F600]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Ron,

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

Thanks and regards,

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image004.png@01D55369.C866F600]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433
On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image006.png@01D55369.C866F600]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de><mailto:info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com><mailto:Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>
Cc: bikramma@gmail.com<mailto:bikramma@gmail.com>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand


On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image009.jpg@01D55369.C866F600]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image011.png@01D55369.C866F600]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


--
Angular momentum makes the world go 'round.


Attachments:

image008.png (image/png, 7.5K) download view image
image012.png (image/png, 22.4K) download view image
image002.png (image/png, 7.6K) download view image
image004.png (image/png, 7.6K) download view image
image006.png (image/png, 7.6K) download view image
image009.jpg (image/jpeg, 21.2K) download view image
image011.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-15 19:43           ` Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Ramakrishna Chava @ 2019-08-15 19:43 UTC (permalink / raw)
  To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Friends,

When start  database through pg_ctl  that port should be 5432 as per shared
screenshot details but while connect  to pgadmin 5433 means,those records
of from cache memory, to clear all logs and to stop/start service on
windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N
"postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).

Postgres,if doesn't run on 5433 port then should be give below error.

Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and
accepting
TCP/IP connections on port 5433?

Thank You,
Ram.

On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <
Bikram.Majumdar@aqsacom.com> wrote:

> Hi Ron,
>
>
>
> I still have some issues I need to resolve.
>
> As noted before in earlier email, we were able to resolve the connection
> issue by stopping and disabling firewall on the postgres database server.
>
> And, we can connect to port 5433.
>
>
>
> But the reason to switch postgresql port (from default 5432 to 5433) is
> that : we want to run pgpool for connection balance on port 5432, and
> postgresql on port 5433.
>
> And we are running pgpool on the same server where the database is
> running.
>
> Everything works fine on the postgresql server – we can connect to the
> database via pgpool port 5432 (no issues – see screenshot below):
>
>
>
>
>
> But, connections from pg4admin are failing with pgpool running on port
> 5432:
>
> IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin):
> HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not
> connecting via pgpool)
>
>
>
>
>
>
>
> Any idea?
>
>
>
> Thanks and regards,
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Bikram MAJUMDAR
> *Sent:* Monday, August 12, 2019 5:19 PM
> *To:* Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
> *Subject:* RE: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> Hi Ron,
>
>
>
> It was a firewall issue on the postgres database server. I think the
> firewall only opened up the default port 5432 when postgres was installed.
>
> I stopped the firewall on the postgres database server  and now I am able
> to connect from pgadmin.
>
>
>
> Thanks and regards,
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Ron <ronljohnsonjr@gmail.com>
> *Sent:* Monday, August 12, 2019 5:14 PM
> *To:* pgsql-admin@lists.postgresql.org
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> There are more firewalls than just the one running (or not) on cemtore01.
>
> Keep things simple and just run a traceroute from the server running
> pgadmin4 to the server running postgres.
>
> If that works, then telnet to the server on port 5433
>
> On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
>
> Hi Tim,
>
>
>
> Thanks for your quick response.
>
> Are you thinking port 5433 is not opened for listening on the postgres
> database server?
>
> [root@cemtore01 ~]# systemctl status firewalld.service
>
> â firewalld.service - firewalld - dynamic firewall daemon
>
>    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
> vendor preset: enabled)
>
>    Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11
> days ago
>
>      Docs: man:firewalld(1)
>
> Main PID: 883 (firewalld)
>
>    CGroup: /system.slice/firewalld.service
>
>            ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
>
>
>
> Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall
> daemon.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'beyond-scope' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'failed-policy' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'reject-route' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
>
> May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
>
> May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Tim Scheurenbrand <info@timscheurenbrand.de>
> <info@timscheurenbrand.de>
> *Sent:* Monday, August 12, 2019 4:25 PM
> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
> <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
> *Cc:* bikramma@gmail.com
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> Hi Bikram
>
> Have you checked your firewall settings?
>
> Tim Scheurenbrand
>
>
>
> On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <
> Bikram.Majumdar@aqsacom.com> wrote:
>
>
>
> Hi ,
>
> We need help in resolving connection issues using the pgadmin tool.
>
> We had our pgadmin (pgadmin4) installed a few months back on windows 10
> and we were able to use it for  our postgres server running on port 5432.
>
> But, recently we had to change our postgres server port from 5433 to 5432
> -
>
> And accordingly, in pgadmin we changed the port also to 5433 – but we are
> receiving connection timed out error in connecting to our server (see below
> screen shot).
>
>
>
>
>
>
>
> Please help to resolve this issue.
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
> *e.* bikram.majumdar@aqsacom.com
>
> *s.* BIKRAM MAJUMDAR
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
>
>
> --
> Angular momentum makes the world go 'round.
>

Attachments:

image008.png (image/png, 7.5K) download view image
image012.png (image/png, 22.4K) download view image
image002.png (image/png, 7.6K) download view image
image004.png (image/png, 7.6K) download view image
image006.png (image/png, 7.6K) download view image
image009.jpg (image/jpeg, 21.2K) download view image
image011.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
@ 2019-08-15 20:14             ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  0 siblings, 1 reply; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-15 20:14 UTC (permalink / raw)
  To: Ramakrishna Chava <chavarkit@gmail.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Ramakrisna,

I am not sure I understand what you are trying to explain.

To be a little more clear :  Postgres database is running  as a service by running the following command:
# systemctl start postgresql

And postgresql is running on port 5433 (see below):

[cid:image010.png@01D5537C.22B05810]
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image001.png@01D5537C.22B86E60]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ramakrishna Chava <chavarkit@gmail.com>
Sent: Thursday, August 15, 2019 2:43 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)


Hi Friends,

When start  database through pg_ctl  that port should be 5432 as per shared screenshot details but while connect  to pgadmin 5433 means,those records of from cache memory, to clear all logs and to stop/start service on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).

Postgres,if doesn't run on 5433 port then should be give below error.

Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and accepting
TCP/IP connections on port 5433?

Thank You,
Ram.

On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:
Hi Ron,

I still have some issues I need to resolve.
As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.
And, we can connect to port 5433.

But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.
And we are running pgpool on the same server where the database is running.
Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):

[cid:image003.png@01D5537B.EEC6DAB0]

But, connections from pg4admin are failing with pgpool running on port 5432:
IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool)

[cid:image004.png@01D5537B.EEC6DAB0]


Any idea?

Thanks and regards,
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image005.png@01D5537B.EEC6DAB0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>; pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Ron,

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

Thanks and regards,

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image006.png@01D5537B.EEC6DAB0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433
On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image007.png@01D5537B.EEC6DAB0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de><mailto:info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com><mailto:Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>
Cc: bikramma@gmail.com<mailto:bikramma@gmail.com>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand

On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image008.jpg@01D5537B.EEC6DAB0]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image009.png@01D5537B.EEC6DAB0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


--
Angular momentum makes the world go 'round.


Attachments:

image003.png (image/png, 7.5K) download view image
image004.png (image/png, 22.4K) download view image
image005.png (image/png, 7.6K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
image010.png (image/png, 45.8K) download view image
image001.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-15 20:43               ` Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-16 07:37                 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) arnab biswas <arnab.biswas@associates.scit.edu>
  0 siblings, 1 reply; 17+ messages in thread

From: Ramakrishna Chava @ 2019-08-15 20:43 UTC (permalink / raw)
  To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

 Hi Bikram,

I read the subject and misunderstand of the problem.

You  are able  to start database with 5433 port number means, either 5432
port  firewal blocked or to clear all s_% logs from temp directory and
restart the server.

Still, if you have any issues and let me know status.

Thank You,
Ram.


On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
wrote:

> Hi Ramakrisna,
>
>
>
> I am not sure I understand what you are trying to explain.
>
>
>
> To be a little more clear :  Postgres database is running  as a service by
> running the following command:
>
> # systemctl start postgresql
>
>
>
> And postgresql is running on port 5433 (see below):
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Ramakrishna Chava <chavarkit@gmail.com>
> *Sent:* Thursday, August 15, 2019 2:43 PM
> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
> *Cc:* Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
>
>
> Hi Friends,
>
>
>
> When start  database through pg_ctl  that port should be 5432 as per
> shared screenshot details but while connect  to pgadmin 5433 means,those
> records of from cache memory, to clear all logs and to stop/start service
> on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N
> "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).
>
>
>
> Postgres,if doesn't run on 5433 port then should be give below error.
>
>
>
> Unable to connect to server:
>
> could not connect to server: Connection refused (0x0000274D/10061)
> Is the server running on host "test_server-01" (114.102.170.244) and
> accepting
> TCP/IP connections on port 5433?
>
>
>
> Thank You,
>
> Ram.
>
>
>
> On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <
> Bikram.Majumdar@aqsacom.com> wrote:
>
> Hi Ron,
>
>
>
> I still have some issues I need to resolve.
>
> As noted before in earlier email, we were able to resolve the connection
> issue by stopping and disabling firewall on the postgres database server.
>
> And, we can connect to port 5433.
>
>
>
> But the reason to switch postgresql port (from default 5432 to 5433) is
> that : we want to run pgpool for connection balance on port 5432, and
> postgresql on port 5433.
>
> And we are running pgpool on the same server where the database is
> running.
>
> Everything works fine on the postgresql server – we can connect to the
> database via pgpool port 5432 (no issues – see screenshot below):
>
>
>
>
>
> But, connections from pg4admin are failing with pgpool running on port
> 5432:
>
> IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin):
> HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not
> connecting via pgpool)
>
>
>
>
>
>
>
> Any idea?
>
>
>
> Thanks and regards,
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Bikram MAJUMDAR
> *Sent:* Monday, August 12, 2019 5:19 PM
> *To:* Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
> *Subject:* RE: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> Hi Ron,
>
>
>
> It was a firewall issue on the postgres database server. I think the
> firewall only opened up the default port 5432 when postgres was installed.
>
> I stopped the firewall on the postgres database server  and now I am able
> to connect from pgadmin.
>
>
>
> Thanks and regards,
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Ron <ronljohnsonjr@gmail.com>
> *Sent:* Monday, August 12, 2019 5:14 PM
> *To:* pgsql-admin@lists.postgresql.org
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> There are more firewalls than just the one running (or not) on cemtore01.
>
> Keep things simple and just run a traceroute from the server running
> pgadmin4 to the server running postgres.
>
> If that works, then telnet to the server on port 5433
>
> On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
>
> Hi Tim,
>
>
>
> Thanks for your quick response.
>
> Are you thinking port 5433 is not opened for listening on the postgres
> database server?
>
> [root@cemtore01 ~]# systemctl status firewalld.service
>
> â firewalld.service - firewalld - dynamic firewall daemon
>
>    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
> vendor preset: enabled)
>
>    Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11
> days ago
>
>      Docs: man:firewalld(1)
>
> Main PID: 883 (firewalld)
>
>    CGroup: /system.slice/firewalld.service
>
>            ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
>
>
>
> Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall
> daemon.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'beyond-scope' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'failed-policy' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
> 'reject-route' is not supported by the kernel for ipv6.
>
> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route:
> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>
> May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
>
> May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
>
> May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
> *From:* Tim Scheurenbrand <info@timscheurenbrand.de>
> <info@timscheurenbrand.de>
> *Sent:* Monday, August 12, 2019 4:25 PM
> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
> <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
> *Cc:* bikramma@gmail.com
> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
> postgres database server when the database is listening on port 5433
> (instead of port 5432)
>
>
>
> Hi Bikram
>
> Have you checked your firewall settings?
>
> Tim Scheurenbrand
>
>
>
> On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <
> Bikram.Majumdar@aqsacom.com> wrote:
>
>
>
> Hi ,
>
> We need help in resolving connection issues using the pgadmin tool.
>
> We had our pgadmin (pgadmin4) installed a few months back on windows 10
> and we were able to use it for  our postgres server running on port 5432.
>
> But, recently we had to change our postgres server port from 5433 to 5432
> -
>
> And accordingly, in pgadmin we changed the port also to 5433 – but we are
> receiving connection timed out error in connecting to our server (see below
> screen shot).
>
>
>
>
>
>
>
> Please help to resolve this issue.
>
>
>
> *Bikram Majumdar*
>
> Sr Software Developer/DBA, Aqsacom Inc.
>
> *c.* 1.972.365.3737
>
> *e.* bikram.majumdar@aqsacom.com
>
> *s.* BIKRAM MAJUMDAR
>
>
>
> <http://www.aqsacom.com/;
>
>
>
> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
> Addressee(s) named herein. If you are not an Addressee, or the person
> responsible for delivering this to an Addressee, you are hereby notified
> that reading, copying, or distributing this message is prohibited. If you
> have received this electronic mail message in error, please reply to the
> sender and take the steps necessary to delete the message completely from
> your computer system. Statement and opinions expressed in this e-mail are
> those of the sender, and do not necessarily reflect those of AQSACOM.
> AQSACOM accepts no liability for any damage caused by any virus/worms
> transmitted by this email.
>
>
>
>
>
> --
> Angular momentum makes the world go 'round.
>
>

Attachments:

image003.png (image/png, 7.5K) download view image
image004.png (image/png, 22.4K) download view image
image005.png (image/png, 7.6K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
image010.png (image/png, 45.8K) download view image
image001.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
@ 2019-08-16 07:37                 ` arnab biswas <arnab.biswas@associates.scit.edu>
  2019-08-16 07:53                   ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) manish yadav <manishy174@yahoo.co.in>
  2019-08-16 14:38                   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  0 siblings, 2 replies; 17+ messages in thread

From: arnab biswas @ 2019-08-16 07:37 UTC (permalink / raw)
  To: Ramakrishna Chava <chavarkit@gmail.com>; +Cc: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Bikram,

Use netstat -lnt to see what services are running. I think some other
service is running on 5432 because of which your postgresql is running on
5433.

Regards,

Arnab Biswas

On Fri, 16 Aug, 2019, 02:13 Ramakrishna Chava, <chavarkit@gmail.com> wrote:

>  Hi Bikram,
>
> I read the subject and misunderstand of the problem.
>
> You  are able  to start database with 5433 port number means, either 5432
> port  firewal blocked or to clear all s_% logs from temp directory and
> restart the server.
>
> Still, if you have any issues and let me know status.
>
> Thank You,
> Ram.
>
>
> On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <
> Bikram.Majumdar@aqsacom.com> wrote:
>
>> Hi Ramakrisna,
>>
>>
>>
>> I am not sure I understand what you are trying to explain.
>>
>>
>>
>> To be a little more clear :  Postgres database is running  as a service
>> by running the following command:
>>
>> # systemctl start postgresql
>>
>>
>>
>> And postgresql is running on port 5433 (see below):
>>
>>
>>
>> *Bikram Majumdar*
>>
>> Sr Software Developer/DBA, Aqsacom Inc.
>>
>> *c.* 1.972.365.3737
>>
>>
>>
>> <http://www.aqsacom.com/;
>>
>>
>>
>> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
>> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
>> Addressee(s) named herein. If you are not an Addressee, or the person
>> responsible for delivering this to an Addressee, you are hereby notified
>> that reading, copying, or distributing this message is prohibited. If you
>> have received this electronic mail message in error, please reply to the
>> sender and take the steps necessary to delete the message completely from
>> your computer system. Statement and opinions expressed in this e-mail
>> are those of the sender, and do not necessarily reflect those of AQSACOM.
>> AQSACOM accepts no liability for any damage caused by any virus/worms
>> transmitted by this email.
>>
>>
>>
>> *From:* Ramakrishna Chava <chavarkit@gmail.com>
>> *Sent:* Thursday, August 15, 2019 2:43 PM
>> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
>> *Cc:* Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
>> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
>> postgres database server when the database is listening on port 5433
>> (instead of port 5432)
>>
>>
>>
>>
>>
>> Hi Friends,
>>
>>
>>
>> When start  database through pg_ctl  that port should be 5432 as per
>> shared screenshot details but while connect  to pgadmin 5433 means,those
>> records of from cache memory, to clear all logs and to stop/start service
>> on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N
>> "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).
>>
>>
>>
>> Postgres,if doesn't run on 5433 port then should be give below error.
>>
>>
>>
>> Unable to connect to server:
>>
>> could not connect to server: Connection refused (0x0000274D/10061)
>> Is the server running on host "test_server-01" (114.102.170.244) and
>> accepting
>> TCP/IP connections on port 5433?
>>
>>
>>
>> Thank You,
>>
>> Ram.
>>
>>
>>
>> On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <
>> Bikram.Majumdar@aqsacom.com> wrote:
>>
>> Hi Ron,
>>
>>
>>
>> I still have some issues I need to resolve.
>>
>> As noted before in earlier email, we were able to resolve the connection
>> issue by stopping and disabling firewall on the postgres database server.
>>
>> And, we can connect to port 5433.
>>
>>
>>
>> But the reason to switch postgresql port (from default 5432 to 5433) is
>> that : we want to run pgpool for connection balance on port 5432, and
>> postgresql on port 5433.
>>
>> And we are running pgpool on the same server where the database is
>> running.
>>
>> Everything works fine on the postgresql server – we can connect to the
>> database via pgpool port 5432 (no issues – see screenshot below):
>>
>>
>>
>>
>>
>> But, connections from pg4admin are failing with pgpool running on port
>> 5432:
>>
>> IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin):
>> HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not
>> connecting via pgpool)
>>
>>
>>
>>
>>
>>
>>
>> Any idea?
>>
>>
>>
>> Thanks and regards,
>>
>> *Bikram Majumdar*
>>
>> Sr Software Developer/DBA, Aqsacom Inc.
>>
>> *c.* 1.972.365.3737
>>
>>
>>
>> <http://www.aqsacom.com/;
>>
>>
>>
>> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
>> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
>> Addressee(s) named herein. If you are not an Addressee, or the person
>> responsible for delivering this to an Addressee, you are hereby notified
>> that reading, copying, or distributing this message is prohibited. If you
>> have received this electronic mail message in error, please reply to the
>> sender and take the steps necessary to delete the message completely from
>> your computer system. Statement and opinions expressed in this e-mail are
>> those of the sender, and do not necessarily reflect those of AQSACOM.
>> AQSACOM accepts no liability for any damage caused by any virus/worms
>> transmitted by this email.
>>
>>
>>
>> *From:* Bikram MAJUMDAR
>> *Sent:* Monday, August 12, 2019 5:19 PM
>> *To:* Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
>> *Subject:* RE: Need help in establishing pgadmin4 to connect to the
>> postgres database server when the database is listening on port 5433
>> (instead of port 5432)
>>
>>
>>
>> Hi Ron,
>>
>>
>>
>> It was a firewall issue on the postgres database server. I think the
>> firewall only opened up the default port 5432 when postgres was installed.
>>
>> I stopped the firewall on the postgres database server  and now I am able
>> to connect from pgadmin.
>>
>>
>>
>> Thanks and regards,
>>
>>
>>
>> *Bikram Majumdar*
>>
>> Sr Software Developer/DBA, Aqsacom Inc.
>>
>> *c.* 1.972.365.3737
>>
>>
>>
>> <http://www.aqsacom.com/;
>>
>>
>>
>> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
>> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
>> Addressee(s) named herein. If you are not an Addressee, or the person
>> responsible for delivering this to an Addressee, you are hereby notified
>> that reading, copying, or distributing this message is prohibited. If you
>> have received this electronic mail message in error, please reply to the
>> sender and take the steps necessary to delete the message completely from
>> your computer system. Statement and opinions expressed in this e-mail are
>> those of the sender, and do not necessarily reflect those of AQSACOM.
>> AQSACOM accepts no liability for any damage caused by any virus/worms
>> transmitted by this email.
>>
>>
>>
>> *From:* Ron <ronljohnsonjr@gmail.com>
>> *Sent:* Monday, August 12, 2019 5:14 PM
>> *To:* pgsql-admin@lists.postgresql.org
>> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
>> postgres database server when the database is listening on port 5433
>> (instead of port 5432)
>>
>>
>>
>> There are more firewalls than just the one running (or not) on cemtore01.
>>
>> Keep things simple and just run a traceroute from the server running
>> pgadmin4 to the server running postgres.
>>
>> If that works, then telnet to the server on port 5433
>>
>> On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
>>
>> Hi Tim,
>>
>>
>>
>> Thanks for your quick response.
>>
>> Are you thinking port 5433 is not opened for listening on the postgres
>> database server?
>>
>> [root@cemtore01 ~]# systemctl status firewalld.service
>>
>> â firewalld.service - firewalld - dynamic firewall daemon
>>
>>    Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
>> vendor preset: enabled)
>>
>>    Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months
>> 11 days ago
>>
>>      Docs: man:firewalld(1)
>>
>> Main PID: 883 (firewalld)
>>
>>    CGroup: /system.slice/firewalld.service
>>
>>            ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
>>
>>
>>
>> Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic
>> firewall daemon.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
>> 'beyond-scope' is not supported by the kernel for ipv6.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope:
>> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
>> 'failed-policy' is not supported by the kernel for ipv6.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy:
>> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type
>> 'reject-route' is not supported by the kernel for ipv6.
>>
>> Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route:
>> INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
>>
>> May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
>>
>> May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
>>
>> May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
>>
>>
>>
>> *Bikram Majumdar*
>>
>> Sr Software Developer/DBA, Aqsacom Inc.
>>
>> *c.* 1.972.365.3737
>>
>>
>>
>> <http://www.aqsacom.com/;
>>
>>
>>
>> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
>> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
>> Addressee(s) named herein. If you are not an Addressee, or the person
>> responsible for delivering this to an Addressee, you are hereby notified
>> that reading, copying, or distributing this message is prohibited. If you
>> have received this electronic mail message in error, please reply to the
>> sender and take the steps necessary to delete the message completely from
>> your computer system. Statement and opinions expressed in this e-mail are
>> those of the sender, and do not necessarily reflect those of AQSACOM.
>> AQSACOM accepts no liability for any damage caused by any virus/worms
>> transmitted by this email.
>>
>>
>>
>> *From:* Tim Scheurenbrand <info@timscheurenbrand.de>
>> <info@timscheurenbrand.de>
>> *Sent:* Monday, August 12, 2019 4:25 PM
>> *To:* Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
>> <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
>> *Cc:* bikramma@gmail.com
>> *Subject:* Re: Need help in establishing pgadmin4 to connect to the
>> postgres database server when the database is listening on port 5433
>> (instead of port 5432)
>>
>>
>>
>> Hi Bikram
>>
>> Have you checked your firewall settings?
>>
>> Tim Scheurenbrand
>>
>>
>>
>> On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <
>> Bikram.Majumdar@aqsacom.com> wrote:
>>
>>
>>
>> Hi ,
>>
>> We need help in resolving connection issues using the pgadmin tool.
>>
>> We had our pgadmin (pgadmin4) installed a few months back on windows 10
>> and we were able to use it for  our postgres server running on port 5432.
>>
>> But, recently we had to change our postgres server port from 5433 to 5432
>> -
>>
>> And accordingly, in pgadmin we changed the port also to 5433 – but we are
>> receiving connection timed out error in connecting to our server (see below
>> screen shot).
>>
>>
>>
>>
>>
>>
>>
>> Please help to resolve this issue.
>>
>>
>>
>> *Bikram Majumdar*
>>
>> Sr Software Developer/DBA, Aqsacom Inc.
>>
>> *c.* 1.972.365.3737
>>
>> *e.* bikram.majumdar@aqsacom.com
>>
>> *s.* BIKRAM MAJUMDAR
>>
>>
>>
>> <http://www.aqsacom.com/;
>>
>>
>>
>> *Disclaimer. *This electronic mail message contains CONFIDENTIAL
>> information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED
>> COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED
>> BY LAW FROM DISCLOSURE, and (b) intended only for the use of the
>> Addressee(s) named herein. If you are not an Addressee, or the person
>> responsible for delivering this to an Addressee, you are hereby notified
>> that reading, copying, or distributing this message is prohibited. If you
>> have received this electronic mail message in error, please reply to the
>> sender and take the steps necessary to delete the message completely from
>> your computer system. Statement and opinions expressed in this e-mail are
>> those of the sender, and do not necessarily reflect those of AQSACOM.
>> AQSACOM accepts no liability for any damage caused by any virus/worms
>> transmitted by this email.
>>
>>
>>
>>
>>
>> --
>> Angular momentum makes the world go 'round.
>>
>>

Attachments:

image009.png (image/png, 7.6K) download view image
image001.png (image/png, 7.6K) download view image
image005.png (image/png, 7.6K) download view image
image010.png (image/png, 45.8K) download view image
image003.png (image/png, 7.5K) download view image
image004.png (image/png, 22.4K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-16 07:37                 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) arnab biswas <arnab.biswas@associates.scit.edu>
@ 2019-08-16 07:53                   ` manish yadav <manishy174@yahoo.co.in>
  2019-08-16 14:44                     ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  1 sibling, 1 reply; 17+ messages in thread

From: manish yadav @ 2019-08-16 07:53 UTC (permalink / raw)
  To: Ramakrishna Chava <chavarkit@gmail.com>; arnab biswas <arnab.biswas@associates.scit.edu>; +Cc: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi,
Please verify port 5433 of database machine is accessible (telnet port 5433) from the server where pgadmin is installed. If it's accessible it should work after changing port 5433 in connection settings and pg_hba entry available in remote database instance.


Thanks and Regards,
Manish Yadav
Mobile : +91 8527607945 

    On Friday, 16 August 2019, 1:10:03 PM IST, arnab biswas <arnab.biswas@associates.scit.edu> wrote:  
 
 Hi Bikram, 
Use netstat -lnt to see what services are running. I think some other service is running on 5432 because of which your postgresql is running on 5433.

Regards,

Arnab Biswas

On Fri, 16 Aug, 2019, 02:13 Ramakrishna Chava, <chavarkit@gmail.com> wrote:

 Hi Bikram,
I read the subject and misunderstand of the problem.
You  are able  to start database with 5433 port number means, either 5432 port  firewal blocked or to clear all s_% logs from temp directory and restart the server.
Still, if you have any issues and let me know status.
Thank You,Ram.

On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com> wrote:


Hi Ramakrisna,

 

I am not sure I understand what you are trying to explain.

 

To be a little more clear :  Postgres database is running  as a service by running the following command:

# systemctl start postgresql

 

And postgresql is running on port 5433 (see below):

 



Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

 



 

Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 

From: Ramakrishna Chava <chavarkit@gmail.com> 
Sent: Thursday, August 15, 2019 2:43 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

 

 

Hi Friends,

 

When start  database through pg_ctl  that port should be 5432 as per shared screenshot details but while connect  to pgadmin 5433 means,those records of from cache memory, to clear all logs and to stop/start service on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).

 

Postgres,if doesn't run on 5433 port then should be give below error.

 

Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and accepting
TCP/IP connections on port 5433?

 

Thank You,

Ram.

 

On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com> wrote:


Hi Ron,

 

I still have some issues I need to resolve.

As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.

And, we can connect to port 5433.

 

But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.  

And we are running pgpool on the same server where the database is running.

Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):

 



 

But, connections from pg4admin are failing with pgpool running on port 5432:

IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool) 

 



 

 

Any idea?

 

Thanks and regards,

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

 



 

Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 

From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com>;pgsql-admin@lists.postgresql.org
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

 

Hi Ron,

 

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.

I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

 

Thanks and regards,

 

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

 



 

Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 

From: Ron <ronljohnsonjr@gmail.com>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

 

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433

On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:


Hi Tim,

 

Thanks for your quick response.

Are you thinking port 5433 is not opened for listening on the postgres database server?

[root@cemtore01 ~]# systemctl status firewalld.service

â firewalld.service - firewalld - dynamic firewall daemon

   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)

   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago

     Docs: man:firewalld(1)

Main PID: 883 (firewalld)

   CGroup: /system.slice/firewalld.service

           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

 

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port

May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports

May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

 

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

 



 

Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 

From: Tim Scheurenbrand<info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

 

Hi Bikram

Have you checked your firewall settings?

Tim Scheurenbrand

 

On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:


 

Hi ,

We need help in resolving connection issues using the pgadmin tool.

We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.

But, recently we had to change our postgres server port from 5433 to 5432 - 

And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot). 

 



 

 

Please help to resolve this issue.

 

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

e.bikram.majumdar@aqsacom.com

s. BIKRAM MAJUMDAR

 



 

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 



 

--
Angular momentum makes the world go 'round.



  

Attachments:

image004.png (image/png, 22.4K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image001.png (image/png, 7.6K) download view image
image005.png (image/png, 7.6K) download view image
image010.png (image/png, 45.8K) download view image
image003.png (image/png, 7.5K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-16 07:37                 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) arnab biswas <arnab.biswas@associates.scit.edu>
  2019-08-16 07:53                   ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) manish yadav <manishy174@yahoo.co.in>
@ 2019-08-16 14:44                     ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-17 06:38                       ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) manish yadav <manishy174@yahoo.co.in>
  0 siblings, 1 reply; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-16 14:44 UTC (permalink / raw)
  To: manish yadav <manishy174@yahoo.co.in>; Ramakrishna Chava <chavarkit@gmail.com>; arnab biswas <arnab.biswas@associates.scit.edu>; +Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Manish,
Thanks for helping.
First of all – all our ports are open on the server as we have stopped/disabled firewall.
And, we can connect to the postgressql server from pgadmin server on any port – 5432 or 5433 when we are not running  pgpool on the database server.
The problem comes when we are running pgpool on port 5432 on the database server. Connections from pgadmin tool specifying port 5432 does not work.

Thanks and regards,
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image010.png@01D55417.22C08140]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: manish yadav <manishy174@yahoo.co.in>
Sent: Friday, August 16, 2019 2:53 AM
To: Ramakrishna Chava <chavarkit@gmail.com>; arnab biswas <arnab.biswas@associates.scit.edu>
Cc: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi,

Please verify port 5433 of database machine is accessible (telnet port 5433) from the server where pgadmin is installed. If it's accessible it should work after changing port 5433 in connection settings and pg_hba entry available in remote database instance.



Thanks and Regards,

Manish Yadav
Mobile : +91 8527607945


On Friday, 16 August 2019, 1:10:03 PM IST, arnab biswas <arnab.biswas@associates.scit.edu<mailto:arnab.biswas@associates.scit.edu>> wrote:


Hi Bikram,

Use netstat -lnt to see what services are running. I think some other service is running on 5432 because of which your postgresql is running on 5433.
Regards,

Arnab Biswas

On Fri, 16 Aug, 2019, 02:13 Ramakrishna Chava, <chavarkit@gmail.com<mailto:chavarkit@gmail.com>> wrote:
 Hi Bikram,

I read the subject and misunderstand of the problem.

You  are able  to start database with 5433 port number means, either 5432 port  firewal blocked or to clear all s_% logs from temp directory and restart the server.

Still, if you have any issues and let me know status.

Thank You,
Ram.


On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi Ramakrisna,



I am not sure I understand what you are trying to explain.



To be a little more clear :  Postgres database is running  as a service by running the following command:

# systemctl start postgresql



And postgresql is running on port 5433 (see below):



[cid:image002.png@01D55417.22B3B000]

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737



[cid:image003.png@01D55417.22B3B000]<http://www.aqsacom.com/;



Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



From: Ramakrishna Chava <chavarkit@gmail.com<mailto:chavarkit@gmail.com>>
Sent: Thursday, August 15, 2019 2:43 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>>
Cc: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>; pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)





Hi Friends,



When start  database through pg_ctl  that port should be 5432 as per shared screenshot details but while connect  to pgadmin 5433 means,those records of from cache memory, to clear all logs and to stop/start service on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).



Postgres,if doesn't run on 5433 port then should be give below error.



Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and accepting
TCP/IP connections on port 5433?



Thank You,

Ram.



On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi Ron,



I still have some issues I need to resolve.

As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.

And, we can connect to port 5433.



But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.

And we are running pgpool on the same server where the database is running.

Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):



[cid:image004.png@01D55417.22B3B000]



But, connections from pg4admin are failing with pgpool running on port 5432:

IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool)



[cid:image005.png@01D55417.22B3B000]





Any idea?



Thanks and regards,

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737



[cid:image003.png@01D55417.22B3B000]<http://www.aqsacom.com/;



Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>; pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)



Hi Ron,



It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.

I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.



Thanks and regards,



Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737



[cid:image006.png@01D55417.22B3B000]<http://www.aqsacom.com/;



Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)



There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433

On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:

Hi Tim,



Thanks for your quick response.

Are you thinking port 5433 is not opened for listening on the postgres database server?

[root@cemtore01 ~]# systemctl status firewalld.service

â firewalld.service - firewalld - dynamic firewall daemon

   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)

   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago

     Docs: man:firewalld(1)

Main PID: 883 (firewalld)

   CGroup: /system.slice/firewalld.service

           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid



Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port

May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports

May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone



Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737



[cid:image007.png@01D55417.22B3B000]<http://www.aqsacom.com/;



Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.



From: Tim Scheurenbrand <info@timscheurenbrand.de><mailto:info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com><mailto:Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>
Cc: bikramma@gmail.com<mailto:bikramma@gmail.com>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)



Hi Bikram

Have you checked your firewall settings?

Tim Scheurenbrand



On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:



Hi ,

We need help in resolving connection issues using the pgadmin tool.

We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.

But, recently we had to change our postgres server port from 5433 to 5432 -

And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).



[cid:image008.jpg@01D55417.22B3B000]





Please help to resolve this issue.



Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>

s. BIKRAM MAJUMDAR



[cid:image009.png@01D55417.22B3B000]<http://www.aqsacom.com/;



Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.





--
Angular momentum makes the world go 'round.


Attachments:

image002.png (image/png, 45.8K) download view image
image003.png (image/png, 7.6K) download view image
image004.png (image/png, 7.5K) download view image
image005.png (image/png, 22.4K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
image010.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-16 07:37                 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) arnab biswas <arnab.biswas@associates.scit.edu>
  2019-08-16 07:53                   ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) manish yadav <manishy174@yahoo.co.in>
  2019-08-16 14:44                     ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
@ 2019-08-17 06:38                       ` manish yadav <manishy174@yahoo.co.in>
  0 siblings, 0 replies; 17+ messages in thread

From: manish yadav @ 2019-08-17 06:38 UTC (permalink / raw)
  To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Bikram,
As I understand from previous mails, you are now able to connect from pgAdmin machine to remote database machine on port 5432/5433 without using pgpool and finding difficulty while connecting to database using pgpool.
You might need to check pgpool configuration settings whether it's allowed to accept connection from remote machine and ensure pgpool is running on port 5432.
listen_addresses = '*'

Also see pgpool logs for more details.


Thanks and Regards,
Manish Yadav
Mobile : +91 8527607945 

    On Friday, 16 August 2019, 8:14:36 PM IST, Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com> wrote:  
 
 #yiv0917755068 #yiv0917755068 -- _filtered #yiv0917755068 {font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv0917755068 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv0917755068 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv0917755068 {font-family:Cambria;panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv0917755068 {font-family:Old;panose-1:2 5 6 4 5 5 5 2 2 4;} _filtered #yiv0917755068 {font-family:Garamond;panose-1:2 2 4 4 3 3 1 1 8 3;}#yiv0917755068 #yiv0917755068 p.yiv0917755068MsoNormal, #yiv0917755068 li.yiv0917755068MsoNormal, #yiv0917755068 div.yiv0917755068MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:sans-serif;}#yiv0917755068 a:link, #yiv0917755068 span.yiv0917755068MsoHyperlink {color:blue;text-decoration:underline;}#yiv0917755068 a:visited, #yiv0917755068 span.yiv0917755068MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv0917755068 p.yiv0917755068msonormal0, #yiv0917755068 li.yiv0917755068msonormal0, #yiv0917755068 div.yiv0917755068msonormal0 {margin-right:0in;margin-left:0in;font-size:11.0pt;font-family:sans-serif;}#yiv0917755068 p.yiv0917755068msonormal, #yiv0917755068 li.yiv0917755068msonormal, #yiv0917755068 div.yiv0917755068msonormal {margin-right:0in;margin-left:0in;font-size:11.0pt;font-family:sans-serif;}#yiv0917755068 span.yiv0917755068EmailStyle20 {font-family:serif;color:windowtext;font-weight:normal;font-style:normal;}#yiv0917755068 .yiv0917755068MsoChpDefault {font-size:10.0pt;} _filtered #yiv0917755068 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv0917755068 div.yiv0917755068WordSection1 {}#yiv0917755068 
Hi Manish,
 
Thanks for helping.
 
First of all – all our ports are open on the server as we have stopped/disabled firewall.
 
And, we can connect to the postgressql server from pgadmin server on any port – 5432 or 5433 when we are not running  pgpool on the database server.
 
The problem comes when we are running pgpool on port 5432 on the database server. Connections from pgadmin tool specifying port 5432 does not work.   
 
  
 
Thanks and regards,
 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
  
 

 
  
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
  
 
From: manish yadav <manishy174@yahoo.co.in> 
Sent: Friday, August 16, 2019 2:53 AM
To: Ramakrishna Chava <chavarkit@gmail.com>; arnab biswas <arnab.biswas@associates.scit.edu>
Cc: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
 
  
 
Hi,
 
  
 
Please verify port 5433 of database machine is accessible (telnet port 5433) from the server where pgadmin is installed. If it's accessible it should work after changing port 5433 in connection settings and pg_hba entry available in remote database instance.
 
  
 
  
 
  
 
Thanks and Regards,
 
  
 
Manish Yadav
Mobile : +91 8527607945
 
  
 
  
 
On Friday, 16 August 2019, 1:10:03 PM IST, arnab biswas <arnab.biswas@associates.scit.edu> wrote:
 
  
 
  
 
Hi Bikram, 
 
  
 
Use netstat -lnt to see what services are running. I think some other service is running on 5432 because of which your postgresql is running on 5433.
 
Regards,

Arnab Biswas
 
  
 
On Fri, 16 Aug, 2019, 02:13 Ramakrishna Chava, <chavarkit@gmail.com> wrote:
 

 Hi Bikram,
 
  
 
I read the subject and misunderstand of the problem.
 
  
 
You  are able  to start database with 5433 port number means, either 5432 port  firewal blocked or to clear all s_% logs from temp directory and restart the server.
 
  
 
Still, if you have any issues and let me know status.
 
  
 
Thank You,
 
Ram.
 
  
 
  
 
On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com> wrote:
 

Hi Ramakrisna,
 
 
 
I am not sure I understand what you are trying to explain.
 
 
 
To be a little more clear :  Postgres database is running  as a service by running the following command:
 
# systemctl start postgresql
 
 
 
And postgresql is running on port 5433 (see below):
 
 
 

 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
 
 

 
 
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system.Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
 
 
From: Ramakrishna Chava <chavarkit@gmail.com>
Sent: Thursday, August 15, 2019 2:43 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
Cc: Ron <ronljohnsonjr@gmail.com>;pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
 
 
 
 
 
Hi Friends,
 
 
 
When start  database through pg_ctl  that port should be 5432 as per shared screenshot details but while connect  to pgadmin 5433 means,those records of from cache memory, to clear all logs and to stop/start service on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).
 
 
 
Postgres,if doesn't run on 5433 port then should be give below error.
 
 
 
Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and accepting
TCP/IP connections on port 5433?
 
 
 
Thank You,
 
Ram.
 
 
 
On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com> wrote:
 

Hi Ron,
 
 
 
I still have some issues I need to resolve.
 
As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.
 
And, we can connect to port 5433.
 
 
 
But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.  
 
And we are running pgpool on the same server where the database is running.
 
Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):
 
 
 

 
 
 
But, connections from pg4admin are failing with pgpool running on port 5432:
 
IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool) 
 
 
 

 
 
 
 
 
Any idea?
 
 
 
Thanks and regards,
 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
 
 

 
 
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
 
 
From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com>;pgsql-admin@lists.postgresql.org
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
 
 
 
Hi Ron,
 
 
 
It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
 
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.
 
 
 
Thanks and regards,
 
 
 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
 
 

 
 
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
 
 
From: Ron <ronljohnsonjr@gmail.com>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
 
 
 
There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433
 
On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
 

Hi Tim,
 
 
 
Thanks for your quick response.
 
Are you thinking port 5433 is not opened for listening on the postgres database server?
 
[root@cemtore01 ~]# systemctl status firewalld.service
 
â firewalld.service - firewalld - dynamic firewall daemon
 
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
 
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
 
     Docs: man:firewalld(1)
 
Main PID: 883 (firewalld)
 
   CGroup: /system.slice/firewalld.service
 
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
 
 
 
Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
 
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
 
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
 
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
 
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone
 
 
 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
 
 

 
 
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
 
 
From: Tim Scheurenbrand<info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
 
 
 
Hi Bikram
 
Have you checked your firewall settings?
 
Tim Scheurenbrand
 
 
 
On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:
 

 
 
Hi ,
 
We need help in resolving connection issues using the pgadmin tool.
 
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
 
But, recently we had to change our postgres server port from 5433 to 5432 - 
 
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot). 
 
 
 

 
 
 
 
 
Please help to resolve this issue.
 
 
 
Bikram Majumdar
 
Sr Software Developer/DBA, Aqsacom Inc.
 
c. 1.972.365.3737
 
e.bikram.majumdar@aqsacom.com
 
s. BIKRAM MAJUMDAR
 
 
 

 
 
 
Disclaimer.This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.
 
 
 


 
 
--
Angular momentum makes the world go 'round.
 


  

Attachments:

image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image004.png (image/png, 7.5K) download view image
image005.png (image/png, 22.4K) download view image
image010.png (image/png, 7.6K) download view image
image002.png (image/png, 45.8K) download view image
image003.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread

* RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)
  2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 21:24 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Tim Scheurenbrand <info@timscheurenbrand.de>
  2019-08-12 21:51   ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-12 22:14     ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ron <ronljohnsonjr@gmail.com>
  2019-08-12 22:19       ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 18:03         ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 19:43           ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-15 20:14             ` RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  2019-08-15 20:43               ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Ramakrishna Chava <chavarkit@gmail.com>
  2019-08-16 07:37                 ` Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) arnab biswas <arnab.biswas@associates.scit.edu>
@ 2019-08-16 14:38                   ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
  1 sibling, 0 replies; 17+ messages in thread

From: Bikram MAJUMDAR @ 2019-08-16 14:38 UTC (permalink / raw)
  To: arnab biswas <arnab.biswas@associates.scit.edu>; Ramakrishna Chava <chavarkit@gmail.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hi Arnab,

Thanks.  If you have followed the email chain, I am running pgpool (postgres connection pooling) on port 5432  -- and postgresql on port 5433.

The problem in connection arises when I specify port 5432 in pgadmin to force connection pooling via pgpool.  But, if I specify port 5433 in pgadmin everything works – but then I am not using connection pooling for pgadmin connections.

Thanks and regards,
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image010.png@01D55416.46F988F0]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: arnab biswas <arnab.biswas@associates.scit.edu>
Sent: Friday, August 16, 2019 2:38 AM
To: Ramakrishna Chava <chavarkit@gmail.com>
Cc: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; Ron <ronljohnsonjr@gmail.com>; pgsql-admin@lists.postgresql.org
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram,

Use netstat -lnt to see what services are running. I think some other service is running on 5432 because of which your postgresql is running on 5433.
Regards,

Arnab Biswas

On Fri, 16 Aug, 2019, 02:13 Ramakrishna Chava, <chavarkit@gmail.com<mailto:chavarkit@gmail.com>> wrote:
 Hi Bikram,

I read the subject and misunderstand of the problem.

You  are able  to start database with 5433 port number means, either 5432 port  firewal blocked or to clear all s_% logs from temp directory and restart the server.

Still, if you have any issues and let me know status.

Thank You,
Ram.


On Fri, Aug 16, 2019 at 1:44 AM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:
Hi Ramakrisna,

I am not sure I understand what you are trying to explain.

To be a little more clear :  Postgres database is running  as a service by running the following command:
# systemctl start postgresql

And postgresql is running on port 5433 (see below):

[cid:image002.png@01D55416.46EFEC00]
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image003.png@01D55416.46EFEC00]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ramakrishna Chava <chavarkit@gmail.com<mailto:chavarkit@gmail.com>>
Sent: Thursday, August 15, 2019 2:43 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>>
Cc: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>; pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)


Hi Friends,

When start  database through pg_ctl  that port should be 5432 as per shared screenshot details but while connect  to pgadmin 5433 means,those records of from cache memory, to clear all logs and to stop/start service on windows machine ("C:\PostgreSQL\11\bin\pg_ctl.exe" runservice -N "postgresql-x64-11" -D "C:\PostgreSQL\11\data" -w).

Postgres,if doesn't run on 5433 port then should be give below error.

Unable to connect to server:

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host "test_server-01" (114.102.170.244) and accepting
TCP/IP connections on port 5433?

Thank You,
Ram.

On Thu, Aug 15, 2019 at 11:33 PM Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:
Hi Ron,

I still have some issues I need to resolve.
As noted before in earlier email, we were able to resolve the connection issue by stopping and disabling firewall on the postgres database server.
And, we can connect to port 5433.

But the reason to switch postgresql port (from default 5432 to 5433) is that : we want to run pgpool for connection balance on port 5432, and postgresql on port 5433.
And we are running pgpool on the same server where the database is running.
Everything works fine on the postgresql server – we can connect to the database via pgpool port 5432 (no issues – see screenshot below):

[cid:image004.png@01D55416.46EFEC00]

But, connections from pg4admin are failing with pgpool running on port 5432:
IT CANNOT CONNECT VIA PGPOOL (i.e when we specify port 5432 in pg4admin): HOWEVER, IT CONNECTS FINE WHEN WE USE PORT 5433 (i.e when we are not connecting via pgpool)

[cid:image005.png@01D55416.46EFEC00]


Any idea?

Thanks and regards,
Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image003.png@01D55416.46EFEC00]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Bikram MAJUMDAR
Sent: Monday, August 12, 2019 5:19 PM
To: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>; pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Ron,

It was a firewall issue on the postgres database server. I think the firewall only opened up the default port 5432 when postgres was installed.
I stopped the firewall on the postgres database server  and now I am able to connect from pgadmin.

Thanks and regards,

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image006.png@01D55416.46EFEC00]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Ron <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>>
Sent: Monday, August 12, 2019 5:14 PM
To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

There are more firewalls than just the one running (or not) on cemtore01.

Keep things simple and just run a traceroute from the server running pgadmin4 to the server running postgres.

If that works, then telnet to the server on port 5433
On 8/12/19 4:51 PM, Bikram MAJUMDAR wrote:
Hi Tim,

Thanks for your quick response.
Are you thinking port 5433 is not opened for listening on the postgres database server?
[root@cemtore01 ~]# systemctl status firewalld.service
â firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago
     Docs: man:firewalld(1)
Main PID: 883 (firewalld)
   CGroup: /system.slice/firewalld.service
           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.
Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.
May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port
May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports
May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737

[cid:image007.png@01D55416.46EFEC00]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

From: Tim Scheurenbrand <info@timscheurenbrand.de><mailto:info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com><mailto:Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>
Cc: bikramma@gmail.com<mailto:bikramma@gmail.com>
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Hi Bikram
Have you checked your firewall settings?
Tim Scheurenbrand

On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com<mailto:Bikram.Majumdar@aqsacom.com>> wrote:

Hi ,
We need help in resolving connection issues using the pgadmin tool.
We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.
But, recently we had to change our postgres server port from 5433 to 5432 -
And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

[cid:image008.jpg@01D55416.46EFEC00]


Please help to resolve this issue.

Bikram Majumdar
Sr Software Developer/DBA, Aqsacom Inc.
c. 1.972.365.3737
e. bikram.majumdar@aqsacom.com<mailto:bikram.majumdar@aqsacom.com>
s. BIKRAM MAJUMDAR

[cid:image009.png@01D55416.46EFEC00]<http://www.aqsacom.com/;

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.


--
Angular momentum makes the world go 'round.


Attachments:

image002.png (image/png, 45.8K) download view image
image003.png (image/png, 7.6K) download view image
image004.png (image/png, 7.5K) download view image
image005.png (image/png, 22.4K) download view image
image006.png (image/png, 7.6K) download view image
image007.png (image/png, 7.6K) download view image
image008.jpg (image/jpeg, 21.2K) download view image
image009.png (image/png, 7.6K) download view image
image010.png (image/png, 7.6K) download view image
^ permalink raw reply [nested|flat] 17+ messages in thread


end of thread, other threads:[~2019-08-17 06:38 UTC | newest]

Thread overview: 17+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-08-12 21:08 Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432) Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-12 21:24 ` Tim Scheurenbrand <info@timscheurenbrand.de>
2019-08-12 21:51   ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-12 22:09     ` Tim Scheurenbrand <info@timscheurenbrand.de>
2019-08-12 22:18       ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-12 22:14     ` Ron <ronljohnsonjr@gmail.com>
2019-08-12 22:16       ` Tim Scheurenbrand <info@timscheurenbrand.de>
2019-08-12 22:19       ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-15 18:03         ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-15 19:43           ` Ramakrishna Chava <chavarkit@gmail.com>
2019-08-15 20:14             ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-15 20:43               ` Ramakrishna Chava <chavarkit@gmail.com>
2019-08-16 07:37                 ` arnab biswas <arnab.biswas@associates.scit.edu>
2019-08-16 07:53                   ` manish yadav <manishy174@yahoo.co.in>
2019-08-16 14:44                     ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>
2019-08-17 06:38                       ` manish yadav <manishy174@yahoo.co.in>
2019-08-16 14:38                   ` Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox