Technical Tip: How to restart a specific WAD worker process

[ojacinto]

Description	This article describes how to restart a specific WAD worker process.
Scope	FortiProxy v7.0.0, v7.2.0, v7.4.0 and above.
Solution	Identify the index of the WAD worker process desired to be restarted. To do this, execute the following commands: FPX # diagnose debug reset FPX # diagnose debug enable FPX # diagnose test application wad 1000  <----- This will show all wad processes information (type, index, PID of each of them, and the current state). FPX-VM02 # diagnose test application wad 1000 Process [0]:  WAD manager type=manager(0) pid=1534 diagnosis=yes. Process [1]: type=dispatcher(1) index=0 pid=1583 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [2]: type=worker(2) index=0 pid=1584 state=running                    diagnosis=no debug=enable valgrind=supported/disabled Process [3]: type=worker(2) index=1 pid=1585 state=running                    diagnosis=no debug=enable valgrind=supported/disabled Process [4]: type=algo(3) index=0 pid=1582 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [5]: type=informer(4) index=0 pid=1576 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [6]: type=user-info(5) index=0 pid=1580 state=running                    diagnosis=no debug=enable valgrind=supported/disabled Process [7]: type=cache-service-cs(6) index=0 pid=1574 state=running                    diagnosis=no debug=enable valgrind=supported/disabled Process [8]: type=cert-inspection(8) index=0 pid=1578 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [9]: type=YouTube-filter-cache-service(9) index=0 pid=1579 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [10]: type=debug(11) index=0 pid=1572 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [11]: type=config-notify(12) index=0 pid=1577 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [12]: type=tls-fgpt-service(13) index=0 pid=1581 state=running                    diagnosis=no debug=enable valgrind=unsupported/disabled Process [13]: type=object-cache(14) index=0 pid=1573 state=running                    diagnosis=no debug=disable valgrind=unsupported/disabled Process [14]: type=preload daemon(17) index=0 pid=1575 state=running                    diagnosis=no debug=disable valgrind=unsupported/disabled In this case, it is possible to see that FortiProxy-VM launched two worker processes. To restart the worker process with the index 0, it is necessary to execute the command: diagnose wad worker restart  <index>   <----- Restarts specific worker by the index. To restart all WADworker processes, it is possible to execute one of the following options: diagnose wad worker restart  <-----  Restart all WAD workers. Or:    diagnose test application wad 97   <----- Restart all WAD worker processes. FPX-VM02 # diagnose wad worker restart 0