Troubleshooting Tip: Automation Stitch Fails to Ban IP Addresses Due to Auto‑Script Table Limit Reached
| Description | This article explains an issue where a FortiGate automation stitch fails to ban source IP addresses. Although the stitch triggers successfully, the action does not execute. The root cause is that the system.auto-script table has reached its maximum allowed number of entries, preventing new CLI‑script actions from being created. A step‑by‑step procedure is provided to diagnose and resolve the issue. |
| Scope | FortiGate. |
| Solution | An automation stitch is created to ban source IP addresses using a FortiAnalyzer event handler, based on IPS event logs.
Configuration example:
config system automation-action
config system automation-trigger
config system automation-stitch The automation stitch shows as triggered in system event logs, but the source IP address does not appear in: diagnose user <banned-ip> list Troubleshooting: Debug Output. Run the automation stitch debugging processes:
Example output: pid:5763-__handle_pkg_logs()-356: Subscriber:4 processing package size:486530 logs:460 pickup:2
Root cause:
The error message 'Too many entries in all tables of 'system.auto-script' in vdom global: 256 / vdom-max = 256' occurs when the maximum number of automation scripts permitted in the global VDOM has been reached.
To determine the maximum number of automation scripts supported by a FortiGate device, run 'print tablesize' command and check for the system.auto-script entry in the output to see how many auto-scripts are supported on the FortiGate.
print tablesize system.auto-script: 0 256 512 ...
In example output above , 256 represents per VDOM limit whereas 512 represents Global limit (Technical Tip: FortiGate maximum values table).
List existing Auto-Scripts:
show config system auto-script Delete unused or obsolete entries:
config system auto-script
Once the number of auto-scripts falls below the system limit, automation stitches resume normal operation and source IP addresses are successfully added to the banned list.
Related articles: |