Error "Database on system with hostname ______ is not responding"


This error occurs when a managing system cannot communicate with one of its sources or managed systems.


This issue appears in two forms:

When clicking on a system in the navigation pane, the error message pops up "Database on system with hostname ______ is not responding"

Alternatively, in the navigation pane of the legacy UI, you may see an '!' next to the system. Hovering over the system causes a tooltip to pop-up stating "This system was incompletely loaded". 


  1. From the command line, ping the source system to verify that the target is able to communicate with the source. 
  2. Verify that the source system is listed as "is_active" in the target's database. This command will automatically correct the database if the source is listed as inactive.
    psql -U postgres bpdb -c "update set is_active='t'"
  3. Verify that you can communicate with the source system database, and that the source system has the target system listed as a manager. (HOSTNAME in the sample below should be replaced by the actual hostname of the managed system)
    psql -U postgres bpdb -h HOSTNAME -c "select * from bp.managers"
If you cannot communicate with the source database after all steps have been completed, then there is likely an error in /usr/bp/data/pg_hba.conf on the source, or /usr/bp/data/pg_service.conf on the target. 

Only the last part of pg_hba.conf is configurable, and should look like this:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all               trust
# IPv6 local connections:
host    all             all             ::1/128                 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
host    bpdb    +bpexch,wguest              md5
hostssl bpdb     postgres         trust

These lines are required at minimum but there may also be additional entries. 

pg_service.conf should appear as follows:





Where HOSTNAME is again replaced by the hostname of the managed system. Make any needed corrections to these files, restart the database, and then repeat step 2 to resolve the issue. 


This error occurs when communication is interrupted between the two systems, often due to network outages. 

Damage to the pg_hba and pg_service files is usually caused by an improper dump and reload of the database. 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section