<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cpanel on Daniel Pomfret</title>
    <link>https://pomfret.uk/tags/cpanel/</link>
    <description>Recent content in Cpanel on Daniel Pomfret</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Daniel Pomfret</copyright>
    <lastBuildDate>Fri, 29 Jun 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pomfret.uk/tags/cpanel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>cPanel : &#34;The Exim database is most likely corrupted and the following steps should be followed&#34;</title>
      <link>https://pomfret.uk/posts/cpanel-the-exim-database-is-most-likely-corrupted-and-the-following-steps-should-be-followed/</link>
      <pubDate>Fri, 29 Jun 2018 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/cpanel-the-exim-database-is-most-likely-corrupted-and-the-following-steps-should-be-followed/</guid>
      <description>&lt;p&gt;If you are seeing the following error in the exim logs, you will need to reset the exim databases.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;&amp;ldquo;The Exim database is most likely corrupted and the following steps should be followed&amp;rdquo;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;To reset exim&amp;rsquo;s database of retry, reject, and wait-report_smtp attempts on cPanel, I find the safest way is to run the following commands.&lt;/p&gt;&#xA;&lt;p&gt;/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry &amp;gt; /dev/null&#xA;/usr/sbin/exim_tidydb -t 1d /var/spool/exim reject &amp;gt; /dev/null&#xA;/usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp &amp;gt; /dev/null&#xA;service exim restart&lt;/p&gt;</description>
    </item>
    <item>
      <title>cPanel Error:The system experienced the following error when it attempted to install the “OWASP ModSecurity Core Rule Set V3.0” vendor</title>
      <link>https://pomfret.uk/posts/cpanel-errorthe-system-experienced-following-error-attempted-install-owasp-modsecurity-core-rule-set-v3-0-vendor/</link>
      <pubDate>Tue, 06 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/cpanel-errorthe-system-experienced-following-error-attempted-install-owasp-modsecurity-core-rule-set-v3-0-vendor/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve noticed that since upgrading cPanel to v68.0.28 our ModSecurity Vendors have dropped off, and no longer available in the interface, and the rules are no longer available for Apache.&lt;/p&gt;&#xA;&lt;p&gt;When trying to add the OWASP Ruleset (Vendor) back, I get the following error message.&lt;/p&gt;&#xA;&lt;p&gt;Error:The system experienced the following error when it attempted to install the “OWASP ModSecurity Core Rule Set V3.0” vendor: API failure: The system could not validate the new Apache configuration because httpd exited with a nonzero value. Apache produced the following error: httpd: Syntax error on line 208 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 29 of /etc/apache2/conf.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/conf.d/modsec_vendor_configs/OWASP/modsecurity_crs_10_setup.conf: No such file or directory&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
