I keep seeing this message in the runtime message logs (going to the container out in JSON format) that indicates to look elsewhere in the trace files:

message: FBTSTM068W The server encountered an exception while processing a request in validate mode. If the environment has trace enabled, the exception will appear in the trace log.
module: com.tivoli.am.fim.trustserver.sts.STSModuleChain

However, under /var/application.logs.local/rtprofile/ there are no trace files, just messages.log (and rolled messages) and the ffdc directory.

Where do the runtime trace logs go now (on lightweight containers, v10.0.5.0)?  On a side note, we don't have a shared / persistent volume for logs.  We ship all logs to container out.  The traces I can understand if they are going to a log and not container log, but I am not seeing any trace file.  The trace spec is configured to com.tivoli.am.fim.trustserver.sts.utilities.IDMappingExtUtils=INFO so I would expect we would be seeing a trace log somewhere.

Before the lightweight containers, the trace.log and rotated files were located in the rtprofile directory.  I haven't had to troubleshoot anything for a while, but I have a development team that is having issues with refresh tokens returning a 500 error from the authorization server and I suspect the above message could be related.  I did a find / -name trace.log and I do not see them anywhere.

I feel like I am missing something simple but it has been a long week, and I'm hoping that's the case!  Any help finding the trace output from the verify-access-runtime would be appreciated!

Thanks!

Matt

------------------------------
Matt Jenkins
------------------------------

Very strange, under my lab I do see trace files under /var/application.logs.local/rtprofile/ when I have com.tivoli.am.fim.trustserver.sts.utilities.IDMappingExtUtils=FINER.  So I am guessing nothing is being logged to the trace log in the other environment I am working with the development team on.  However, I don't understand why FBTSTM068W refers me there, unless I need to adjust the trace spec to catch whatever is being pushed to the trace log when this event occurs.

I keep seeing this message in the runtime message logs (going to the container out in JSON format) that indicates to look elsewhere in the trace files:

message: FBTSTM068W The server encountered an exception while processing a request in validate mode. If the environment has trace enabled, the exception will appear in the trace log.
module: com.tivoli.am.fim.trustserver.sts.STSModuleChain

However, under /var/application.logs.local/rtprofile/ there are no trace files, just messages.log (and rolled messages) and the ffdc directory.

Where do the runtime trace logs go now (on lightweight containers, v10.0.5.0)?  On a side note, we don't have a shared / persistent volume for logs.  We ship all logs to container out.  The traces I can understand if they are going to a log and not container log, but I am not seeing any trace file.  The trace spec is configured to com.tivoli.am.fim.trustserver.sts.utilities.IDMappingExtUtils=INFO so I would expect we would be seeing a trace log somewhere.

Before the lightweight containers, the trace.log and rotated files were located in the rtprofile directory.  I haven't had to troubleshoot anything for a while, but I have a development team that is having issues with refresh tokens returning a 500 error from the authorization server and I suspect the above message could be related.  I did a find / -name trace.log and I do not see them anywhere.

I feel like I am missing something simple but it has been a long week, and I'm hoping that's the case!  Any help finding the trace output from the verify-access-runtime would be appreciated!

Thanks!

Matt

------------------------------
Matt Jenkins
------------------------------