Does anyone have some good steps for diagnosing SLDataGateway.exe taking all Virtual Memory and Crashing the DMA?
Please see some interesting log file entries from just before DMA crashing:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: SLDataGateway.exe (5944) consumed 46393978880 bytes, prunsrv.exe (1296) consumed 7146168320 bytes, and SLElement.exe (6652) consumed 1616957440 bytes.
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: SLDataGateway.exe (5792) consumed 40352841728 bytes, prunsrv.exe (1224) consumed 7361466368 bytes, and SLNet.exe (2652) consumed 2814517248 bytes.
Thank you for looking.
Hi Alasdair, here are some checks you can perform to narrow down an SLDataGateway memory issue:
- Check VM Size trending of SLDataGateway in a Microsoft Platform element that monitors your agent. Does SLDataGateway memory usage change over time? Are there sudden spikes or leak patterns? Are they reoccurring on a month-to-date timespan?
- Compare SLDataGateway VM Size trending with Commit Charge Total or Free Virtual Memory trending on the same agent. There may be other processes consuming the memory, and SLDataGateway may be not the culprit.
- Note the starting points of leaks. Check the SLWatchdog2.txt log around the start time of the issue. Pay attention to lines like "Process * stopped" or "Not signaled 1 (since *)".
- If possible, check if any configuration changes were made in DataMiner around the time the issue occurred for the first time.
- If available, check the SLDataGateway.txt and SLDBConnection.txt logs around the time the issue started, pay attention to lines like
"Queue for * exceeded *000 items".
These checks may help you collect some initial facts required for the investigation.