Error connecting to the server pgadmin

When connecting to a PostgreSQL server, you may get an error message. If you
encounter an error message, please review the message carefully; each error
message attempts to incorporate the information you’ll need to resolve the
problem. For more details about specific errors, please locate the error
message in the list below:

Connection to the server has been lost

This error message indicates that the connection attempt has taken longer than
the specified threshold; there may be a problem with the connection properties
provided on the Server dialog, network connectivity issues, or the server may
not be running.

could not connect to Server: Connection refused

If pgAdmin displays this message, there are two possible reasons for this:

the database server isn’t running — simply start it.
the server isn’t configured to accept TCP/IP requests on the address shown.

For security reasons, a PostgreSQL server “out of the box” doesn’t listen on
TCP/IP ports. Instead, it must be enabled to listen for TCP/IP requests. This
can be done by adding listen_addresses=’*’; this will make the server accept
connections on any IP interface.

For further information, please refer to the PostgreSQL documentation about
runtime configuration.

FATAL: no pg_hba.conf entry

If pgAdmin displays this message when connecting, your server can be contacted
correctly over the network, but is not configured to accept your connection.
Your client has not been detected as a legal user for the database.

To connect to a server, the pg_hba.conf file on the database server must be
configured to accept connections from the host of the pgAdmin client. Modify
the pg_hba.conf file on the database server host, and add an entry in the form:

host template1 postgres 192.168.0.0/24 md5 for an IPV4 network

host template1 postgres ::ffff:192.168.0.0/120 md5 for an IPV6 network

For more information, please refer to the PostgreSQL documentation about
client authentication.

FATAL: password authentication failed

The password authentication failed for user error message indicates there
may be a problem with the password you entered. Retry the password to confirm
you entered it correctly. If the error message returns, make sure that you have
the correct password, that you are authorized to access the server, and that
the access has been correctly configured in the server’s postgresql.conf
configuration file.

Источник

I have installed pgadmin on a new windows laptop and when I try to create a new server, it says:

When I try to run my django app in pycharm it is giving me the same error

could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host «localhost» (127.0.0.1) and accepting
TCP/IP connections on port 5432?

How to solve this ?

asked Jul 19, 2019 at 9:27

Rahul SharmaRahul Sharma

1,9704 gold badges25 silver badges67 bronze badges

You may need to installing PostgreSQL Server first.

You can verify if the folder is created in the below folder,
C:Program FilesPostgreSQL

answered Aug 25, 2020 at 4:00

In case someone is running the pgadmin-4 in docker, and not able to connect to postgres container, like me.
The solution is to first find the ip at which the docker image is running.

Step-1, make sure the postgres container is running.

Step-2 write command- PS C:docker> docker ps
Should result as below or similar,

Step3- in order to find the ip address running the postgres use part of container ID and analyze like below command

PS C:docker> docker inspect fc834

Note: Here I have only used part of container id that is fc834..

This should result the following or similar,
Step4-

Use this ip address in the connection as below with your correct username and password

answered Jun 12, 2022 at 19:50

KjkKjk

3014 silver badges3 bronze badges

You can configurate your newly created server to run on localhost and port 5432.

First select the “Connection” tab in the “Create-Server” window. Then, configure the connection as follows:

Enter your server’s IP address in the “Hostname/ Address” field. Default is localhost.
Specify the “Port” as “5432”.
Enter the name of the database in the “Database Maintenance” field.
Enter your username as postgres and password (use the same password you used when previously configuring the server to accept remote connections) for the database.
Click “Save” to apply the configuration.

NOTE You first have to install PostgreSQL on your machine and run it or run it with docker.

answered Jul 19, 2019 at 9:44

StevyStevy

3,0587 gold badges22 silver badges38 bronze badges

I had the same issue. But in my case I had installed pgadmin in version 9. But also installed version 12 at the same time.

When I now uninstalled version 9, the port was already set in the config of version 12 and not given free.

So my solution was to change the port of version 12 in the postgresql.conf file. Or even simplier, change the port in the server creation from 5432 to 5433. Now you are able to create a server again.

answered Nov 7, 2019 at 9:41

kwoxerkwoxer

3,7044 gold badges42 silver badges67 bronze badges

You should uninstall Postgres and pgAdmin from your PC. Then install postgres, note that you have the option of installing pgAdmin together with Postgres, so you don’t have to download pgAdmin separately. Allow the installation to complete then restart you PC. Hopefully you should be able to create your server/database

