Issue with temp folder (and Wordpress) after update
Hello,
There recently has been an update on my server (with WHM/cPanel) and now all Wordpress web site have an issue when updating or adding media files : there seem to be no temp folder available.
As this used to always work fine, not sure what has changed and what I should do to fix this.
I've connected to the server and check, there is a tmp folder at the root of the server with correct permission, but still.
Thanks for your ideas,
Antoine
-
Hello @aolbrechts, Please review the following threads to determine if your system is affected by either of the referenced bugs: In Progress - php session timeout since 64.0 update Custom PHP Session Handler If not, please post the output from the following commands: cat /etc/redhat-release cat /usr/local/cpanel/version rpm -qa|grep cagefs /opt/cpanel/ea-php56/root/usr/bin/php -i|grep session.save /opt/cpanel/ea-php70/root/usr/bin/php -i|grep session.save
Thank you.0 -
Hello, I manually edited the php.ini to set a temp folder and it seems it's OK now. Not sure why this has changed since yesterday. Antoine 0 -
Hello Antoine, While manually editing the session.save_path path acts as a workaround, I recommend investigating to determine why the new value was not working on your system (the change improves security). You can read more about the changes to the session.save_path PHP value in cPanel 64 on the following document: 0 -
I had to specify the /tmp directory so it isn't in the MultiPHP INI Editor, I had to go manually in the editor mode. >> upload_tmp_dir = /tmp Should be OK now, I guess. 0 -
Hello, It seems that's unrelated to the new session path. I'm happy to see the issue is now addressed. Thank you for updating us with the outcome. 0 -
I've always been mentioning the temp folder, not session path. It's OK, now. 0 -
Hello, I'm having the exact same issue, upload_tmp_dir appears as "no value" with php_info(), was just after cPanel update that all the Wordpress installations on the server started to malfunction, they can't update or upload media files, all because the tmp directory issue, how can I fix this? Note: I'm using PHP-FPM if that matters. EDIT: I've changed the setting upload_tmp_dir using the PHP INI Editor to "/tmp" as @aolbrechts said and now everithing is working again, but I don't think this is the right and safest aproach, so it would be nice if someone can explain why this is hapening with the cPanel update. 0 -
Hello, I'm having the exact same issue, upload_tmp_dir appears as "no value" with php_info(), was just after cPanel update that all the Wordpress installations on the server started to malfunction, they can't update or upload media files, all because the tmp directory issue, how can I fix this? Note: I'm using PHP-FPM if that matters. EDIT: I've changed the setting upload_tmp_dir using the PHP INI Editor to "/tmp" as @aolbrechts said and now everithing is working again, but I don't think this is the right and safest aproach, so it would be nice if someone can explain why this is hapening with the cPanel update.
Could you verify which version of cPanel your system was updated "from" and "to"? Also, did you recently update to EasyApache 4, or was that utilized before the cPanel update? Thank you.0 -
Could you verify which version of cPanel your system was updated "from" and "to"? Also, did you recently update to EasyApache 4, or was that utilized before the cPanel update? Thank you.
Where can I check from which version I updated from?, it updated to 64.0.15 and I have been using Easy Apache 4 for more than a year.0 -
Exact same issue here after Cpanel update. Current version is 64.0 build 17. We've had complaints from customers on several servers, we have yet to check them all. Edit: I changed the upload dir in the php editor to /tmp, restarted apache but the phpinfo.php still shows 'no value'. 0 -
Hello, Could anyone facing this issue verify what method was used to make the change to the upload_tmp_dir PHP configuration value prior to encountering this error message? Or, was it simply always left unconfigured? Also, what's configured in the /var/cpanel/php-fpm.d/$username.conf file for the affected account (specifically the php_admin_value[upload_tmp_dir] and env[TMPDIR] values)? Exact same issue here after Cpanel update. Current version is 64.0 build 17. We've had complaints from customers on several servers, we have yet to check them all. Edit: I changed the upload dir in the php editor to /tmp, restarted apache but the phpinfo.php still shows 'no value'.
Would you mind opening a support ticket using the link in my signature, and posting the ticket number here? We'd like to take a closer look at an affected system to see if we can determine the change that resulted in this issue. Thank you.0 -
In version 11.62 and earlier, the upload_tmp_dir script is set to default. No directory is specified and it works fine. It is possible that the default path has changed in the last version. 0 -
In version 11.62 and earlier, the upload_tmp_dir script is set to default. No directory is specified and it works fine.
Could you review /var/cpanel/php-fpm.d/$username.conf for an account affected by the issue and verify what's configured for the "php_admin_value[upload_tmp_dir]" and "env[TMPDIR]" values? Thank you.0 -
Could you review /var/cpanel/php-fpm.d/$username.conf for an account affected by the issue and verify what's configured for the "php_admin_value[upload_tmp_dir]" and "env[TMPDIR]" values? Thank you.
Mine is "/home/$username/tmp" for both.0 -
Mine is "/home/$username/tmp" for both.
Would you mind opening a support ticket using the link in my signature, and posting the ticket number here? We'd like to take a closer look at an affected system to see if we can determine the change that resulted in this issue. Thank you.0 -
What was the fix for this issue? 0 -
@egillette - I don't see that a fix was posted for this particular issue. Since this thread is five years old, you can always start a new thread to get some assistance, or create a ticket with our team for us to take a look at a particular server. 0
Please sign in to leave a comment.
Comments
17 comments