IBM Support

Operations Center logs remote monitoring errors in activity log

Technote (troubleshooting)


Problem(Abstract)

An IBM Spectrum Protect server configured as hub server is later configured as a spoke server. After the configuration change, various errors are logged in the activity logs of both the hub server and the spoke server.

Symptom

In this case, the two servers are SERVER1 (hub) and SERVER2 (spoke).

The hub server, SERVER1, shows the following errors :

ANR0102E tbcli.c(2183): Error 1202 inserting row in table "TSMMon.Status".
ANR2183W monstats.c(6467): Transaction 0:154713533 was aborted.
ANR0530W Transaction failed for session 82257 for node SERVER2 (Windows) - internal server error detected.
ANR1991I Remote monitoring ended for server SERVER2.
ANR0486W Session nnn for node SERVER2 (Windows) terminated - internal error detected.
ANR9999D Thread<176> issued message 486 from:
ANR9999D Thread<176> 000007FEED8503BE outMsgf()+3e
ANR9999D Thread<176> 000007FEED64DF8A smServClose()+19a
ANR9999D Thread<176> 000007FEED66749A RemSrvMonThread()+10aa
ANR9999D Thread<176> 000007FEECED7641 startThread()+171
ANR9999D Thread<176> 000007FEF0B14F7F beginthreadex()+107
ANR9999D Thread<176> 000007FEF0B15126 endthreadex()+192
ANR9999D Thread<176> 0000000077515A4D BaseThreadInitThunk()+d
ANR9999D Thread<176> 00000000777AB831 RtlUserThreadStart()+21


The spoke server, SERVER2, shows the following errors :

ANR0104E monalert.c(4089): Error 1114 deleting row from table "TSMMon.Alert".
ANR0530W Transaction failed for session nnn for node SERVER1 (Windows) - internal server error detected.
ANR1991I Remote monitoring ended for server SERVER1.
ANR0486W Session 217 for node SERVER1 (Windows) terminated - internal error detected.
ANR9999D Thread<166> issued message 486 from:
ANR9999D Thread<166> 000007FEEB8603BE outMsgf()+3e
ANR9999D Thread<166> 000007FEEB65DF8A smServClose()+19a
ANR9999D Thread<166> 000007FEEB67749A RemSrvMonThread()+10aa
ANR9999D Thread<166> 000007FEEAEE7641 startThread()+171
ANR9999D Thread<166> 000007FEEADD4F7F beginthreadex()+107
ANR9999D Thread<166> 000007FEEADD5126 endthreadex()+192
ANR9999D Thread<166> 0000000076D05A4D BaseThreadInitThunk()+d
ANR9999D Thread<166> 0000000076E3B831 RtlUserThreadStart()+21


Diagnosing the problem

Run the QUERY SERVERGROUP command on each server. For example :

The command on SERVER1 (hub) shows this result :

Server Group      Members        
--------------    -------------  
IBM-OC-SERVER1    SERVER2  


The command on SERVER2 (spoke) shows this result :

Server Group       Members        
--------------     -------------  
IBM-OC-SERVER2     SERVER1

The query results show that both SERVER1 and SERVER2 are incorrectly configured as hub and spoke servers at the same time.


Resolving the problem

In this case, the server identified as SERVER1 should be the hub server and SERVER2 should be the spoke server. Run the following IBM Spectrum Protect server administrative commands on the SERVER2 server to remove the hub configuration from it :


DELETE GRPMEMBER IBM-OC-SERVER2 SERVER1
SET MONITOREDSERVERGROUP ""
DELETE SERVERGROUP IBM-OC-SERVER2
SET MONITORINGADMIN ""
SET STATUSMONITOR OFF
SET ALERTMONITOR OFF
REMOVE ADMIN IBM-OC-SERVER2

Document information

More support for: Tivoli Storage Manager
Server

Software version: All Supported Versions

Operating system(s): Platform Independent

Reference #: 1971748

Modified date: 23 October 2017


Translate this page: