kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.
search cancel

kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.

book

Article ID: 265706

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

We encounter the following error :

kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.

Could you please help us resolve this issue?

Resolution

A reported warning can be found in the conduit_log:

2023-05-10T09:04:59+02:00 (WARNING:6946.3719128896): [7063] kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.
2023-05-10T09:16:06+02:00 (WARNING:7634.2323306304): [7063] kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.
2023-05-10T09:20:19+02:00 (WARNING:7299.4092630848): [7063] kicker: can not open bmserver pid file /data/scanner/jobs/bmserver/bmserver.pid: No such file or directory.

Conduit services are used only to download and update spam definitions.


This warning indicates that the conduit attempted to signal the Brightmail Engine to tell it to reload the rulesets (presumably because there was an update) but the Brightmail Engine wasn't available at the time.

If the Control Center shows that the Brightmail Engine service is running, this warning can be ignored.