Interesting, that’s a new one. How large is the log file? Are there any extremely long lines in that file?
The log file is 858kb and yes, there are a couple of super long lines like this:
[20-Oct-2017 08:56:03 UTC] WordPress database error Unknown table 'wp_xx_blog_accordionslider_accordions,wp_xx_blog_accordionslider_panels,wp_xx_blog_accordionslider_l' for query DROP TABLE wp_xx_blog_accordionslider_accordions, wp_xx_blog_accordionslider_panels, wp_xx_blog_accordionslider_layers made by do_action('wp_ajax_delete-plugin'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wp_ajax_delete_plugin, delete_plugins, uninstall_plugin, include('C:\inetpub\vhosts\censored-domain.com\www.censored-domain.com\blog\wp-content\plugins\accordion-slider-lite\uninstall.php'), bqw_accordion_slider_lite_delete_all_data
Otherwise the log file is full of this little beauty that seems to get trigged on every request(!):
[24-Oct-2017 18:10:20 UTC] PHP Warning: is_readable(): open_basedir restriction in effect. File(C:\inetpub\vhosts\censored-domain.com\www.censored-domain.com\blog/wp-content/plugins/C:\inetpub\vhosts\censored-domain.com\www.censored-domain.com\blog\wp-content\plugins\xml-sitemap-feed/languages/xml-sitemap-feed-en_US.mo) is not within the allowed path(s): (C:/Inetpub/vhosts//censored-domain.com\;C:\Windows\Temp\) in C:\inetpub\vhosts\censored-domain.com\www.censored-domain.com\blog\wp-includes\l10n.php on line 583
🙂
Hmm, 858 KiB is not all that much. I’ve tested the plugin with files that are over 5 MiB. The example line is around 640 characters long, which should also be quite manageable.
How are the log filters set up: is the plugin showing all log entries, or have you configured it to ignore less important stuff like PHP notices? Technically, filtering by severity is slower than just showing the last X entries.
Still, it shouldn’t take anywhere close to 60 seconds. Could it be that the server has an unusually slow disk or some other hardware issue?
Damn, you’re right.
It was a shitty sever performance. It was a hardware issue on the server.
