Error caught while calling pidusage PM2 error WMIC -> then restart many time process at pm2

What's going wrong?

from .pm2/pm2.log:

2021-08-01T05:45:40: PM2 error: Error caught while calling pidusage
2021-08-01T05:45:40: PM2 error: Error: �G���[:

�� = ��O���������܂����B

PM2 version info

2021-08-02T14:50:59: PM2 log: PM2 version : 4.5.6
2021-08-02T14:50:59: PM2 log: Node.js version : 8.11.3
2021-08-02T14:50:59: PM2 log: Current arch : x64
2021-08-02T14:50:59: PM2 log: PM2 home : C:\Users\Administrator.pm2
2021-08-02T14:50:59: PM2 log: PM2 PID file : C:\Users\Administrator.pm2\pm2.pid
2021-08-02T14:50:59: PM2 log: RPC socket file : \.\pipe\rpc.sock
2021-08-02T14:50:59: PM2 log: BUS socket file : \.\pipe\pub.sock
2021-08-02T14:50:59: PM2 log: Application log path : C:\Users\Administrator.pm2\logs
2021-08-02T14:50:59: PM2 log: Worker Interval : 30000
2021-08-02T14:50:59: PM2 log: Process dump file : C:\Users\Administrator.pm2\dump.pm2
2021-08-02T14:50:59: PM2 log: Concurrent actions : 2
2021-08-02T14:50:59: PM2 log: SIGTERM timeout : 1600

Supporting information

2021-07-28T19:37:34: PM2 log: [PM2] This PM2 is not UP TO DATE
2021-07-28T19:37:34: PM2 log: [PM2] Upgrade to version 5.1.0
2021-07-29T19:37:35: PM2 log: [PM2] This PM2 is not UP TO DATE
2021-07-29T19:37:35: PM2 log: [PM2] Upgrade to version 5.1.0
2021-07-30T19:37:35: PM2 log: [PM2] This PM2 is not UP TO DATE
2021-07-30T19:37:35: PM2 log: [PM2] Upgrade to version 5.1.0
2021-07-31T19:37:36: PM2 log: [PM2] This PM2 is not UP TO DATE
2021-07-31T19:37:36: PM2 log: [PM2] Upgrade to version 5.1.0
2021-08-01T05:43:10: PM2 error: Error caught while calling pidusage
2021-08-01T05:43:10: PM2 error: Error: �G���[:

�� = ��O���������܂����B

2021-08-01T05:43:40: PM2 error: Error caught while calling pidusage
2021-08-01T05:43:40: PM2 error: Error: �s���� WMIC ��O�ł��B

2021-08-01T05:44:09: PM2 error: Error caught while calling pidusage
2021-08-01T05:44:09: PM2 error: Error: pidusage wmic command exited with code 3221225794
2021-08-01T05:44:26: PM2 log: App [server:0] exited with code [3221225477] via signal [SIGINT]
2021-08-01T05:44:26: PM2 log: App [server:0] starting in -fork mode-
2021-08-01T05:44:26: PM2 log: App [server:0] online
2021-08-01T05:45:40: PM2 error: Error caught while calling pidusage
2021-08-01T05:45:40: PM2 error: Error: �G���[:

�� = ��O���������܂����B

2021-08-01T05:46:10: PM2 error: Error caught while calling pidusage
2021-08-01T05:46:10: PM2 error: Error: �s���� WMIC ��O�ł��B

2021-08-01T05:46:40: PM2 error: Error caught while calling pidusage
2021-08-01T05:46:40: PM2 error: Error: pidusage wmic command exited with code 3221225794
2021-08-01T05:46:51: PM2 log: App [server:0] exited with code [3221225477] via signal [SIGINT]
2021-08-01T05:46:51: PM2 log: App [server:0] starting in -fork mode-
2021-08-01T05:46:51: PM2 log: App [server:0] online
2021-08-01T05:47:10: PM2 error: Error caught while calling pidusage
2021-08-01T05:47:10: PM2 error: Error: pidusage wmic command exited with code 3221225794
2021-08-01T05:47:39: PM2 error: Error caught while calling pidusage
2021-08-01T05:47:39: PM2 error: Error: pidusage wmic command exited with code 3221225794
2021-08-01T05:47:43: PM2 log: App [server:0] exited with code [3] via signal [SIGINT]
2021-08-01T05:47:43: PM2 log: App [server:0] starting in -fork mode-
2021-08-01T05:47:43: PM2 log: App [server:0] online

Start by reproducing the pidusage failure on the Windows environment described, then inspect the WMIC command and the PM2 monitoring and restart path. Use the logged exit codes and repeated server restarts to trace the failure; done means pidusage errors no longer trigger the repeated process restarts and the relevant behavior is covered by a regression test.