Show TAC Missing or No Information
Problem
This section describes how to resolve the failure of logs or Cores with the Show TAC feature.
When the Show TAC feature is executed, the logs or cores fail to show up in the Apache server.
Resolution
-
Verify the status of the Show TAC process.
tac-debug-pkg status
-
Verify the parameters and syntax.
-
The TAC package creation time must be in yyyy-mm-dd_hh:mm:ss format.
-
The parameters specified for filtering must match the microservices labeling.
-
-
In the target node, run the following command to verify if the targeted JournalD entries or Core files are within the specified time range.
journalctl
NoteThe first line of the output specifies the starting time of the current logs repository. Also, JournalID starts aging out old entries (log rotation) when the log size reaches the specified limit.Similarly, for the Core files, run the following command to display the available Core files and its corresponding time stamp.
ls -al /var/lib/systemd/coredump
-
Verify if the JournalID is rate-limiting the entries in the target node. Filter for statements like the one shown in the following example:
journalctl | grep Suppressed Suppressed <number> messages from /system.slice/...
NoteJournalD is configured to allow 10000 messages per 10 seconds period.