CBPolicyD: Source 'any' is not a valid specification

Hello CWP Community,

I hope this message finds everyone well. I am currently facing an issue with my CentOS 7.9.2009 server and would appreciate any assistance or insights you can provide.

Problem Description:
I am encountering the following error in the logs:

Source 'any' is not a valid specification

Server Configuration:

• CentOS Version: 7.9.2009 (Core)
• Kernel: 3.10.0-1160.119.1.el7.x86_64
• Active Services:
• Apache Webserver: Active
• Nginx Reverse Proxy: Active
• BIND DNS Server: Active
• SSH Server: Active
• Postfix Mail Server: Active
• Dovecot IMAP/POP3 Server: Active
• ClamAV: Active
• AMaViS: Active
• OpenDKIM: Active
• SpamAssassin: Active
• CBPolicyD: Active

Steps Taken:
1. Checked policies in CWP panel, especially policy IDs 6 (Default Server Limit) and 7 (package_default).
2. Verified configuration files manually:

Code: [Select]

/etc/cbpolicyd/cluebringer.conf
/etc/cbpolicyd/webui.conf
4. Restarted services:

Code: [Select]

systemctl restart cbpolicyd
systemctl restart postfix
5. Monitored logs using:

Code: [Select]

tail -f /var/log/messages
Jul 12 16:14:14 srv5us3 cbpolicyd: [2024/07/12-16:14:14 - 2467] [POLICIES] WARNING: [ID:6/Name:Default Server Limit]=>(group:cwp_domains): - Source 'any' is not a valid specification
Jul 12 16:14:14 srv5us3 cbpolicyd: [2024/07/12-16:14:14 - 2467] [POLICIES] WARNING: [ID:7/Name:Default Server Limit]=>(group:cwp_domains): - Source 'any' is not a valid specification
Jul 12 16:14:15 srv5us3 cbpolicyd: [2024/07/12-16:14:15 - 2465] [POLICIES] WARNING: [ID:6/Name:Default Server Limit]=>(group:cwp_domains): - Source 'any' is not a valid specification
Jul 12 16:14:15 srv5us3 cbpolicyd: [2024/07/12-16:14:15 - 2465] [POLICIES] WARNING: [ID:7/Name:Default Server Limit]=>(group:cwp_domains): - Source 'any' is not a valid specification

Current Situation:
Despite these steps, the error persists. I have also reduced the maximum emails allowed in policies 6 and 7 to 25 and 20 respectively. I am now looking to identify the exact file where these changes are stored to further troubleshoot the issue.

Any advice or guidance on resolving this error would be greatly appreciated.

Thank you in advance for your support!

Best regards,

I would say at this point all bets are off on CentOS 7.9... it is now EOL so best to ELevate to AlmaLinux 8 for production purposes. Then we can support you better with current advice and a better foundation going forward.