windows_script collect timeout

[liyfbeat]

I use Windows Script to collect monitoring data of Windows servers. The collector has been deployed on the Windows server, but it often stops collecting server information after running for a few hours, while other tasks can be executed normally. Since security software is installed on the server, I suspect that it is caused by Windows Script calling PowerShell. The following logs will be displayed in the collector's error logs：
2025-06-05 20:11:01.403 [metrics-task-timeout-monitor-0] ERROR org.apache.hertzbeat.collector.dispatch.CommonDispatcher Line:168 - [Collect Timeout]:
id: 516487926905600
app: "windows_script"
metrics: "top_mem_process"
priority: 5
time: 1749125461403
code: TIMEOUT
msg: "collect timeout"

I need to add that even if I stopped the security software on another server, the collect timeout still occurred, and then the windows script was completely stopped.

Ps.
hertzbeat version is 1.6.1

[liyfbeat]

@tomsun28 Could U give me some suggestions?

[tomsun28]

hi, based on the log analysis, it seems that the metric collection on Windows timed out. This needs to be investigated further to determine why the execution timed out — could it be due to pollshell?

[liyfbeat]

It's possible, but I'm not certain what's causing this. After all, restarting the collector allows it to resume normal data collection, but it malfunctions again after running for a while.

[lx1229]

Do u try to run command of 'top_mem_process' on terminal or power bash manually?

[liyfbeat]

Certainly, either executing PowerShell commands directly in the operating system or performing data collection through HertzBeat is feasible.

[liyfbeat]

The issue is that after HertzBeat has been collecting data for some time, it stops. Upon investigating the cause, it is found that the PowerShell execution has timed out. Restarting the collector allows data collection to resume normally.

[lx1229]

A wired issue! I will keep investigating this! Let's try to find out the true reason