This article describes the issue when the customer is unable to see the forward traffic logs either in memory or disk or another remote logging device.
- The customer was getting an error at 2% (loading too slow) in GUI while checking for the forward traffic logs in GUI.
- Changed the status to memory but still no logs same error.
- Disabled the disk logging but still no change.
Logs are taken during the time of issue.
# exec log filter category 0
file_no=60716, start line=0, end_line=16237
After seeing the error in the index file, it was tried to kill the httpsd and miglogd but still, the same issue was faced. If the issue kindly is still persisting, refer to the below steps.
When searching logs stored in disk or memory, the log search daemon (log_se)'s child process (chile process) creates a temporary index file on the local hard disk. If this process fails, the log search will be stopped.
NOTE: After disabling the hard disk logging and using the memory alone will also have such a problem.
This is because when doing any kind of log search, it does not matter if it is from a disk log or memory log, the log search child process will make a temporary index file on disk and if that step fails, the log search will fail too. That is exactly what is shown in the debug log.