- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
fortiagte v7.2.0 Automation Stitch for daily backup not running.
Hello Expert,
I create a automated stitch to schedule daliy back and tftp the file to windows server.
When I Test using a exec backup full-config tftp backup.cfg 192.xx.xx.xx from the fortigate the backup works okay.
I created the action trigger and stitch but for some reason the backup is not generated at the designated time as defind in the trigger.
I humbly request some guidance to troubleshoot Thank you
- Labels:
-
FortiGate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello jomof,
Thank you for reaching out. My understanding is that the backup works through the stitch however it does not execute at the 25th minute of every hour according to the screen shot. You can try troubleshooting steps for automation stitches running a debug as advised on the following document:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-check-why-automation-stitch-is-not-...
You can also check system event logs to verify if something wrong happened when the stitch is triggered from Log&Report>System Events menu.
Thank you,
saleha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Change the 'action execution' from Parallel to Sequential. Did it work this time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jomof,
If you run the same cmd manually on the CLI it works?
collect below output:-
diag debug app autod -1
diag debug enable
test the automation
Salon Raj Joshi
Created on ‎11-28-2024 06:42 AM Edited on ‎11-28-2024 06:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When i executed the command for debuging see screen shot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jomof ,
Please disable the 'Execute on security Fabric' option in the CLI Script Edit page in the GUI for a try.
Jerry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello disable as per suggestion but still no trigger.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you execute the cmd while triggering the automation stitch?
Salon Raj Joshi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jomof,
Yes it looks like the execution of the script expired. Do you get any notification on the tftp server that there was an attempt to connect or that does not even happen. Have you tried to rebuild the script specially the trigger and test again. can you share the stitch, action and trigger config in cli please:
show sys automation-stitch <name>
show sys automation-trigger <name>
show sys automation-action <name>
Thank you,
saleha
