How to collect the detailed App log in the PCF
Article ID: KB0079177
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Oracle Tuxedo | - |
Description
When collecting the debug log in the PCF container runtime, for instance, the Tuxedo client traces for troubleshooting a Tuxedo BW Plugin application JVM crash issue, it can not write to the default console log.
Issue/Introduction
How to collect the detailed App log in the PCF
Environment
Linux Environment
Resolution
Please create a symbolic link to /dev/stdout the process standard output with the PCF log file to gather the details,
for example, the console log file is written to /usr/tmp/app.out; go to the directory and remove the file app.out, and create a symbolic link to /dev/stdout like below,
ln -s /dev/stdout app.out
When listing the files in the folder, it shows the file app.out linked to /dev/stdout, i.e app.out -> /dev/stdout
Note: The symbolic link must be done after the container is available and before tests are started. If the container is later destroyed then the same steps need to be followed again.
for example, the console log file is written to /usr/tmp/app.out; go to the directory and remove the file app.out, and create a symbolic link to /dev/stdout like below,
ln -s /dev/stdout app.out
When listing the files in the folder, it shows the file app.out linked to /dev/stdout, i.e app.out -> /dev/stdout
Note: The symbolic link must be done after the container is available and before tests are started. If the container is later destroyed then the same steps need to be followed again.
Feedback
Yes
No
Powered by
