Error: " . . . kicker can not open bmserver.pid file . . . " logged by the conduit for Symantec Brightmail
|Article:TECH83047|||||Created: 2005-01-12|||||Updated: 2005-01-28|||||Article URL http://www.symantec.com/docs/TECH83047|
The following error is logged by the Symantec Brightmail conduit:
11 Jan 2005 07:08:07 (ERROR:13872.1):  kicker: can not open bmserver pid file /opt/symantec/sbas/Scanner/jobs/bmserver/bmserver.pid: No such file or directory.
The following table lists the possible causes and their solutions:
|The bmserver.pid file is corrupted.||Replace the bmserver.pid file.|
|The bmserver.pid file is missing or not readable.||Stop and then start the affected host through the Control Center.|
|The bmserver jobs directory does not exist.||Create the missing directory.|
|The bmserver jobs directory cannot be written to by the mailwall user||Change the permissions on the bmserver jobs directory to give write permission to the mailwall user.|
The conduit process that downloads new rulesets cannot signal the scanning server that it should update its active rules. If this condition persists, it can negatively impact filtering effectiveness.
The following is an example of the process id file:
host$ ls -laR /opt/symantec/sbas/Scanner/jobs/bmserver
drwxr-x--- 2 mailwall bmi 4096 Jan 9 20:43 .
drwxr-x--- 7 mailwall bmi 4096 Dec 3 09:12 ..
-rwx------ 1 mailwall bmi 0 Jan 9 20:43 bmserver.out
-rw-r--r-- 1 mailwall bmi 6 Jan 9 20:43 bmserver.pid
-rw-r--r-- 1 mailwall bmi 6 Jan 9 20:43 pidfile
Article URL http://www.symantec.com/docs/TECH83047