FortiGate: killed daemon is /bin/pyfcgid: status=0x0
# diagnose debug crashlog read
[...]
288: 2021-08-16 13:57:01 the killed daemon is /bin/pyfcgid: status=0x0
289: 2021-08-16 15:11:06 the killed daemon is /bin/pyfcgid: status=0x0
290: 2021-10-07 14:58:50 the killed daemon is /bin/pyfcgid: status=0x0
291: 2021-10-08 14:48:05 the killed daemon is /bin/pyfcgid: status=0x0
292: 2021-10-08 15:36:08 the killed daemon is /bin/pyfcgid: status=0x0
293: 2021-10-08 18:13:56 the killed daemon is /bin/pyfcgid: status=0x0
289: 2021-08-16 15:11:06 the killed daemon is /bin/pyfcgid: status=0x0
290: 2021-10-07 14:58:50 the killed daemon is /bin/pyfcgid: status=0x0
291: 2021-10-08 14:48:05 the killed daemon is /bin/pyfcgid: status=0x0
292: 2021-10-08 15:36:08 the killed daemon is /bin/pyfcgid: status=0x0
293: 2021-10-08 18:13:56 the killed daemon is /bin/pyfcgid: status=0x0
Technical Tip: pyfcgid (python config daemon) entry in FortiGate crash log
status=0x0 means that this process will be terminated and deleted so
that kernel can give space for other processes in terms of resource
allocation.
In other works, status=0x0 is normal process shutdown due to job done without abnormality.
Update