Filling logs with garbage

  • Resolved dazigster

    (@dazigster)


    1 year ago

    Every second, the following is logged, literally tens of thousands of times. The even weirder thing is that plugins (in fact all but uploads) are excluded from backups anyway! The even weirder thing is you can deactivate and reactivate Backup Migration and it will just carry on filling the log with the same 4 lines.

    [2025-05-15 11:02:00] [ERROR] There was an error before request shutdown (but it was not logged to backup/restore log)
    [2025-05-15 11:02:00] [ERROR] Error message: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead
    [2025-05-15 11:02:00] [ERROR] Error file/line: /[REDACTED]/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php|60
    [2025-05-15 11:02:00] [ERROR] Error handler: init#01|8192

    Temporarily renaming container.php breaks the log loop (and also hard breaks the site, of course), but as soon as you rename it back, it resumes (and presumably the runaway process was still running in the background anyway).

    As it is, I’ll have to uninstall this Backup plugin as it’s just filling the storage with a giant logfile (and, as noted in a separate ticket, simply doesn’t work anyway except for manual backups, for which other much more stable plugins exist)

Viewing 1 replies (of 1 total)
  • Plugin Support MixHa

    (@mixha)

    1 year ago

    Hello @dazigster ,

    Thank you for your feedback.

    The logs you’re seeing are not generated by our plugin directly, but rather originate from the Yoast SEO plugin, which appears to be incompatible with the current PHP version (8.4.7). The specific error message is related to deprecated usage in Yoast’s vendor-prefixed Symfony component.

    Our plugin does not cause these errors — what it does is intercept and mirror existing PHP errors (such as those found in error.log or debug.log) to its own log system, purely to aid in diagnosing issues related to our plugin’s functionality. This helps our support and development teams investigate when real problems occur.

    Since the errors are already present at the PHP level, our plugin is not the root cause, nor is it duplicating them unnecessarily. They would exist even without our plugin active — the only difference is that you wouldn’t see them in our log file.

    If you prefer not to see these mirrored errors in our logs, you can safely ignore them, or alternatively, address the source error within the Yoast plugin or downgrade PHP to a compatible version with Yoast plugin.

    As for the log size limit, we will apply it in the upcoming plugin version.

    Kind regards

Viewing 1 replies (of 1 total)

The topic ‘Filling logs with garbage’ is closed to new replies.

  • 1 reply
  • 2 participants
  • Last reply from: MixHa
  • Last activity: 1 year ago
  • Status: resolved