answered Aug 21, 2021 at 7:48

I was running postgress and pgadmin both using docker container.

sudo docker ps

sudo docker inspect <postgress_container_id>

Output:

   "Networks": {
        "work_file_default": {
            "IPAMConfig": null,
            "Links": null,
            "Aliases": [
                "postgres",
                "578a7a1050d1"
            ],
            "NetworkID": "49dbe9d7280b55e36afc4308469c1b55e051d7eea8f1c03f08728e652cf22b5b",
            "EndpointID": "c30a642c5a0f2970147c9734cadfbe1e8d7c29fcba8a83a628b7c2b3db114716",
            "Gateway": "172.18.0.1",
            **"IPAddress": "172.18.0.4",**
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "MacAddress": "02:42:ac:12:00:04",
            "DriverOpts": null
        }

Instead of localhost put the IP obtained from above command (172.18.0.4)

Antoine

1,3714 gold badges20 silver badges26 bronze badges

answered Dec 14, 2022 at 18:40

In my case was I got both pgadmin and postgresql services running in separate docker containers and I was trying to connect to localhost(127.0.0.1), which is cause of unable to connect to server error.

Note: 5438 port on my computer (host machine) was mapped to 5432 port of postgresql container.

so practically there are two solutions (if you have these services in separate containers and you have mapped postgresql port to your host machine ):

1-find out your local IP (mine is 192.168.1.106) and put it in the Host field.

2- you can put two containers(pgadmin and postgres) in one network (docker network)
and instead of your local IP, put postgres container IP in the Host field.

-Another tip that may help: what I’ve recently find out was if you are linux user and have ufw enabled, you should allow the port.

e.g. on my computer postgres is running on 5438 port, so I performed below command (so I could connect from pgadmin container to 5438 port of host wich postgres is running)

ufw allow 5438

answered Sep 15, 2022 at 10:01

Execute the container with the data Eg:

docker run --name postgresdb -e POSTGRES_USER=username -e POSTGRES_PASSWORD=password -e POSTGRES_DB=mydb -p 5432:5432 --restart always -d postgres

Then in the PGAdmin client in the Host Name/Address use:

host.docker.internal

Image Conn PGAdmin

answered Jan 9 at 3:08

I was trying to install PostgreSQL and pgAdmin with an installer that is given here https://www.postgresql.org/download/windows/. This installer includes the PostgreSQL server, pgAdmin;
I was facing an error while starting pgAdmin: «The pgAdmin 4 server could not be contacted». I tried different solutions but did not work.

Then I uninstalled both of them, deleted the temp folder C:Users%USERNAME%AppDataRoamingpgAdmin and delete those ones too %temp%.

Then I installed the pgAdmin separately from this link https://www.pgadmin.org/download/
and it works. If you need to connect it with your local server I think you should install the PostgreSQL server first and then pgAdmin separately.

answered May 18, 2021 at 11:57

I faced the same problem. So I uninstalled pgAdmin through control panel. after that deleted the folder where pgAdmin was located. Then I went to this link and installed pgadmin whole package from there and now it works fine.

answered Feb 17, 2022 at 15:45

JoharKhanJoharKhan

1862 silver badges7 bronze badges

I was getting this error when I was running pgadmin in a docker container on my machine, which meant that localhost:5432 was not accessible.

I worked around this by using the native version of pgadmin.

answered May 21, 2022 at 1:18

ngood97ngood97

5045 silver badges15 bronze badges

If you are running PostgreSQL in a docker container, set the host name in pgAdmin to postgres not the mapped address or localhost.

answered Sep 16, 2022 at 17:12

press win key+R then Search for services.msc A window will open in that find postgresql-x64-13 right click, in that tab click start option For me its works perfectly.
Check out this stackoverflow link

unable to connect to server for Postgres

answered Dec 11, 2022 at 5:50

how I solved this problem in ubuntu 22.04

I didn’t have a password set in Postgres, that’s why the error occurred ‘unable to connect server 127.0.0.0 port 5432
Open the terminal in ubuntu and enter this command;
sudo -u postgres psql
Run the statement to add new password. ALTER USER Postgres PASSWORD 'AddNewPasswordHere'; in » you should enter your new password

Example:

1)sudo -u postgres psql

2)ALTER USER postgres PASSWORD ‘mynewpassword’

3)sudo service postgresql restart

4)Then you can create a server in pgadmin

