out of sync after codebase deployment?

  • Resolved max

    (@maximledoux)


    6 years, 4 months ago

    Had an issue today. I updated the Yoast SEO plugin (yes, different plugin, but bear with me, it’s not actually about Yoast), tested it on our staging site, worked fine, no conflicts, then I deployed to our production site. The site wouldn’t load, kept on timing out. I checked the logs, saw immediately references to

    PHP Fatal error: require(): Failed opening required '/public_html/wp-content/plugins/wordpress-seo/vendor/composer/ClassLoader52.php' (include_path='.:/usr/share/php') in /public_html/wp-content/plugins/wordpress-seo/vendor/composer/autoload_real_52.php on line 10

    I ended up deleting the Yoast plugin folder from the command line and the site loaded up again. I then looked further back into the logs and found:

    PHP Warning: Redis::connect(): connect() failed: Connection refused in /public_html/wp-content/object-cache.php on line 436

    So bear in mind that Yoast SEO works fine on our staging site (fresh — today — copy of production site’s database). SO it’s really not a problem with Yoast, that just happened to be the particular update I was deploying.

    Is it possible that Redis was referencing plugin files that no longer existed? I’m somewhat fuzzy what Redis::connect(): connect() means.

    But if so, what’s the appropriate way to deal with this? I use deployhq.com to deploy our codebase, and I can run SSH commands before and after the deployment.

    Would this be a good idea:

    wp redis stop
    Run Deployment
    wp redis start
    ?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter max

    (@maximledoux)

    My real question is whether stopping and starting redis on a somewhat regular basis is a good idea.

    Thread Starter max

    (@maximledoux)

    I mean wp redis disable and wp redis enable!

    Plugin Author Daniel Bachhuber

    (@danielbachhuber)

    Hey @maximledoux,

    Sorry to hear you’re having difficulty. It’s hard to know what the specific issue might be without access to your environment to debug.

    Generally, a PHP Warning: Redis::connect(): connect() failed error probably means that all Redis connections have been exhausted. This would be unrelated to the deployment process — only something you’ve noticed at this point in time.

    The fatal error itself appears related to your deployment process (unrelated to WP Redis).

    As to starting and stopping Redis, that shouldn’t be needed. It’s better to fix whatever issues you’re having with Redis.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘out of sync after codebase deployment?’ is closed to new replies.