• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

/var/www/vhosts/system/<subdomainname>/etc/php.ini not updated or newly generated

B_P

Regular Pleskian
Dear all,

For one of the subdomains (sub.domain.com) of my own webspace, I changed some custom PHP settings as mentioned at http://download1.parallels.com/Ples...inistrator-guide/index.htm?fileName=69696.htm.
Actually, I added the additional directive "always_populate_raw_post_data=-1".
The subdomain is running PHP as FastCGI application (PHP5.6.6), on Apache 2.2 (Ubuntu 12.04 LTS).

Normally, I would assume that when saving these settings, Plesk would automatically update the corresponding PHP ini file at /var/www/vhosts/system/sub.domain.com/etc/php.ini. However, the php.ini file is neither modified, nor touched, or regenerated.

Thus, I tried to reconfigure the whole webserver configuration files by running /usr/local/psa/admin/sbin/httpdmng --reconfigure-all. But even then, there is no update for this file. Looking at the modification date of other config files of this domain (e.g., /var/www/vhosts/system/sub.domain.com/conf/httpd.conf) I can see that the configuration in genereral has been updated but the specific php.ini file for this domain has not.

If I rename /var/www/vhosts/system/sub.domain.com/etc/php.ini and re-run httpdmng, no new php.ini is generated. For other subdomains, I can see that the php.ini file has been updated.

Does anybody have an idea what is wrong with this configuration update?
 
Hi B_P,

if you use the command "/usr/local/psa/bin/php_settings -h", you will see, that this command has two options - the "-h" ( or "--help" string for the help display and the "-u" ( or "--update-all" ) string to "Update per-domain PHP settings of all domains in accordance with the server-wide php.ini file." ( server-wide php.ini - modifications can now be done with Plesk 12.5 over your Plesk Control Panel for each installed PHP - version at: Home > Tools & Settings > PHP-Settings > YOUR_DESIRED_PHP_VERSION - - - tab: php.ini ).


Depending to your domain - specific webserver settings, your domain - specific PHP - settings will be either written to your domain - specific PHP-FPM - configuration file for that domain/subdomain ( located at "/etc/php5/fpm/pool.d/sub.domain.com.conf" ( location is for Debain/Ubuntu - based systems ), or... if you don't use PHP-FPM, then your domain - specific PHP.ini at "/var/www/vhosts/system/sub.domain.com/etc/php.ini" will be updated.

If there was no change at all, when you modified your domain - specific PHP - settings over the Plesk Control Panel at "Home > Domains > sub.domain.com > PHP-Settings", please consider to switch on the "debug - log - level" for your Plesk Control Panel


... so that investigations at your Plesk Control Panel - error-log ( /usr/local/psa/admin/logs/panel.log ) are easier.
 
  • Like
Reactions: B_P
Hi B_P,

if you use the command "/usr/local/psa/bin/php_settings -h", you will see, that this command has two options - the "-h" ( or "--help" string for the help display and the "-u" ( or "--update-all" ) string to "Update per-domain PHP settings of all domains in accordance with the server-wide php.ini file." ( server-wide php.ini - modifications can now be done with Plesk 12.5 over your Plesk Control Panel for each installed PHP - version at: Home > Tools & Settings > PHP-Settings > YOUR_DESIRED_PHP_VERSION - - - tab: php.ini ).


Depending to your domain - specific webserver settings, your domain - specific PHP - settings will be either written to your domain - specific PHP-FPM - configuration file for that domain/subdomain ( located at "/etc/php5/fpm/pool.d/sub.domain.com.conf" ( location is for Debain/Ubuntu - based systems ), or... if you don't use PHP-FPM, then your domain - specific PHP.ini at "/var/www/vhosts/system/sub.domain.com/etc/php.ini" will be updated.

If there was no change at all, when you modified your domain - specific PHP - settings over the Plesk Control Panel at "Home > Domains > sub.domain.com > PHP-Settings", please consider to switch on the "debug - log - level" for your Plesk Control Panel


... so that investigations at your Plesk Control Panel - error-log ( /usr/local/psa/admin/logs/panel.log ) are easier.

Hi UFHH01,

your hint to enable debugging helped to find the issue I guess. So what I found is that Plesk assumed my server to use PHP5-FPM even though it did not. When I investigated this issue, I found the following details:
- nginx was not running, but php5-FPM was enabled and running
- The web hosting settings of the domain showed clearly that FastCGI should be used
- Since nginx was not running, the web server settings also did not show the option "process php by nginx". However, I assume that this box must have been checked for testing at some time before. I guess that it is hidden when nginx is not running but that the setting is still active in the background. Thus, in combination with php5-fpm running, I guess that Plesk got partly confused that the subdomain should use PHP5-FPM even though it was not available.
 
Back
Top