kofrasa

2,0702 gold badges14 silver badges10 bronze badges

answered Dec 26, 2022 at 0:13

If you already tried with “127.0.0.1” and it didn’t work then use “localhost”

answered Jan 18 at 16:34

Viand DirectViand Direct

3691 gold badge3 silver badges4 bronze badges

After two years i think this would be of good help to so many people.

You don’t have to uninstall postgresql or PGADMIN from your system.

What you need to do i input the username and password for a particular user created on postgresql into the server input box.

And that all you need.

i hope this helps anyone

answered May 28, 2022 at 17:44

Источник

I installed PostgreSQL on Windows 10 and the server appears to be in Task Manager. However, I get this error when opening pgAdmin4:

Failed to connect to the pgAdmin application server. Click here to try again.

Any ideas for what the problem is?

asked Jul 6, 2016 at 13:30

Did you try running the pgAdmin application as an administrator ?
I was having the same issue, but ran the application as an administrator and was able to connect.

answered Oct 3, 2016 at 8:24

RitzRitz

1411 silver badge3 bronze badges

I installed pgAdmin 4 via the EnterpriseDB PostgreSQL installer as well as the stand-alone Windows installer and had the same problem both times. Then I came across this: https://www.pgadmin.org/docs4/dev/desktop_deployment.html

It seems the Windows installer configures pgAdmin for server mode, and we need to switch it to Desktop mode. Why the installer does not have an option for this I do not know.

You should be able to getting it working by doing the following:

Modify config_local.py file in web folder, adding SERVER_MODE = False
Install python for windows, checking the box to add it to your path
Install the python packages necessary to run setup.py (see below)
Delete C:Users%USERNAME%AppDataRoamingpgAdminpgadmin4.db since upgrade mode seems to not work.
Run python setup.py from any command prompt

Here are the python packages I think I installed to get setup.py to work

pip install flask
pip install flask_security
pip install flask_babel
pip install django-htmlmin
pip install python-dateutil
pip install flask_sqlalchemy

answered Oct 6, 2016 at 3:44

rougourougou

1811 silver badge2 bronze badges

I had the same problem with pgAdmin 4 1.6 on Windows 7. The solution was simply to delete %appdata%pgAdmin which was created by an earlier version. On systems other than Windows, there probably is a pgAdmin directory in your user directory. Of course, all session settings etc. are gone after deleting this.

answered Jul 14, 2017 at 7:21

I had the same problem with pgadmin 3.0 on windows server 2016. What I did is not actually a solution but solved my problem at, least. I switch to an older version 2.1 that worked like a charm.

answered May 13, 2018 at 15:40

Источник

Connection errors

When connecting to a PostgreSQL server, you might get error messages
that need some more explanations. If you encounter them, please read the
following information carefully, we’re sure they will help you.

notrunning
no-hba

could not connect to Server: Connection refused

If this message appears, there are two possible reasons for this: either
the server isn’t running at all. Simply start it.

The other non-trivial cause for this message is that the server isn’t
configured to accept TCP/IP requests on the address shown.

For security reasons, a PostgreSQL server “out of the box” doesn’t
listen on TCP/IP ports. Instead, it has to be enabled to listen for
TCP/IP requests. This can be done by adding tcpip = true to the
postgresql.conf file for Versions 7.3.x and 7.4.x, or
listen_addresses=’*’ for Version 8.0.x and above; this will make the
server accept connections on any IP interface.

For further information, please refer to the PostgreSQL documentation
about runtime configuration.

FATAL: no pg_hba.conf entry

If this message appears, your server can be contacted correctly over the
network, but isn’t configured to accept your connection. Your client
isn’t detected as a legal user for the database.

You will have to add an entry in the form
host template1 postgres 192.168.0.0/24 md5 for IPV4 or
host template1 postgres ::ffff:192.168.0.0/120 md5 for IPV6 networks
to the pg_hba.conf file.

For further information, please refer to the PostgreSQL documentation
about client authentication.

Источник

Found these. We’ll give it a shot.

https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows

Windows debugging.

Open Environment Variables (WINDOWS key + BREAK)
Set environment variable «_NT_SYMBOL_PATH» for 4.2.

C:Program FilesPostgreSQL12debug_symbols;SRV*c:localsymbols*http://msdl.microsoft.com/download/symbols

