Support » Plugin: Error Log Monitor » Plugin causing PHP error

  • Resolved harryfear



    Any ideas how to solve this:

    [Oct 24, 13:56:27] PHP Fatal error: Maximum execution time of 60 seconds exceeded in \wp-content\plugins\error-log-monitor\Elm\ReverseLineIterator.php on line 93


    Ironically, only know of this because of the amazing plugin itself. The above error message is delivered by the plugin’s email alert:

    New PHP errors have been logged on
    Here are the last 1 entries from C:\inetpub\vhosts\\\error-log-folder\php-errors.log:
    • This topic was modified 3 years, 2 months ago by harryfear.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Janis Elsts


    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\\\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\\\blog/wp-content/plugins/C:\inetpub\vhosts\\\blog\wp-content\plugins\xml-sitemap-feed/languages/ is not within the allowed path(s): (C:/Inetpub/vhosts//\;C:\Windows\Temp\) in C:\inetpub\vhosts\\\blog\wp-includes\l10n.php on line 583


    Plugin Author Janis Elsts


    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.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin causing PHP error’ is closed to new replies.