Fortinet Document Library

Version:


Table of Contents

7.0.0
Download PDF
Copy Link

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. To restart the FortiSOAR MEA , run 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. To restart the FortiSOAR MEA , run the following commands on the FortiManager CLI:

# config system docker
# set fortisoar disable
# end

# config system docker
# set fortisoar enable
# end