In FortiProxy v7.6.6, when editing a CLI Script action in Security Fabric -> Automation -> Automation Action via GUI, an error occurs, as it is displayed in the following screenshot:
A pop-up is shown with this error message:
"Error creating CMDBerror: Expected response argument to be an object or string, got null"
Moreover, at the same time, a segmentation fault error occurs regarding the cmdbsvr process as below:
diagnose debug crashlog read
...
2026-MM-DD 13:48:34 <18499> application cmdbsvr
2026-MM-DD 13:48:34 <18499> *** signal 11 (Segmentation fault) received ***
2026-MM-DD 13:48:34 <18499> Register dump:
2026-MM-DD 13:48:34 <18499> RAX: 0000000000000000 RBX: 000055dc25f6dc40
2026-MM-DD 13:48:34 <18499> RCX: 000055dbf0a731c8 RDX: ffffffffff4f2feb
2026-MM-DD 13:48:34 <18499> R08: 00007fd44f8e2fe8 R09: 0000000000000000
2026-MM-DD 13:48:34 <18499> R10: 00007ffdfa236270 R11: 0000000000000008
2026-MM-DD 13:48:34 <18499> R12: 000055dc26223f9d R13: 00007ffdfa240590
2026-MM-DD 13:48:34 <18499> R14: 000055dc26223f9d R15: 000055dc25f6dc40
2026-MM-DD 13:48:34 <18499> RSI: 000055dc26223f9d RDI: 0000000000000000
2026-MM-DD 13:48:34 <18499> RBP: 00007ffdfa2361f0 RSP: 00007ffdfa2361e0
2026-MM-DD 13:48:34 <18499> RIP: 000055dbefc39ac9 EFLAGS: 0000000000010246
2026-MM-DD 13:48:34 <18499> CS: 0033 FS: 0000 GS: 0000
2026-MM-DD 13:48:34 <18499> Trap: 000000000000000e Error: 0000000000000004
2026-MM-DD 13:48:34 <18499> OldMask: 0000000000000000
2026-MM-DD 13:48:34 <18499> CR2: 0000000000000058
2026-MM-DD 13:48:34 <18499> stack: 0x7ffdfa2361e0 - 0x7ffdfa241df0
2026-MM-DD 13:48:34 <18499> Backtrace:
2026-MM-DD 13:48:34 <18499> [0x55dbefc39ac9] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb813ad] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb73b70] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb746e1] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb8e406] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb8eb38] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb70dac] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefb71861] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbd430f] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbf7d81] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbecf6c] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbe20ed] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbde695] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefbe1e30] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbefc00477] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6b0a02] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6b6f6b] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6b75e6] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6ba232] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6bac23] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> [0x7fd4534b5deb] => /lib/libc.so.6 {0x7fd453492000}
2026-MM-DD 13:48:34 <18499> [0x55dbee6abada] => /bin/cmdbsvr {0x55dbee4a2000}
2026-MM-DD 13:48:34 <18499> fortidev 6.0.1.0005
2026-MM-DD 13:48:34 the killed daemon is /bin/cmdbsvr: status=0xb
As a workaround it it is possible to edit the CLI Script in Automation Action via CLI without errors.
The solution has been released in FortiProxy v7.6.7 and above.
| 
