Skip to main content
Frosty
Frosty
New Member
December 21, 2014
Solved

Transparent web proxy crashing? (diag wacs restart)

  • December 21, 2014
  • 1 reply
  • 5462 views

Since enabling the transparent web proxy in our FG200B a few days ago, I noticed this morning that nothing was showing up in the cache monitor.  Suspecting that it had 'crashed' over the weekend, I went into the CLI and ran:

[ul]
  • config global
  • diag wacs restart[/ul]

    and sure enough, straight away there was stuff showing up again in the cache monitor screen.  Several questions occur to me:

    [ol]
  • is the transparent web proxy cache functionality robust, or is it known to be a bit flaky?
  • is there any way I can be sure about my suspicion that the service is crashing?[/ol]

    I didn't think to run 'diag sys top' before restarting the wa_cs service, but I will do that if I notice problems with it again.

      • Best answer by Jeroen

      Normaly you will see something like this in your system events:

       

      date=2014-12-31 time=13:24:02 logid=0100032546 type=event subtype=system level=warning vd="root" logdesc="Application crash" action=crash msg="Pid: 28447, application: wad, Firmware: FortiGate-1500D v5.2.1,build0618b618,140915 (GA) (Release), Signal 11 received, Backtrace: [0x011ad238] [0x0120cab8] [0x0120cfc0] [0x012136fb] [0x0126ee7a] [0x0126f0a6] [0x0126e5ed] [0x012a1a78] [0x0043d35c] [0x0043a3e3] [0x2a95c40475] [0x0043a889]"

      1 reply

      Jeroen
      JeroenAnswer
      New Member
      January 5, 2015

      Normaly you will see something like this in your system events:

       

      date=2014-12-31 time=13:24:02 logid=0100032546 type=event subtype=system level=warning vd="root" logdesc="Application crash" action=crash msg="Pid: 28447, application: wad, Firmware: FortiGate-1500D v5.2.1,build0618b618,140915 (GA) (Release), Signal 11 received, Backtrace: [0x011ad238] [0x0120cab8] [0x0120cfc0] [0x012136fb] [0x0126ee7a] [0x0126f0a6] [0x0126e5ed] [0x012a1a78] [0x0043d35c] [0x0043a3e3] [0x2a95c40475] [0x0043a889]"

      Terms & ConditionsAccessibility statement