Search results

yum install perl-DBD-MySQL

I had the same backup issues with Plesk 17.5.3 update #17 on CentOS 7 (7.3.1611). The installation of the package "perl-DBD-MySQL" solved the problem.

Where did you insert the conversion?

Hi, mod_rewrite belongs to apache and nginx doesn't support .htaccess files. You'll have to convert it for nginx yourself or try your luck with a converter like https://winginx.com/en/htaccess.

Hm... don't know what's the problem there. I'm running MariaDB on all my servers (installed before Plesk) without any problems. Absolutely no problem with reindexing (big) magento shops. Maybe the different MySQL versions have different default settings/limits. Have you adjusted your MySQL...

The default values are on the page I mentioned above - in the text of each directive.

Event should be the best mpm - it can handle more connections than the other mpms (separate thread for keepalive connections etc.) and has some other advantages over the other mpms like smaller memory footprint etc. For example one of my configurations. Location...

I got MU#32 on all servers. Igor, are there no files downloaded for MU#31? When the autoinstaller downloads the files for the MUs, there are still no downloads for MU#31.

You can run Magento CE 1.7.x+ with PHP 5.6 without any problems.

I don't think it has been applied - when I reinstall all patches, the process finishes after update 30 - no download for update 31.

Strange - seems that update 31 is not available - trying to install it for a few days now.

I experienced this issue too for a few websites after a fresh install a few days ago - the solution was to add the line 'DirectoryIndex index.php' to the .htaccess file in the document root for each website.

Have you run 'mysql_upgrade'? Btw. - MariaDB 10.1 runs without any problems with Plesk / Magento 2.x.

Maybe this bug is affecting you (apache <v2.4.11): https://bz.apache.org/bugzilla/show_bug.cgi?id=57198 Have you upgraded apache before the problems started? Maybe you should try a newer apache-version. Have also a look if you have mod_deflate enabled - if yes, disable it for testing - it can...

Seems the problems are caused by the apache side - which apache version are you using?

Just for clarification - you are using apache worker + php-fpm to handle php-files and nginx as reverse proxy for static files, right?

Is there something interesting in the other logs? (messages / syslog etc.)

Are you sure? How is PHP being executed currently? mod_php, fcgid oder php-fpm? Apache Worker + fcgid can consume very much resources.

Sounds like you have a problem with your resources (not enough). If it is a problem with your resources, you should consider to change / optimize your setup, for example: - Switch from apache worker to event - Disable all unused apache-modules - Use the highest possible PHP-Version (Current...

Just for clarification: /etc/sw-cp-server/config ist the config file for the nginx server that serves the plesk panel /etc/nginx/nginx.conf ist the config file for the nginx server that serves the customer-vhosts