Havin 503 and 504 error with this plugin

  • Im facing this 503 and 504 (specially) issue when I install this plugin to my website…It Works for the first minute and then…gateway timeout comes up. I contacted my server that said this plugin is messing with Apache server and I was forced to shut it down. I installed Varnish HTTP Cache, but still this issue remains…Any idea what to be done to avoid this issue?

    my website is https://www.blahcultural.com

    I really want to keep this plugin on my website…I tried to even reduce the ammount of related posts displayed but still issue remains…I selected Cache output and with and without varnish installed…still remained the issue…and at the bottom of config page says the following:
    ALTER TABLE wp_n5jwj9_posts DROP INDEX crp_related;
    ALTER TABLE wp_n5jwj9_posts DROP INDEX crp_related_title;
    ALTER TABLE wp_n5jwj9_posts DROP INDEX crp_related_content;
    ALTER TABLE wp_n5jwj9_posts ADD FULLTEXT crp_related (post_title, post_content);
    ALTER TABLE wp_n5jwj9_posts ADD FULLTEXT crp_related_title (post_title);
    ALTER TABLE wp_n5jwj9_posts ADD FULLTEXT crp_related_content (post_content);
    Forcing me to recreate table too

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter witcherybr2004

    (@witcherybr2004)

    I

    Plugin Author Ajay

    (@ajay)

    May I ask which host this is and what is your server configuration?

    The only issue the plugin has is when activating if you have a very big site. Outside of this it’s usually fine especially with the plugin cache activated.

    Thread Starter witcherybr2004

    (@witcherybr2004)

    https://www.blahcultural.com

    server: DREAMHOST.COM

    I have a DREAMPRESS signature

    Thread Starter witcherybr2004

    (@witcherybr2004)

    I asked my server about my server configuration….it goes below:

    https://www.blahcultural.com
    server: DREAMHOST.COM
    I have a DREAMPRESS signature

    Config Specs:

    Storage 68GB
    Memory is autoscaled so the server will autoscale the RAM to what your site needs
    Currently using 3GB of RAM
    Server CPU quad core processors

    The apache service version is 2.2.22
    current php is 5.6 but they alsoffer 7.Each DreamPress instance is made up of two VPS instances: one web, and one MySQL.

    The two VPS instances:

    are provisioned automatically
    are configured as a pair
    are hosted on isolated clusters of hardware so other sites won’t interfere with their stability or performance. All of them are hosted in the Virginia datacenter as of June 2013.
    disallow root and sudo access
    auto-scale RAM (memory) dynamically (customers cannot modify the RAM allocation)
    In addition to the standard VPS setup, DreamHost added Varnish as a caching layer, which:

    is set up automatically for the DreamPress customer
    listens on port 80
    responds to web requests as a proxy in front of the Apache and PHP WordPress stack
    is extremely efficient at caching content
    allows this set up to scale to very high levels of traffic
    comes with a Unique IP

    Service restrictions
    DreamPress is a managed service, which means DreamHost has restricted certain actions that users can take that would irreparably break their WordPress site.

    DreamPress is a one-site service in that a single plan covers a single domain with a single WordPress installation. However, users can have multiple DreamPress instances for multiple sites, and they can mix and match it with shared, VPS, and dedicated hosting as well.

    Current restrictions
    Unable to configure or modify the VPS instances.
    Unable to manually set memory on the VPS. The memory is configured and scales automatically.
    No admin users or root SSH keys on the VPS instances.
    Unable to add or remove users or domains on the VPS. One SFTP (optional SSH) user and the domain you choose will be configured automatically.
    Unable to add or remove databases or hostnames on the MySQL VPS. The database and hostname will be created automatically for WordPress.
    Unable to merge databases to or from the MySQL VPS
    Unable to delete the web or MySQL VPS instances independently. To delete the VPS instances, go to the (Panel > ‘DreamPress’ > ‘Dashboard’) page, click Change Plan, and then click the Downgrade or Delete buttons. The ‘Downgrade’ option requires an active service to migrate the data to (either shared or VPS, which can be added).
    Unable to add Wildcard DNS as DreamPress does not utilize a standard DreamHost VPS.

    Plugin Author Ajay

    (@ajay)

    Hi, I think it’s an issue because of DreamPress. If I’m not mistaken you’re using their managed hosting service and my plugin is usually not allowed with some of these managed hosting due to the need for FULLTEXT indices.

    One thing worth trying is to use the add-in plugin CRP Taxonomy and disable to the full text.

    Also, make sure that the cache is on in the plugin settings page.

    Lastly, it’s a good idea to enable PHP7 as it’s significantly faster than 5.6, irrespective of using my plugin.

    As always, backup before you make changes

    • This reply was modified 7 years, 4 months ago by Ajay.
    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    The 503 error is likely a process/resources issue.

    The database cache is handled by Memcached (there’s a file called object-cache.php in your wp-content folder), and essentially caches DB calls to memory. Reading this error, I think that’s possibly what’s busted.

    The only issue the plugin has is when activating if you have a very big site.

    How big is ‘big’ and what does it do that causes your plugin to have problems on large sites? Is it trying to scan _all_ posts to generate the lists?

    Plugin Author Ajay

    (@ajay)

    @ipstenu, the issue is that the plugin creates a FULLTEXT index on post_content and post_title (individually and together) when activated. If a user has several thousand posts, this can take a long period of time and in some case I’ve noticed a timeout.
    I’ve tested this up to 4000-5000 posts with dummy data and it’s been fine, but of course determined by server specification.
    Have yet to figure out a workaround for this.

    Lists are only generated when a post is visited and then are cached in a meta key

    • This reply was modified 7 years, 4 months ago by Ajay.
    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Ouch. Yeah okay so that’s going to be a Memcached issue (not Varnish), since the way that works is to try and store queries in RAM to make ’em faster. You’re overloading that.

    You could TEST by renaming the object-cache.php file to object-cache.off and see if that magically lets it run?

    Plugin Author Ajay

    (@ajay)

    Are queries run through $wpdb automatically cached via the object-cache? I wonder if there is a way to bypass this when I create the index.

    e.g. I run $wpdb->query( "ALTER TABLE {$wpdb->posts} ADD FULLTEXT crp_related (post_title, post_content);" );

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Yes the queries would be automatically cached :/ Or try to. If you rename the object cache file I mentioned, that will prevent it from caching, but … It might be better to break that query apart into chunks of 100 posts, and even then ONLY the posts that are posts and not auto-drafts?

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Havin 503 and 504 error with this plugin’ is closed to new replies.