Fortinet black logo

Known Issues and Workarounds

7.2.0
Copy Link
Copy Doc ID 15957536-c12e-11ec-9fd1-fa163e15d75b:693289
Download PDF

Known Issues and Workarounds

  • Issue #0677225: If you manually restart a running instance of the FortiSOAR MEA using the docker restart <fortisoar-container-id> from the FortiManager root shell, or if the FortiSOAR MEA OS gets rebooted due to restarting of the docker container itself with either an OS reboot command or due to any application, then some of the filesystems within the docker container go into the read-only mode. This causes the "tomcat" service to not restart.
    Resolution:
    Restart the FortiSOAR MEA by the following commands on the FortiManager CLI:
    # config system docker
    # set fortisoar disable
    # end
    
    # config system docker
    # set fortisoar enable
    # end
    

Known Issues and Workarounds

  • Issue #0677225: If you manually restart a running instance of the FortiSOAR MEA using the docker restart <fortisoar-container-id> from the FortiManager root shell, or if the FortiSOAR MEA OS gets rebooted due to restarting of the docker container itself with either an OS reboot command or due to any application, then some of the filesystems within the docker container go into the read-only mode. This causes the "tomcat" service to not restart.
    Resolution:
    Restart the FortiSOAR MEA by the following commands on the FortiManager CLI:
    # config system docker
    # set fortisoar disable
    # end
    
    # config system docker
    # set fortisoar enable
    # end