Skip to Content

Server group log

The server group log tracks activity related to server groups. The starting and stopping of operations, the evaluation of other servers, recache requests, and the timing of each event are logged. In the server group log, the discrepancies in the servgrp_board table are also logged.

By default, the log file is named arsrvgrp.log. Each line of a server group log file begins with a <SGRP> prefix.

Related topics

Enabling-and-analyzing-logs

Analyzing-logs

Log-entry-format

Here is a sample server group log file:

<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Server Group Trace Log -- ON
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Server group initial configuration:  ServerGroupConfiguration[serverGroupMember=true serverGroupInterval=30 serverGroupName=null serverGroupFlashboardAdminPort=1099]
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ MemberNode [host=host1, port=port1, cachePeerListenerPort= cachePeerListenerPort1] joined server group
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ caches that participate RMI replication are = [eboCache, activeLinkCache, formCache, domainObjectCache, serverGroupCache, applicationCache, domainKeyCache]
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ computer1 is configured as IPV4 machine.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ RegisterPeer, hostPort = hostPort, peerHostPort = peerHostPort
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Checking if the remote cache peer is running at //hostPort/eboCache
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ The cache peer is running.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Checking if the remote cache peer is running at //hostPort /activeLinkCache
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ The cache peer is running.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Checking if the remote cache peer is running at //hostPort/formCache
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ The cache peer is running.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Checking if the remote cache peer is running at //hostPort/domainObjectCache
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ The cache peer is running.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> /* 2025-04-18T17:03:56.795+0000 */ Checking if the remote cache peer is running at //hostPort/serverGroupCache
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026>/* 2025-04-18T17:03:56.795+0000 */ The cache peer is running.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026>/* 2025-04-18T17:03:56.795+0000 */ cachedMemberNodeBoard is NULL - This means that the others server may have not replicated yet or it is down.
<SGRP> <TrID: jluKP-XvREC67KMqouHuvQ:0000026>/* 2025-04-18T17:03:56.795+0000 */ Returning as either allMembersFromDB is null/empty or otherMembersResources is null/empty or upgrade status is pending.

For more information about server groups, see Configuring-server-groups.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Innovation Suite 25.4