Restart Fortigate http/gui processes automatically because of a memory leakage

[filiaks1]

Hello To All,

Because of a memory leakage the http process needs to be restart from time so I figured using auto-script (there is not analyzer at the moment to use the fabric automation as mentioned in https://docs.fortinet.com/document/fortigate/6.2.14/cookbook/351998/creating-automation-stitches ) that can be scheduled or tiggered through the API but for example the command in "https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-restart-kill-all-the-processes-with... " that is fnsysctl killall httpsd is for backend-shell access and also diagnose test application <daemon_name> 99  that is suggested in the article belos does not seem to find the http processes https://community.fortinet.com/t5/FortiGate/Technical-Tip-Restarting-internal-processess-daemons/ta-...

I only need to find the correct command on 7.4 for Fortigate and then I can create the configuration script and then run the below commands:

 (auto-script) # show
config system auto-script
edit "memory"
set script "fnsysctl killall httpsd"
next
end

POST /api/v2/monitor/system/memory/run

[Yurisk · Accepted solution]

This happens because you're using an evaluation VM copy of Fortigate on which this command is disabled by Fortinet. If you use this command on any FGT with valid license, even FG VM, it will work.

[nithincs]

hi,

the script is correct.

You can also follow alert mail for concerve mode and logs collection https://community.fortinet.com/t5/FortiGate/Technical-Tip-Automation-stitch-for-the-conserve-mode/ta....

[filiaks1]

As I mentioned "fnsysctl killall httpsd" does not work on 7.4 and I am testing in my lab with the default admin user. How can I enter backend shell on 7.4 to run fnsysctl commands?

 fnsysctl killall httpsd
Unknown action 0

[Yurisk · Accepted solution]

This happens because you're using an evaluation VM copy of Fortigate on which this command is disabled by Fortinet. If you use this command on any FGT with valid license, even FG VM, it will work.

[filiaks1 · Accepted solution]

Thanks I tested it and it is ok. I even used the ansible module https://docs.ansible.com/ansible/latest/collections/fortinet/fortios/fortios_system_auto_script_modu... to create it on all forti devices and then with the URI module https://docs.ansible.com/ansible/latest/collections/ansible/builtin/uri_module.html I am triggering it when I want :)