Scan stuck in the "processing" state on the SMB Service

Symptom

The log appears to be stuck with the following entries:

Starting processing server. Listening on 127.0.0.1:6002

Starting health server. Listening on 127.0.0.1:7002

Using configured transport receive timeout of: 600 Starting worker

Under normal conditions, the system should continuously log events in all 600x files instead of remaining stuck at this stage.

Possible Cause

SMB Service process stuck due to insufficient CPU resources The psutil.open_files() function hangs or freezes for several minutes, issue occurs specifically on Windows.

Solution

The issue was fixed starting with Version 3.5.2

If Further Assistance is required, please proceed to create a support case or chat with our support engineer.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
On This Page
Scan stuck in the "processing" state on the SMB ServiceSymptomPossible CauseSolution