sapccmsr logfile monitoring - default trace

[Former Member]

Hi,

We want to monitor default trace files of all server nodes.

We created a templete for each server node with individual MTE.

In RZ20 - we are able to see only defaultraces of one server node 0.

When we check the SAPCCMSR log files...

Mon Apr 13 12:45:44 2009

ALLOGLIB: ERROR: Internal error in Logfile Monitoring: sAlBuildMonitorTree: could not create MO for /usr/sap/<SID>/JC00/j2ee/cluster/server1/log/defaultTrace.5.trc, rc = 253

ERROR-253 Can not attach same MTE [defaultTrace.5.trc] with different MTE class [Server1_defaultTrace]. Existing MTE class: [Server0_defaultTrace]

ALLOGLIB: ERROR: Internal error in Logfile Monitoring: sAlBuildMonitorTree: could not create MO for /usr/sap/<SID>/JC00/j2ee/cluster/server1/log/defaultTrace.4.trc, rc = 253

ERROR-253 Can not attach same MTE [defaultTrace.4.trc] with different MTE class [Server1_defaultTrace]. Existing MTE class: [Server0_defaultTrace]

ALLOGLIB: ERROR: Internal error in Logfile Monitoring: sAlBuildMonitorTree: could not create MO for /usr/sap/<SID>/JC00/j2ee/cluster/server1/log/defaultTrace.3.trc, rc = 253

ERROR-253 Can not attach same MTE [defaultTrace.3.trc] with different MTE class [Server1_defaultTrace]. Existing MTE class: [Server0_defaultTrace]

ALLOGLIB: ERROR: Internal error in Logfile Monitoring: sAlBuildMonitorTree: could not create MO for /usr/sap/<SID>/JC00/j2ee/cluster/server1/log/defaultTrace.2.trc, rc = 253

Please find the template files for both server nodes...

Template for server node 0

-

---

LOGFILE_TEMPLATE

DIRECTORY="/usr/sap/<SID>/JC00/j2ee/cluster/server0/log"

FILENAME="defaultTrace*"

IGNORE_FILE="defaultTrace*.trc.old"

MTE_CLASS="Server0_defaultTrace"

SHOWNEWLINES=1

REPORT_MATCHING_LINES_ONLY=1

PATTERN_0="ERROR"

VALUE_0="RED"

.

Template for server node 1

-

---

LOGFILE_TEMPLATE

DIRECTORY="/usr/sap/<SID>/JC00/j2ee/cluster/server1/log"

FILENAME="defaultTrace*"

IGNORE_FILE="defaultTrace*.trc.old"

MTE_CLASS="Server1_defaultTrace"

SHOWNEWLINES=1

REPORT_MATCHING_LINES_ONLY=1

PATTERN_0="ERROR"

VALUE_0="RED"

.

Thanks,

Tanuj

[Former Member]

Please check Note 800449 - SAP J2EE Engine 6.30/6.40: Logfile monitoring

The error was corrected with NetWeaver 04 SP Stack 13. Until NetWeaver 04 SP Stack

12, you need to correct the affected log file templates manually, by placing the value of

the DIRECTORY parameter in quote marks, such as:

DIRECTORY="F:\usr\sap\J2E\JC00\j2ee\cluster\dispatcher\."

Thank you,

Shyam

Edited by: shyam thamadapalli on Apr 14, 2009 2:38 AM

[Former Member]

Hi,

Thanks for the reply.

But we are running on Netweaver 7.0 SPS 15.

As you mentioned the Directory is already given in " ".

Thanks,

Tanuj

[jay_b2]

I recently encountered this error and managed to think over it. I am listing the resolution for others who come across this in future.

This occurs when you modify the MTE Class for a node in template file, while the node stands configured and visible in RZ20 (as you've already said) and thus, results in ambiguity.

To resolve this, you need to disallow the logviewer from reading the template file. If you modified your sapccmsr.ini file to include the location of template then, this can be done by removing the entries from the sapccmsr.ini OR you can copy it to some other location and delete the file from logmon.

The node should disappear from RZ20 with the next run. In the case of ABAP programs, the maximum frequency of run is five minutes. Now, you are ready to implement the new definition of the log file template. Bring it back to the location and it should process successfully.

Another way might be to change the MTE Class in RZ20 by using edit function. Theoretically, this should also work.

Regards,

Jayesh