[Progress Communities] [Progress OpenEdge ABL] Forum Post: PASOE agent log has scary messages (stget: out of storage)

[dbeavon]

Today there was a higher volume of activity in PASOE than normal and we started seeing some really strange errors in the agent log . Here is an example.. [19/01/29@16:58:01.613-0500] P-007020 T-008596 1 AS-404 -- (Procedure: 'EntryProcedures\Server\StartupStateReset.p' Line:0) ** stget: out of storage. (6498) [19/01/29@16:58:01.614-0500] P-007020 T-008596 1 AS-404 MSAS Destroying Session AS-404 (crash). [19/01/29@16:58:01.727-0500] P-007020 T-008596 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 6, Status: 10002 [19/01/29@16:58:01.729-0500] P-007020 T-005988 1 AS-ResourceMgr MSAS Spawning New Worker Thread. Number: 8 [19/01/29@16:58:06.639-0500] P-008356 T-009680 1 AS-Aux-0 MSAS Agent Starting Up -- Progress OpenEdge Release 11.7 build 1685. [19/01/29@16:58:06.640-0500] P-008356 T-009680 1 AS-Aux-0 -- Logging level set to = 1 [19/01/29@16:58:06.652-0500] P-008356 T-009680 1 AS-Listener MSAS Spawning New Worker Thread. Number: 4 [19/01/29@16:58:07.058-0500] P-008356 T-005232 1 AS-ResourceMgr MSAS Spawning New Worker Thread. Number: 5 Notice the message, "stget: out of storage" and the crash. Based on my reading, this appears to indicate that the PASOE agent, or perhaps the server as a whole, had run out of memory. There is other evidence that there were memory problems. The same MS-agent was generating these messages too at the same time (and we NEVER see errors about SAX parsing): SAX parser error: SAX-PARSE-FIRST, Unexpected exception. (14586) And other processes on the machine were also unhappy. Another small, unrelated process logged this to the windows event log around the same moment of time: System.ComponentModel.Win32Exception (0x80004005): The paging file is too small for this operation to complete at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) But moments later, when I logged into the desktop to investigate, there were no problems at all and the server seemed totally peaceful. I'm guessing that PASOE had some type of spasm and tried to momentarily consume all available memory on the entire system. Is there any other logging I should be looking at other than the MS-agent log and the Windows event log? Is there a way for me to gather better information if/when this reoccurs? We are running OE 11.7.4 on Windows Server.

Continue reading...