Skip to main content
JuYopmail
New Member
January 30, 2019
Question

"FortiClient Logging daemon - FCDBLog.exe" high CPU and RAM

  • January 30, 2019
  • 2 replies
  • 52690 views

FortiClient and its "FortiClient Logging daemon - FCDBLog.exe" process is permanently at high CPU (minimum 12% or 13% CPU, but up to 25%) and it uses up to 6 GB of RAM !!!!

 

Even if I shutdown forticlient, this process stays pending there, and consuming this CPU and RAM !!!

I tried to lower the log level to minimal (Alert or Emergency), but this does not change anything !!!

 

I just need a VPN client, I do not need a thread vulnerability scan or a logger or anything !!!

What can I do to get rid of this process (except from "uninstalling" this product, which is imposed to me by a customer) ??

 

Thank you,

  Ju.

PS : This is maybe occuring because I have a new PC ?

    2 replies

    Toshi_Esumi
    SuperUser
    SuperUser
    January 30, 2019

    I don't know what the process does but to disable local logging, you can go to Settings and uncheck all features for logging like VPN, Update, Vulnerability Scan, Telemetry if they're enabled.

    But I think it's rather because of the FC version than PC version.

    ck_FTNT
    Staff
    Staff
    January 30, 2019

    Hi Ju,

    You did not specify which version you are on, however there is a known issue which was resolved in FortiClient 6.0.4.

     

    Please see the 6.0.4 release notes Resolved Issues section (https://docs.fortinet.com/d/forticlient-6.0.4-windows-release-notes) page 14:

    "522496 FCDBLog.exe keeps crashing."

     

    Regards

    JuYopmail
    JuYopmailAuthor
    New Member
    January 31, 2019

    Hi,

     

    Thanks for that answer !

     

    I am on the only version I found online on https://forticlient.com/downloads

    Version 6.0.0 for Windows.

     

    => Where could I found the 6.0.4 version ???

     

    Regards,

     Ju

    SAM-DXB
    New Member
    September 25, 2023

    in the  Task Manager you can select the process and choose Efficiency mode as it seems working with me