Support Centre

Find articles, help and advice.

 
Welcome, Guest Login

Support Center

BES - Rogue workfile causing AlertServer Connection failure

Last Updated: Jan 29, 2015 02:53PM UTC
Although there can be various causes to AlertServer connection failures, such as a high volume of active alerts or no space left in the BES database, one potential cause could be down to the dbi not processing the integration workfiles. Whenever you experience AlertServer connection failures, check the $PPLOG/POWERpack_Log and $PPLOG/dbi_Log.

If the connection issue is related to the dbi not processing workfiles, or the dbi is trying to process through a backlog of workfiles, you may see the following error messages in the POWERpack_Log and dbi_Log:


POWERpack_Log:
20150128 15:22:35 POWERpackTrans:(System) Establishing Connection to Alert Server Socket 30000
20150128 15:22:35 POWERpackTrans:(System) Alert Server Connection failed(111 Connection refused) -1
20150128 15:22:36 EventDaemon:  EventDaemon waiting for ASConnection to initialise
20150128 15:22:37 POWERpackTrans:(AMON) Establishing Connection to Alert Server Socket 30000
20150128 15:22:37 POWERpackTrans:(AMON) Alert Server Connection failed(111 Connection refused) -1
20150128 15:22:37 PPDbiInterface isReady : Error reading from Socket
20150128 15:22:37 PPDbiInterface isReady : Exception is Read timed out


dbi_Log:
20150128 15:21:22 DbiJM: Waiting for catch up to process
20150128 15:21:32 WorkFileServer: Currentfile = 345883307
20150128 15:21:32 WorkFileServer: Filename = 345883307
20150128 15:21:32 WorkFileServer: No new file avialable - waiting
20150128 15:21:37 AServer: Received 'Is Ready' query from AlertServer
20150128 15:21:37 AServer: Replied 'Is Not Ready' to AlertServer


A telnet to the dbi ( telnet localhost 40004 > option s ) should indicate which line and workfile the dbi is currently up to in its processing. If you make a note of the workfile number from the stats list, check the date/time of the workfile under $PPWORK/Integrations by issuing ls -lart <workfile_no>. If the integration workfile is quite old, or does not exist, then this could be causing the connection issue.

** If you notice a workfile named '000000000' under $PPWORK/Integrations, this could be the underlying cause and should be deleted! See steps below for guidelines.

To get the AlertServer connected, you may need to reset the dbi marker and point it to the latest integration workfile. To do this, perform the following:
 
  1. Stop the dbi (ppStop -n dbi).
  2. Find the latest workfile number from $PPWORK/Integrations and make a note of it.
  3. If there is a workfile named '000000000', delete it.
  4. Open an SQL session to the BES database (DBcon).
  5. Update the DBI Marker for each thread as follows (replace xxxxxxxx with the DBI workfile number from step 2):

1> Update ISS_PP_DbiMarker_Table
2> set fileName = '/var/spool/ISS/POWERpack/xxxxxxxx', filePosition = 0
3> where KeyName = 'DbiJM Thd1'
4> go

1> Update ISS_PP_DbiMarker_Table
2> set fileName = '/var/spool/ISS/POWERpack/xxxxxxxx', filePosition = 0
3> where KeyName = 'DbiJM Thd2'
4> go

1> Update ISS_PP_DbiMarker_Table
2> set fileName = '/var/spool/ISS/POWERpack/xxxxxxxx', filePosition = 0
3> where KeyName = 'DbiJM Thd3'
4> go

 
  1. Exit out of the SQL session and start the dbi (ppStart -n dbi)
  2. Check the $PPLOG/POWERpack_Log and $PPLOG/dbi_Log to see if the AlertServer has now established a connection.

‚ÄčIf you are still experiencing AlertServer connection issues and are unsure what the cause could be, please contact Interlink Software Support for assistance.
 

Contact Us

desk.com@interlinksoftware.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete