Skip to main content
knut
knut
New Member
October 5, 2011
Question

what is cmdbsvr?

  • October 5, 2011
  • 10 replies
  • 28986 views
After upgrading a 200B to 4.0 MR3 patch 2 I can see a strange increase in cpu and memory usage in cmdbsvr: Run Time: 2 days, 21 hours and 29 minutes 16U, 17S, 67I; 1009T, 398F, 194KF cmdbsvr 29 S 20.8 17.3 proxyworker 54 S 4.8 5.7 ipsengine 60 S < 3.6 16.2 scanunitd 26922 S < 0.6 1.6 In a 310B with 4.0 MR2 patch 8 it is way down the list in top: Run Time: 45 days, 11 hours and 6 minutes 11U, 15S, 72I; 1008T, 348F, 213KF ipsengine 95 R < 8.5 19.5 proxyworker 50 R 4.9 6.4 scanunitd 9570 S < 1.5 1.5 urlfilter 60 S 1.3 4.3 scanunitd 9569 S < 0.7 1.5 miglogd 39 S 0.1 1.4 ssl 57 S 0.1 0.3 ipsengine 94 S < 0.0 11.8 httpsd 12391 S 0.0 2.1 httpsd 12393 S 0.0 2.0 cmdbsvr 26 S 0.0 1.8

    10 replies

    abelio
    SuperUser
    abelio
    SuperUser
    October 5, 2011
    Hi, cmdbsrv is an important daemon, process and parse conf file; don' t try to kill it re-check all your config in order to avoid firewall objects with spaces in its names, or non-standard characters. regards
    knut
    knutAuthor
    New Member
    October 6, 2011
    I have checked through everything now, and it looks like i have no spaces, no non english letters and only _, - and . in the config with english letters and numbers. The longest name is 23 letters.
    abelio
    SuperUser
    abelio
    SuperUser
    October 6, 2011
    Hi what about your CPU usage graphs? do you see something abnormal there?
    knut
    knutAuthor
    New Member
    October 7, 2011
    Yes, it spikes every few seconds, and that is usually cmdbsvr. As you can se on the top i attached it is quite often over 20%. Sometimes it is at 99,9% as well.
    Secure_IT_BE_Nick
    Secure_IT_BE_Nick
    New Member
    October 12, 2011
    I have the exact same problem, after upgrading to MR3 on a 100A. Have a ticket open with support, but FN is again very slow with answering...
    knut
    knutAuthor
    New Member
    October 13, 2011
    My issue is maybe related to my 3 FortiAP. I tried to disable them for some time, and the cmdbsvr did not use any CPU when the FortiAP did not run. When I activated the FortiAP again the cmdbsvr started to consume quite a lot of CPU again.
    Secure_IT_BE_Nick
    Secure_IT_BE_Nick
    New Member
    October 13, 2011
    Knut Same thing here, with only 1 AP. Still NO answer from Fortinet. As a partner and FCNSP i' m really dissapointed...
    knut
    knutAuthor
    New Member
    October 14, 2011
    I also got a ticket open, but they want me to change settings I do not believe will help me with the cmdbsvr problems: http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD33078&sliceId=1&docTypeID=DT_KCARTICLE_1_1&dialogID=22030476&stateId=0%200%2022032413 I have no CPU problems with my load, but I do not understand why cmdbsvr should use that much cpu and memory when I use fortiAP. The fortiAP is way more unstable after the upgrade to 4.3.2 from the special branch 4.2.7 made for fortiAP I used before.
    Secure_IT_BE_Nick
    Secure_IT_BE_Nick
    New Member
    October 17, 2011
    with my load, but I do not understand why cmdbsvr should use that much cpu and memory when I use fortiAP. The fortiAP is way more unstable after the upgrade to 4.3.2 from the special branch 4.2.7 made for fortiAP I used before.
    Been there, done that didn' t help... FortiAP is complete gone out of the network. And again still no Answer, ticket created on 2 oktober...
    Secure_IT_BE_Nick
    Secure_IT_BE_Nick
    New Member
    October 21, 2011
    Again still no answer last from 13/10 what is happening with the support these days?
    knut
    knutAuthor
    New Member
    November 7, 2011
    Support is slow... I got this from support today: This issue looks similar to the bug ' 0155391' which reports " Memory leak observed by cmdbsvr process and Wireless Controller during associations "
    knut
    knutAuthor
    New Member
    November 11, 2011
    Did not help with 4.3.3
    knut
    knutAuthor
    New Member
    December 8, 2011
    I just got a firmware update from fortinet. According to Fortinet the problem was: Engineering could isolate this bug and fix it. It was related to an issue with API when trying to save certificate during wireless renegotiation.
    knut
    knutAuthor
    New Member
    December 12, 2011
    I have been running the update I got from Fortinet support for around 4 days now. The CPU usage and memory usage are way better than before, so it might seem like they have fixed the bug.
    Terms & ConditionsAccessibility statement