Errors in DB2 8.0 db2diag.log We have a very old PeopleSoft HR system running on DB2 8.x.  Numerous times a day we get the following errors in the db2diag.log file.

 2019-11-04-01.22.24.012784-300 E16054C794         LEVEL: Error (OS)
 PID     : 229596               TID  : 772         PROC : db2hmon 0
 INSTANCE: hrprod               NODE : 000
 FUNCTION: DB2 UDB, oper system services, sqloPdbConnectSocket, probe:20 
 MESSAGE : ZRC=0x810F0019=-2129723367=SQLO_CONN_REFUSED "Connection refused"
 CALLED  : OS, -, connect
 OSERR   : ECONNREFUSED (79) "Connection refused"
 DATA #1 : String, 32 bytes
 Unable to connect socket on path
 DATA #2 : socket, 4 bytes
 7
 DATA #3 : sockaddr, 39 bytes
 0x303B4F38 : 0001 2F75 7372 2F75 7365 7273 2F64 6232    ../usr/users/db2
 0x303B4F48 : 6173 2F64 6173 2F74 6D70 2F64 6173 6E61    as/das/tmp/dasna
 0x303B4F58 : 6D65 6470 6970 65                          medpipe
 DATA #4 : File name, 37 bytes
 /usr/users/db2as/das/tmp/dasnamedpipe


We're not sure what's causing the error but the reference to DAS in the error has me thinking the instance is trying to connect to the DAS server, or maybe the other way around.  The DBA who was responsible for the system said the error has appeared for a long time and he couldn't figure out the cause but it had no noticeable negative implications on functionality.  He retired last week.  I'd like to fix the issue if possible.   I'm not familiar with 8.4 and it's use of DAS other than DAS being needed to administer multiple instances, using a GUI, on the same server (there's only one instance on the server).

Any help tracking this down greatly appreciated. :)

Richard
Check the following if it's applicable to your case:
ECONNREFUSED (79) "Connection refused" message in the db2diag.log for the db2hmon process.


  Cause
  
  The DB2 Health Monitor periodically wakes up and checks for a
  connection to the DB2 administration server (DAS).  
  
  Resolving The Problem
  
  This type of error is reported when the DAS (DB2 administration
  server) is not active. When the health monitor wakes up it checks for
  a connection to the DAS. In this case the connection is refused as
  either the DAS does not exist or it is not started.