ProxySG & Advanced Secure Gateway

 View Only
  • 1.  Proxy rebooted unexpectedly

    Posted Apr 24, 2018 05:16 AM

    Hi Team,

     

    Our proxy rebooted unxpectedly twice on 19th and 20th April.  Proxy has produced minicontect file with below details. Did not find anything more from proxy logs. May i conform it is related to known bug ?

    Running Version: SGOS 6.6.5.9, Release id: 201969
    Produced on Friday April 20 2018 14:32:40
    Size on disk is 272724992 bytes.

    Minicontext produced on: 2018-04-20 14:32:40+00:00UTC
    Minicontext version: 1.5
    ProxySG Appliance: Version 6.6.5.9.201969
    Architecture: x86_64
    Kernel: Multiprocessor
    System image flags: Customer, Optimized, Non-GDB, 64-bit

    Hardware exception code: 0x0
    Software exception code: 0x11
    Page fault linear address: 0x0
    Process group: ""
    Process: "" in "kernel.exe" at .text+0x1249cca
    Register context:
          RIP              RSP              RBP              RDI
    0000000001249CCA 0000000000000011 0000000001D08DA0 0000000000000011 
          RSI              RDX              RCX              RBX
    000000000000041D 0000000000000000 0000000000000007 0000000001ACEA00 
          RAX              R8               R9               R10
    0000000001ACE980 0000000000000008 0000000000000007 0000000000000000 
          R11              R12              R13              R14
    0000000001C7B4E0 0000000000000011 00000000013A07C7 0000000001AD6760 
          R15             RFLAGS       CS   SS
    000059FB455928B9 0000000001ACEA00 1D08DA0 FFFFFFFF 
    Call Stack:
    System data:
    0000  23 20 57 61 74 63 68 64 6F 67 20 68 61 73 20 6E   # Watchdog has n
    0010  6F 74 20 62 65 65 6E 20 72 65 73 65 74 20 6F 6E   ot been reset on
    0020  20 70 72 6F 63 65 73 73 6F 72 20 30 2E 0A 23 20    processor 0..# 
    0030  41 63 74 75 61 6C 20 4C 65 6E 67 74 68 20 6F 66   Actual Length of
    0040  20 77 64 20 69 6E 74 65 72 76 61 6C 20 33 30 20    wd interval 30 
    0050  73 65 63 6F 6E 64 73 2E 0A 23 20 45 78 70 65 63   seconds..# Expec
    0060  74 65 64 20 4C 65 6E 67 74 68 20 6F 66 20 77 64   ted Length of wd
    0070  20 69 6E 74 65 72 76 61 6C 20 33 30 20 73 65 63    interval 30 sec
    0080  6F 6E 64 73 0A 23 20 50 72 6F 63 65 73 73 6F 72   onds.# Processor
    0090  20 30 20 73 61 77 20 33 30 30 30 20 74 69 63 6B    0 saw 3000 tick
    00A0  73 20 64 75 72 69 6E 67 20 77 64 20 69 6E 74 65   s during wd inte
    00B0  72 76 61 6C 20 65 78 70 65 63 74 65 64 20 33 30   rval expected 30
    00C0  30 30 2E 0A                                       00..
    Core Header:

    Running Version: SGOS 6.6.5.9, Release id: 201969
    Produced on Thursday April 19 2018 11:02:00
    Size on disk is 272205312 bytes.

    Minicontext produced on: 2018-04-19 11:02:00+00:00UTC
    Minicontext version: 1.5
    ProxySG Appliance: Version 6.6.5.9.201969
    Architecture: x86_64
    Kernel: Multiprocessor
    System image flags: Customer, Optimized, Non-GDB, 64-bit

    Hardware exception code: 0x0
    Software exception code: 0x11
    Page fault linear address: 0x0
    Process group: ""
    Process: "" in "kernel.exe" at .text+0x1249cca
    Register context:
          RIP              RSP              RBP              RDI
    0000000001249CCA 0000000000000011 0000000001D08DA0 0000000000000011 
          RSI              RDX              RCX              RBX
    000000000000041D 0000000000000000 0000000000000007 0000000001ACEA00 
          RAX              R8               R9               R10
    0000000001ACE980 0000000000000008 0000000000000007 0000000000000000 
          R11              R12              R13              R14
    0000000001C7B4E0 0000000000000011 00000000013A07C7 0000000001AD6760 
          R15             RFLAGS       CS   SS
    004468FEF7B56597 0000000001ACEA00 1D08DA0 FFFFFFFF 
    Call Stack:
    System data:
    0000  23 20 57 61 74 63 68 64 6F 67 20 68 61 73 20 6E   # Watchdog has n
    0010  6F 74 20 62 65 65 6E 20 72 65 73 65 74 20 6F 6E   ot been reset on
    0020  20 70 72 6F 63 65 73 73 6F 72 20 30 2E 0A 23 20    processor 0..# 
    0030  41 63 74 75 61 6C 20 4C 65 6E 67 74 68 20 6F 66   Actual Length of
    0040  20 77 64 20 69 6E 74 65 72 76 61 6C 20 33 30 20    wd interval 30 
    0050  73 65 63 6F 6E 64 73 2E 0A 23 20 45 78 70 65 63   seconds..# Expec
    0060  74 65 64 20 4C 65 6E 67 74 68 20 6F 66 20 77 64   ted Length of wd
    0070  20 69 6E 74 65 72 76 61 6C 20 33 30 20 73 65 63    interval 30 sec
    0080  6F 6E 64 73 0A 23 20 50 72 6F 63 65 73 73 6F 72   onds.# Processor
    0090  20 30 20 73 61 77 20 33 30 30 30 20 74 69 63 6B    0 saw 3000 tick
    00A0  73 20 64 75 72 69 6E 67 20 77 64 20 69 6E 74 65   s during wd inte
    00B0  72 76 61 6C 20 65 78 70 65 63 74 65 64 20 33 30   rval expected 30
    00C0  30 30 2E 0A                                       00..

     

    Regards,

    Anoop



  • 2.  RE: Proxy rebooted unexpectedly

    Posted Apr 24, 2018 08:48 AM

    Hi Anoop,

     

                   Is this for a VM or Physical appliance. Restart is caused by watchdog as the message says.



  • 3.  RE: Proxy rebooted unexpectedly

    Posted Apr 24, 2018 10:07 AM

    Hi Aravind,

    This is HW platform S200-20. 

    Regards,

    Anoop



  • 4.  RE: Proxy rebooted unexpectedly

    Posted Apr 24, 2018 10:10 AM

    Hi Aravind,

    Noticed Bug#240320(The proxy experiences a watchdog restart in the SNMP subsystem in environments with more frequent connection timeouts) being fixed in 6.6.5.10 patch. Is this applicable to our issue ?

    Regards,

    Anoop



  • 5.  RE: Proxy rebooted unexpectedly
    Best Answer

    Posted Apr 24, 2018 10:51 PM

    Hi Anoop,

     

                  Not easy to confirm by looking at the mini-context alone. Since full core is available, it will be better to get it escalated along with that. I was having a doubt but that only applies to VMs even though the crash messages were exactly same. It was related to some mismatch in watch dog reset (Bug#251550) . If this is the issue, then the fix is not yet ready. I will recommend for escalation to get this checked.



  • 6.  RE: Proxy rebooted unexpectedly

    Posted Apr 26, 2018 09:32 PM

    Hi Aravind,

     

    Thaks for your advise. Logged one Symantec case.

    Regards,

    Anoop