open pgAdmin 4 > look for process in Task Manager and get process id
open Microsoft Visual Studio (run as administrator) > Debug > Attach to Process > check «Show processes from all users» > sort by process id > Attach
now go back in pgAdmin

Got a new popup I’ve never seen before from Visual Studio!

Created new virtual environment based on Python 3.8.

Created a new Visual Studio Project using Python, not C++. I might need a newer version of Python based on this fix.

https://github.com/microsoft/ptvs/issues/5853

https://bugs.python.org/issue37633

Since this new version does not show in the Base Interpreter, I created a new environment based on the zip file.

None of that worked. Then I stumbled upon the registry configuration for pgAdmin. I read that pgAdmin uses Python version 2.7. And the PythonPath variable was blank, so I set it to C:PythonPython27. So it must be using a value from somewhere else to get the path. It’s looking in sys.path in Python whatever that is.

Then I set ApplicationPath to C:Program FilespgAdmin 4v4web, to the folder where pgadmin4.py is located.

Here is the icon I’m clicking on each time.
«C:Program FilespgAdmin 4v4runtimepgAdmin4.exe»
«C:Program FilesPostgreSQL12pgAdmin 4binpgAdmin4.exe»

ERROR flask.app: Error starting the app server: (<class ‘OSError’>,
OSError(10013, ‘An attempt was made to access a socket in a way
forbidden by its access permissions’, None, 10013, None),

There are two pgAdmin folders. There are traces left over from the other pgAdmin uninstall.

C:Program Files (x86)pgAdmin 4files.txt
C:Program Files (x86)pgAdmin 4v4
C:Program Files (x86)pgAdmin 4v4venv
C:Program Files (x86)pgAdmin 4v4venvLib
C:Program Files (x86)pgAdmin 4v4venvLibcollections
C:Program Files (x86)pgAdmin 4v4venvLibencodings
C:Program Files (x86)pgAdmin 4v4venvLibimportlib
C:Program Files (x86)pgAdmin 4v4venvLibjson
C:Program Files (x86)pgAdmin 4v4venvLibsite-packages
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibcollections__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibcollections__pycache____init__.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache__aliases.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache__cp1252.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache__latin_1.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache__utf_8.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibencodings__pycache____init__.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibimportlib__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibimportlib__pycache__abc.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibimportlib__pycache__machinery.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibimportlib__pycache__util.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibimportlib__pycache____init__.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibjson__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibjson__pycache__decoder.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibjson__pycache__encoder.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibjson__pycache__scanner.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibjson__pycache____init__.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLibsite-packages__pycache__
C:Program Files (x86)pgAdmin 4v4venvLibsite-packages__pycache___virtualenv.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__abc.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__codecs.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__contextlib.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__copyreg.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__datetime.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__enum.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__functools.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__genericpath.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__heapq.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__io.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__keyword.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__ntpath.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__operator.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__os.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__re.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__reprlib.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__signal.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__site.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__sre_compile.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__sre_constants.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__sre_parse.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__stat.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__subprocess.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__threading.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__types.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache__warnings.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache___bootlocale.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache___collections_abc.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache___sitebuiltins.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache___weakrefset.cpython-38.pyc
C:Program Files (x86)pgAdmin 4v4venvLib__pycache____future__.cpython-38.pyc

FINALLY SOLVED IT! Flask within the Qt framework is NOT getting the port! I put some troubleshooting code into the source code.

C:Program FilespgAdmin 4v4webpgAdmin4.py

# Initialize Flask service only once
# If `WERKZEUG_RUN_MAIN` is None, i.e: app is initializing for first time
# so set `use_reloader` = False, thus reload won't call.
# Reference:
# https://github.com/pallets/werkzeug/issues/220#issuecomment-11176538
with open("myfile.txt", "w") as file1:
    file1.write("Testing")
    file1.write(config.DEFAULT_SERVER)
    file1.write(config.EFFECTIVE_SERVER_PORT)
try:
    app.run(
        host=config.DEFAULT_SERVER,
        port=config.EFFECTIVE_SERVER_PORT,
        use_reloader=(
            (not app.PGADMIN_RUNTIME) and app.debug and
            os.environ.get("WERKZEUG_RUN_MAIN") is not None
        ),
        threaded=config.THREADED_MODE
    )

except IOError:
    app.logger.error("Error starting the app server: %s", sys.exc_info())

Источник

Stepan Sidorov

@Stepan47

Я программист, преимущественно на Python, Java, С#

Я при создании сервера на pgadmin, сталкиваюсь с ошибкой:

Unable to connect to server:

could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?

Вот скриншот если кому не понятно где и как я это делаю:.
Вопрос короткий довольно короткий, как создть сервер?

Вопрос задан

более двух лет назад
2872 просмотра

Сначала нужно создать базу данных postgress (или другую), сделать на ней пользователя, и подкючить ее к pgadmin.

Пригласить эксперта

pgadmin — упрощенно «программа» для управления [уже работающим] сервером
то есть как минимум надо средствами ос установить и запустить postgresql хотя бы с минимальными настройками (логин, пароль)

Похожая проблема:
Сервер PG запущен на хосте. На этом же хосте запущен контейнер docker с pgAdmin.
В интерактиве на PG создан клиент postgres/пассворд и база postgres (как просят книжки)
В конфиге сервера листенер переписан в «*».
На докере создана дополнительная виртуальная сеть и контейнер pgadmin привязан к ней.
IP хоста из контейнера пингуется…
pgAdmin с базой не соединяется

какие еще есть варианты?

Показать ещё
Загружается…

09 февр. 2023, в 15:13

2000 руб./за проект

09 февр. 2023, в 15:06

2000 руб./за проект

09 февр. 2023, в 15:02

12000 руб./за проект

Минуточку внимания

Источник

Stuck with the error “pgAdmin connection to the server has been lost”? We can help you.

Often customers using PostgreSQL report to us that they get this error while trying to connect to PostgreSQL via pgAdmin.

Here at Bobcares, we often handle requests from our customers to fix similar PostgreSQL errors as a part of our Server Management Services. Today we will see how our support engineers fix this for our customers.

What causes pgAdmin “connection to the server has been lost” error?

Before going into the steps for fixing this error we will see what causes this error.

A typical error looks like the one given below.

Cause for the error

This error message indicates that the connection attempt has taken longer than the specified threshold; there may be a problem with the connection properties provided on the Server dialog, network connectivity issues, or the server may not be running.

Methods to fix pgAdmin “connection to the server has been lost”

Following are some of the methods that our support engineers use to fix this error for our customers.

1. Upgrade Pgadmin

We may get this error with pgadmin4 and it does not support PostgreSQL 9.

To fix this error we can upgrade to pgAdmin4 version 2.0.

We can do this from the URL given below:

https://www.pgadmin.org/download/

2. Reconnect the connection

Another method to fix this error is to try reconnecting the connection.

We can do this with the following steps:

1. First select the database where the connection was lost.

2. Then select SQL

3. Now enter the image description here.

4. After that PgAdmin will ask us if we would like to reconnect to this database. Now enter image description and click ok

We will notice a message retrieving data from the server.

3. Restarting PostgreSQL

This error could also trigger when the PostgreSQL database is not working. However, we can fix this by restarting the service.

This can be done with the following command:

#sudo service postgresql restart

After restarting we can try reconnecting to PostgreSQL again.

[Still, stuck with the error? We can help you]

Conclusion

In short, we saw how our Support Techs fix pgAdmin “connection to the server has been lost” error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

#The application server could not be contacted (Embedded PostgreSQL)

Note :
After upgrading the embedded PostgreSQL database version from 9.4.22 to 10.9 in version 2019.11, pgAdmin4 fails to lanuch on Linux platform with the following error: The application server could not be contacted.

Cause

Compared to pgAdmin3 included in PostgreSQL database version 9.4.22, pdAdmin4 included in PostgreSQL database version 10.9 is a different client executable file, which could not be executed on Linux platform,

#Solution

To enable launching the new pdAdmin4 client, a startup script was added, which then requires users to run the script in order to access the client.

Data Flow Probe

To access the client of the embedded PostgreSQL database (version 10 or later), do the following:

Run the following command to start the pgAdmin4 client:
$UCMDB_HOME/pgsql/pgAdmin 4/bin/start_pgadmin4.sh
Follow the on-screen instructions and access the local web browser using URL: http://127.0.0.1:5050.
Log in to the client

UCMDB server:

To access the client of the embedded PostgreSQL database (version 10 or later), do the following:

Run the following command to start the pgAdmin4 client:
$DATAFLOW_PROBE_HOME/pgsql/pgAdmin 4/bin/start_pgadmin4.sh
Follow the on-screen instructions and access the local web browser using URL: http://127.0.0.1:5050.
Log in to the client