Fine tuning Queue for external filters

Support General Configuration
1

Maybe is nothing but script try to connect to services when they are disabled!

# created by AXIGEN version 10.6.5
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:0024F8FB: Filter AVG AntiVirus Filter(127.0.0.1:55555):[ERROR]: Could not connect to filter
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:0024F8FB: Error connecting to socket filter: AVG AntiVirus Filter(127.0.0.1:55555)
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:002BBC76: Filter AVAST(127.0.0.1:5036):[ERROR]: Could not connect to filter
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:002BBC76: Error connecting to socket filter: AVAST(127.0.0.1:5036)
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:00095756: Error connecting to socket filter: AVAST(/var/run/avast4/local.sock) reason: No such file or directory
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:00095756: Error connecting
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:00347C04: Filter ClamAV(127.0.0.1:3310):[ERROR]: Could not connect to filter
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:00347C04: Error connecting to socket filter: ClamAV(127.0.0.1:3310)
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:0017D88B: Filter BD(127.0.0.1:1344):[ERROR]: Could not connect to filter
2025-02-27 12:28:15 +0100 02 sssr PROCESSING:0017D88B: Error connecting to socket filter: BD(127.0.0.1:1344)
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0026762E: Filter AVG AntiVirus Filter(127.0.0.1:55555):[ERROR]: Could not connect to filter
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0026762E: Error connecting to socket filter: AVG AntiVirus Filter(127.0.0.1:55555)
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:003232C7: Filter AVAST(127.0.0.1:5036):[ERROR]: Could not connect to filter
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:003232C7: Error connecting to socket filter: AVAST(127.0.0.1:5036)
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:003CD77F: Error connecting to socket filter: AVAST(/var/run/avast4/local.sock) reason: No such file or directory
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:003CD77F: Error connecting
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0037CA76: Filter ClamAV(127.0.0.1:3310):[ERROR]: Could not connect to filter
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0037CA76: Error connecting to socket filter: ClamAV(127.0.0.1:3310)
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0023C584: Filter BD(127.0.0.1:1344):[ERROR]: Could not connect to filter
2025-02-27 20:54:19 +0100 02 sssr PROCESSING:0023C584: Error connecting to socket filter: BD(127.0.0.1:1344)

2

Hello @Antonello

Yes, this is normal and is triggered when there is a login into the WebAdmin interface so the dedicated filter [1] dashboard could be displayed with real results.

In order to have a fresh result (and not the one computed when you logged in) you have an option To restart the detection process (immediately under the table)

HTH,
Ioan

[1] Security & Filtering > Antivirus & Antispam > Supported Applications