ProxySG & Advanced Secure Gateway

Hi  Team,

Our both poxy got rebooted unexpectedly. One is last week and other is on this week.

I only can see software got rebooted. Please check below logs for more info and help me to find out the reason. 

ProxyA:-

Minicontext produced on: 2019-04-18 08:36:44+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.7.3.10.222765
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0xe
Software exception code: 0x0
Page fault linear address: 0x1d
Process group: "PG_TCPIP"
Process: "HTTP CW 2071A91EA40" in "libstack.exe.so" at .text+0x566abb

ProxyB:-

Minicontext produced on: 2019-04-10 22:38:47+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.7.3.10.222765
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x5a0000
Page fault linear address: 0x0
Process group: "PG_UNKNOWN"
Process: "Threshold_Monitor" in "" at .text+0x0

Thanks,

Mayur

Dear Mayuram,

Appliance ran out of memory please upgrade to 6.7.4.4

Hardware exception code: 0x0
Software exception code: 0x5a0000

BR

Aboonaim

----------

If you are satisfied with an answer, please click "Accept Solution"

Hi Aboonaim,

Thanks for the details, really helpful.

ProxyB:-

Yes, I also can see memory critical logs in event logs just before 10 mins of proxy reboot.

2019-04-11 06:27:21+08:00AWST  "Health Monitor (CRITICAL): Memory Utilization above 79 percent for last 120 seconds"  4F 6F0102:1 Mailed notifier.cpp:111

Is symentec assigned any known bug id for this?

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.

ProxyA:-

Any leads for other proxyA reboot issue?

I seen below bug info in version 6.3.x release notes for Process group: "PG_TCPIP"

https://cryptohub.nl/mirror/proxysg/SGOS_RelNotes_6.3.3.1.pdf

The ProxySG no longer restarts with an error in a PG_TCPIP process in libstack.exe.so. This issue occurred in an ADN deployment. (B#174660, SR 2-453622261)

Then how come its affecting later version as we are currently running inn 6.7.x Also we are not doing any ADN deplyment here, I didnot found any document where this bug explained, Can you cross check?

Also please suggest recomnded vesion for this as well. 

Thanks,

Mayur

Yes, Below are the Process and Bug ID which have been fixed in 6.7.4.4.

process for proxy 1  Process group: "PG_TCPIP" :- Bug id #256018

process for proxy 2  Process: "Threshold_Monitor":-Bug id #248792

Thank by the way for your suggestions.