Skip to main content
Hosemacht
Hosemacht
Explorer
August 31, 2021
Solved

FortiOS 6.4.7 is out!

  • August 31, 2021
  • 1 reply
  • 9502 views

lot of Bug Fixes but WAD Memory Leak (712584) still persists witch keeps me from updating.

What do you think?

    Best answer by Kangming

    Hi Hosemacht, 

     

    Yes, this bug(WAD Memory Leak ID:712584) has not been fixed yet. At present, our R&D team is working hard to locate it. The possible cause is caused by some specific HTTP traffic or FTP traffic or other special traffic, so this is not an issue that every FGT customer who uses the AV feature will encounter. 

     

    If you really encountered this issue, now there is a temporary solution. We can use the script function to restart the wad process regularly, such as restarting the wad process at 1:00 am every night. Usually, memory leaks will take some days or weeks to appear, Therefore, before the bug is not resolved, we can find a suitable cycle without affecting the business to restart the wad process, which can effectively prevent the FGT from entering the Memory conserve mode. 

     

    The script to restart WAD can refer to this kb document：

    https://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD46670&sliceId=1&docTypeID=DT_KCARTICLE_1_1&dialogID=246578521&stateId=1%200%20246576567%27)

     

     

    Thanks

    Kangming

    1 reply

    mike_dp
    mike_dp
    New Member
    August 31, 2021

    We are at 6.4.5 and everything runs smoothly. We will prob wait for the WAD issue to be fixed before upgrading further since we don't have that issue so far. We still have lots of employees working from home so the WAD isn't much used like it used to.

    Kangming
    Staff
    KangmingAnswer
    Staff
    September 3, 2021

    Hi Hosemacht, 

     

    Yes, this bug(WAD Memory Leak ID:712584) has not been fixed yet. At present, our R&D team is working hard to locate it. The possible cause is caused by some specific HTTP traffic or FTP traffic or other special traffic, so this is not an issue that every FGT customer who uses the AV feature will encounter. 

     

    If you really encountered this issue, now there is a temporary solution. We can use the script function to restart the wad process regularly, such as restarting the wad process at 1:00 am every night. Usually, memory leaks will take some days or weeks to appear, Therefore, before the bug is not resolved, we can find a suitable cycle without affecting the business to restart the wad process, which can effectively prevent the FGT from entering the Memory conserve mode. 

     

    The script to restart WAD can refer to this kb document：

    https://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD46670&sliceId=1&docTypeID=DT_KCARTICLE_1_1&dialogID=246578521&stateId=1%200%20246576567%27)

     

     

    Thanks

    Kangming

      boneyard
      boneyard
      Valued Contributor
      September 4, 2021

      i was pretty happy with 6.4.6 but there are several fixes in 6.4.7 which make me wonder if .7 isn't the better one. random ssl cert pop up in flow and hairpin NAT issue in proxy. it remains annoying such basic functionality just breaks.

      Terms & ConditionsAccessibility statement