Issue with piping
Hi,
I have an issue with email piping. I have two email adresses forwarded to whmcs. That worked before. If i send a mail to one of this mail adresseses whmcs makes a ticket but also sends an error mail to the person who send the mail.
the error mails tells me there is a unexpected syntax error in local.ini. At first it was an error in php5.6, as none of my clients is using php 5.6 i decide to only use php 7 and 7.1 on my server. This didn't solved the problem. The problem is still the same, the error message points me to (in php 5.6 and 7.0) the opcache.validate_timestamps=0 line in the ini file
I tried to put a 1 instead of the 0 on the line opcache.validate_timestamps=0 this also didn't solve the problem.
=====error message====
PHP: syntax error, unexpected '(' in /opt/cpanel/ea-php70/root/etc/php.d/local.ini on line 1648
Action: failed
Final-Recipient: rfc822;|/home/drentheweb/whmcs_crons/pipe.php
Status: 5.0.0
==================
-
=====error message==== PHP: syntax error, unexpected '(' in /opt/cpanel/ea-php70/root/etc/php.d/local.ini on line 1648 Action: failed Final-Recipient: rfc822;|/home/drentheweb/whmcs_crons/pipe.php Status: 5.0.0 ==================
Hello, Could you verify what version of cPanel is installed on this server, and what appears on line 1648 of the /opt/cpanel/ea-php70/root/etc/php.d/local.ini file on this server? Thank you.0 -
1646 ; Opcache Tuning 1647 opcache.revalidate_freq=0 1648 opcache.validate_timestamps=0 (comment this out dev environment) 1649 opcache.max_accelerated_files=7963 1650 opcache.memory_consumption=192 1651 opcache.interned_strings_buffer=16 1652 opcache.fast_shutdown=1 I got the latest release version of cpanel: cPanel & WHM 64.0 (build 36) 0 -
Hello, Can you temporarily move the local.ini file out of the way and restart Apache to verify if there's something in that file causing the issue? EX: mv /opt/cpanel/ea-php70/root/etc/php.d/local.ini /opt/cpanel/ea-php70/root/etc/php.d/local.ini.backup1 /scripts/restartsrv_httpd
Thank you.0 -
Thank you, somehow: /scripts/restartsrv_httpd was enough to fix the issue. 0 -
Hello, I'm happy to see the issue is now solved. Let us know if you encounter any additional issues. Thank you. 0
Please sign in to leave a comment.
Comments
5 comments