|
When memory usage is very high and increases very fast in a short period, it might be a memory leak issue, and it can be analyzed by the following steps.
Note that memory increase does not always mean a memory leak. A memory leak issue usually has these phenomena:
-
Very fast and abnormal memory increase (usually with common or low traffic levels).
-
Continuous memory increases without deallocated.
-
Used memory is not deallocated even after traffic drops or stopped.
The most important thing for troubleshooting a memory leak issue is to locate which module, process, or function causes the memory increase.
- Collect below log output to identify the root cause.
get sys status
diag hardware sysinfo memory
diag hardware sysinfo cpu
diagnose hardware deviceinfo disk
get hardware status
get sys perf stat <--- run this 2-3 times
diag autoupdate ver
diag sys top-sum <---Press 'C' and let run for about 15 seconds then press 'q' to stop.
diag sys top 1 20 <--- Press 'C' let run for about 15 seconds then press 'q' to stop.
diag sys top-mem
get system status
get system performance status (Run this command 5 times in intervals of 1 minute).
diag sys top 1 40 (Run for 30 Sec and CTRL C to stop).
diag sys top-s '-s mem' (Run for 30 Sec and CTRL C to stop).
diagnose autoupdate versions
diag debug crashlog read | grep 2024
- Run 'diag sys top 1 20' to check the top utilized resources and based on the top utilizing resources, collect further logs for them.
- 'diag hardware sysinfo memory' will give an idea of the allocated memory of current usage firewall resources.
Example:
diag har sysinfo memory
MemTotal: 1963860 kB
Cached: 448948 kB ---> Cached mem is 440 MB.
Active: 932748 kB ---> Active mem is above 900 MB. Almost half of the memory.
- Check the 'diag sys top-mem', calculate the memory utilization of the top utilized resource, and verify the crash logs.
The well-known processes for memory leaks are WAD, IPS, fgtlogd, and others. In case of memory leak issues, always refer to the release notes of the known issues of the firmware.
Refer to the below article to collect logs in case of WAD, IPS, and other processes consuming the memory. Based on the logs it can be identified If there is a leak or any network condition is triggering high memory usage.
WAD
|
