cpanel_exim_system_filter.lock

Vinayak

Well-Known Member
Jun 27, 2003
280
2
168
Bharat
cPanel Access Level
Root Administrator
Why this file at "/etc/cpanel_exim_system_filter.lock"

Containing
15193
/usr/local/cpanel/scripts/eximconfgen - waiting for lock on /etc/cpanel_exim_system_filter
CENTOS 6.4 x86_64 virtuozzo
WHM 11.38.1 (build 15)
exim-4.80.1-1.cp1136.x86_64
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,911
2,234
363
cPanel Access Level
DataCenter Provider
Twitter
Hello :)

Is there an Exim or cPanel update in progress on your system? Or, are you making any changes to the Exim configuration? You can check the process list for that process or PID with a command such as:

Code:
ps aux|grep eximconf
You may need to kill the process if it's hanging, or manually remove the lock file.

Thank you.
 

Vinayak

Well-Known Member
Jun 27, 2003
280
2
168
Bharat
cPanel Access Level
Root Administrator
No Exim or cPanel update running, no process to kill.

This lock files appears when updating Exim config through "Home » Service Configuration » Exim Configuration Manager" and remains there.

Surprisingly Exim is not taking the changes that are being made.

What I followed is:

1)
* Place each sysfilter block you wish to include in a unique file at:
/usr/local/cpanel/etc/exim/sysfilter/options/
* Enable or disable the custom block in WHM using:
Service Configuration => Exim Configuration Manager => Filters => Custom Filter: [your unique file]
Above method has been working till few days back. But today lock file appears, remain there and rules in new sysfilter file are not incorporated.

No success removing it manually, it comes again when saving config through "Exim Configuration Manager".
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,911
2,234
363
cPanel Access Level
DataCenter Provider
Twitter
Per the ticket, this issue was the result of a reference to a custom filter file in:

/etc/exim.conf.localopts

The custom filter file did not actually exist, thus the Exim configuration file could not build successfully. The reference to the non-existent file was removed to resolve the issue.

Thank you.