Forwarded to devs Minor: Configuration Trouble Shooter shows false positive alerts during configuration change

[Bitpalast]

TITLE:

Minor: Configuration Trouble Shooter shows false positive alerts during configuration change​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Onyx 17.07, CentOS 7.3, 64 bit​

PROBLEM DESCRIPTION:

When the hosting settings of a domain on a slow system or a system with many domains are being changed from for example "web space" to "redirect", the web configuration trouble shooter shows errors for the corresponding hosting configuration files. It is possible that a configuration error message like the one below is mailed although shortly later the configuration is correct on disk.

Unable to generate the web server configuration file on the host <hostname> because of the following errors:

Template_Exception: nginx: [emerg] open() "/etc/nginx/plesk.conf.d/vhosts/<domain>.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/zz010_psa_nginx.conf:7
nginx: configuration file /etc/nginx/nginx.conf test failed

file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0

Please resolve the errors in web server configuration templates and generate the file again.

STEPS TO REPRODUCE:

Test on a server that takes a while to update hosting settings, for example either on a slow server or on one that has many PHP-FPM children and many domains, so that restarting anything takes a few seconds.

Change the hosting settings of a domain from "web space" to "redirect". Then go into configuration trouble shooter.​

ACTUAL RESULT:

Configuration trouble shooter will claim missing/empty or false configuration files for domainForwarding.php or nginxDomainVhost.php for the related domain.​

EXPECTED RESULT:

Configuration trouble shooter should not display errors on domains that are currently processing a configuration change, because it is irrelevant if accidentally in that very second a user opens the extension a domain configuration file is being rebuilt and not available for that reason.​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

From developer:

I tried to reproduce the issue according to the provided steps but did not have a similar error message.

Usually I see that some configs are in progress of regeneration and they are marked with red icon (see screenshot).

Under the hoods Configuration Troubleshooter performs two actions:

• Check psa.Configurations table
• Check apache and nginx services status (no testing of config files)

Both actions are not able to affect configs content.
But the error "[emerg] open() "/etc/nginx/plesk.conf.d/vhosts/<domain>.conf failed (2: No such file or directory)" means either some interruption of configs generation process or testing of config files in unexpected moment.

Could you please increase verbosity in panel.ini

[log]
filter.priority = 7
show.util_exec = 1
show.util_exec_io = 1

And send the log file.

 

[Bitpalast]

Anonymous log file attached. It contains three transactions: changing a domain from "redirect" to "webspace", creating a new domain and changing one from "webspace" to "redirect". That all works fine. The problem is that during the transaction, Configuration Trouble Shooter shows these domains with the red exclamation mark. It should exclude domains that are currently be reconfigured from the list or it should at least show that they are being reconfigured and hide the "reconfigure" icon in the column on the right.

I was unable to reproduce the error message that is mailed, because this occurs rarely. There is a slight possibility that that error message mail is linked to the issued described in Apache service restarts twice while applying changes in Plesk . We have only recently applied the hot fix from that article.

But the basic (and very minor) issue that Configuration Trouble Shooter is not excluding domains from its test that are still "processing" remains.

 

[IgorG]

Peter, thank you for this additional information. The issue is created as PPPM-6752

 

[IgorG]

Fixed:

Change Log for Plesk Obsidian

Find out about changes, additions and updates to Plesk Obsidian on an iteration to iteration basis.

docs.plesk.com

Webserver Configuration Troubleshooter no longer shows that some configs are broken when they are actually not after reconfiguration (for example, after domain’s hosting settings were changed but these changes did not propagate yet). (PPPM-6752)