Question 2 Replies 160 Views × Close popover Tharine Nagulendran (TharineN) AI4Process AI4Process GB View Profile Send Message TharineN Member since 2017 7 posts AI4Process Posted: June 27, 2018 Last activity: July 11, 2018 Posted: 27 Jun 2018 13:38 EDT Last activity: 11 Jul 2018 4:25 EDT Closed How to update postgres port in Pega 7.3.1 PE Hi, I have successfully installed Pega 7.3.1 PE in my local system, then installed another instance of Pega 7.3.1 PE with different app server port and DB port (5435) in the same system. After shutting down the 2nd instace started the 1st instance, but this time the 1st PE instance is failing on startup, because the connection to DB port (5432) is getting refused. when I checked my port statuses postgres.exe is listening to 5434. How can I resolve this issue? System Administration Installation and Deployment Data Integration × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years ago Posted: 28 Jun 2018 7:25 EDT × Close popover Mohammad Asif Hasan (Asif Hasan) PEGA Senior Technical Solutions Engineer Pegasystems Inc. IN View Profile Send Message Asif Hasan PEGA replied to TharineN Hi, Thanks for posting on PSC. It seems to be a generic issue with postgres instead Pega. You have to edit postgresql.conf file and change line with 'listen_addresses'. This file you can find in the /etc/postgresql/9.3/main directory. Refer:- Can't connect to postgresql port 5432 - https://github.com/PostgresApp/PostgresApp/issues/37 Hope it helps, additionally I'll try to find any Pega related bug which might be causing it and update here. Regards. Asif Posted: 2 years ago Posted: 11 Jul 2018 4:25 EDT × Close popover Tharine Nagulendran (TharineN) AI4Process AI4Process GB View Profile Send Message TharineN AI4Process replied to Asif Hasan Hi Asif, Thanks for the response. My observation : The Issue is getting fixed when, starting the tom cat server after restarting the whole system. (shutdown tomcat server -> restart the system -> start the tomcat server) Could not fix the issue as mentioned above, in the system where I didn't have the admin rights!!