FortiSOAR Knowledge Base
FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
bbae
Staff
Staff
Article Id 418492
Description This article describes the issue of being unable to update the solution pack. It provides a step-by-step guide to troubleshoot and resolve the issue.
Scope Connector, Solution pack, FortiSOAR.
Solution

To address the issue of being unable to update the SOAR Framework solution pack, follow these steps:

  1. Check the user's permissions to update the solution pack. Refer to the FortiSOAR documentation for more information on permissions required for using solution packs.
  2. Make sure that FortiSOAR can continuously connect to the Fortinet FortiSOAR repository or to the offline repository, if using the offline repo, to ensure the installation of widgets that depend on the Solution Pack.
    This issue might be related to a connection issue with the offline repository, due to content being out of sync.

  3. If this kind of error is displayed as shown below during update or installation, it is necessary to install the required widget, in this case, the indicatorExtraction widget, manually first.

    Since installing the widget on the FortiSOAR failed, it is possible to export it from the other FortiSOAR node and import it into the FortiSOAR, or download it directly from GitHub

    IndicatorExtraction.png  

    IndicatorExtraction2.png

     

  4. If the issue persists after successfully installing a widget and a similar error is displayed as shown below, try manually installing the Solution pack using an unmodified, intact file available for download from GitHub.

    Platform Utilities.png

     

  5. Try debugging as follows if the steps above don't work out, and open the TAC ticket with Fortinet with the debug log.

    1. Run tail -50f  /var/log/cyops/cyops-api/prod.log

    2. Try installation and collect tail logs.

Contributors