Home › Forums › SecAst (Security for Asterisk) › Installation & Upgrade › High CPU usage

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • teliumcustomer1
    Member
    July 30, 2019 at 4:32 am
    Post count: 6
    #6591

    I installed everything tonight and everything appears to be working fully, but the secast process is using 100% CPU usage. Any idea what would be causing this?

    Avatar photoTelium Support Group
    Member
    July 31, 2019 at 6:14 pm
    Post count: 258
    #6849

    To start, lets make sure nothing significant is missing/misconfigured. To diagnose:

    1. Stop the SecAst service
    2. Delete the SecAst event log (file)
    3. Start SecAst from the command line with the -f parameter (foreground)
    4. Post the screen output and log file (first 200 lines)
    5. Post the output of “ldd secast” (from the /usr/local/secast directory)

    100% CPU is very unusual for SecAst so I suspect something major is missing/misconfigured. If the above looks ok I suggest you post your secast config file (if you are concerned about posting email it to support@autocommander.aws2.ocg.ca)

    teliumcustomer1
    Member
    July 31, 2019 at 10:19 pm
    Post count: 6
    #6850

    Starting SecAst with -f reports an error relating to AstLog file (signal):

    Quote:
    /usr/local/secast/secast -f
    SecAst version 1.5.16 started under PID 15640
    QObject::connect: No such signal AstLogMonitor::sig_logrecord(Eventlog::ELevels, Types::ESources, quint16, QString, TelnetConnection *) in astlogmonitor.cpp:46

    Avatar photoTelium Support Group
    Member
    August 1, 2019 at 12:35 am
    Post count: 258
    #6851

    The error regarding Ast log file is a clue. Associated with that, I notice that in you secast.conf’s [asterisk] stanza you have set the securityevents key to an Asterisk log file.

    This (securityevents) key is only for compatibility with really old (1.4 and older) versions of Asterisk. This setting also disables SecAst’s ability to get more advanced data from Asterisk. If you are running a more recent Asterisk version please set this key to blank (empty). We actually plan to remove this key in a future release of SecAst.

    Once you have made that change let me know how SecAst is working. As well, I suggest you upgrade to SecAst 1.6.x as we have added additional features.

    teliumcustomer1
    Member
    August 1, 2019 at 1:20 am
    Post count: 6
    #6852

    That fixed the CPU usage!

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.