Split: Server 500 error

This topic contains 22 replies, has 2 voices, and was last updated by  Paolo 8 years, 3 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: 

  • Author
    Posts
  • January 21, 2016 at 12:44 pm #69718

    topoffice
    Expired Member
    Post count: 51

    Hey guys;

    Since day 1 I get occasional plain 500 server errors – on both back and front end. Sometimes when loading a listing. Mostly when working with the XML sitemap generation (Yoast). I already cleared GD Booster cache, deactivated the Booster plugin etc. – to no prevail. I read all related posts here and therefore appreciate it if one of you guys checks the GD back end and server side. The site sits on a dedicated server.

    Cheers,

    Martin

    January 21, 2016 at 3:56 pm #69746

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    it would help if you could check the server error logs right after it happens. That way if we can identify the fatal error we can see what is causing it.

    Let us know,

    Thanks

    January 21, 2016 at 4:03 pm #69749

    topoffice
    Expired Member
    Post count: 51
    This reply has been marked as private.
    January 21, 2016 at 7:24 pm #69806

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    the only thing I see regarding sitemaps is a time out:

    2016/01/21 13:03:05 [error] 29873#0: *931537 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 66.249.69.127, server: autobodyshop.org, request: “GET /sitemap_index.xml HTTP/1.1”, upstream: “https://69.30.199.138:8443/sitemap_index.xml”, host: “www.autobodyshop.org”

    Please refer this to your server admin.

    Thanks

    p.s. next time, please ask him directly when you have a 500 internal server error?

    January 22, 2016 at 3:19 pm #69997

    topoffice
    Expired Member
    Post count: 51

    Hey Paolo;

    I had my server guy look into this and he reported back with:

    2016/01/22 08:39:30 [error] 30132#0: *359 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 85.132.54.30, server: autobodyshop.org, request: “GET /sitemap_index.xml HTTP/1.1”, upstream: “https://69.30.199.138:8443/sitemap_index.xml”, host: “www.autobodyshop.org”
    [Fri Jan 22 08:40:01 2016] [error] [client 85.132.54.30] WordPress database error Query execution was interrupted for query SELECT t.term_id FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id LEFT JOIN wp_term_relationships as tr ON tr.term_taxonomy_id = tt.term_taxonomy_id LEFT JOIN wp_posts as p ON p.ID = tr.object_id INNER JOIN wp_geodir_gd_place_detail as pd ON pd.post_id = p.ID WHERE tt.taxonomy IN (‘gd_placecategory’) AND p.post_status = ‘publish’ AND pd.post_locations LIKE ‘%,[virginia],[united-states]’ GROUP BY t.term_id ORDER BY COUNT(t.term_id) DESC limit 5 made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, geodir_sitemap_init, geodir_sitemap_load_sitemap_data

    Looks like a DB loop caused by the GD code!!!

    Please share this with Stiofan!

    Cheers,

    Martin

    January 27, 2016 at 5:25 pm #112524

    Paolo
    Site Admin
    Post count: 31206

    Hi Martin,

    follow up from the developers:

    Checked the server error log and it shows: “upstream timed out (110: Connection timed out) while reading response header from upstream, client: 49.213.57.122, server: autobodyshop.org, request: “GET /sitemap_index.xml HTTP/1.1”, upstream: “https://69.30.199.138:8443/sitemap_index.xml”, host: “www.autobodyshop.org””

    So it seems time out causing the issue outputing the sitemap content.

    I found some info on this time out issue here https://www.scalescale.com/tips/nginx/upstream-timed-out-110-connection-timed-out-while-reading-response-header-from-upstream/
    Also admin details provided earlier not working.

    Let us know if this helps,

    Thanks

    January 27, 2016 at 6:47 pm #112537

    topoffice
    Expired Member
    Post count: 51

    Hey Paolo;

    Thanks for the note which I shared right away with my server admin guy. His reply:

    No. Its not a nginx issue
    I was trying get directly from apache
    Its timed out
    And stopped working with mysql

    I provided 4 admin details. Which ones don’t work … do you need? 🙂

    Cheers,

    Martin

    January 27, 2016 at 9:55 pm #112616

    Paolo
    Site Admin
    Post count: 31206

    I believe he was asking for wp admin details. I’ll double check with him.

    Thanks

    January 28, 2016 at 5:58 pm #112979

    Paolo
    Site Admin
    Post count: 31206
    This reply has been marked as private.
    January 28, 2016 at 5:59 pm #112990

    Paolo
    Site Admin
    Post count: 31206

    split so that you can read private replies…

    January 28, 2016 at 6:13 pm #113033

    topoffice
    Expired Member
    Post count: 51
    This reply has been marked as private.
    February 1, 2016 at 12:45 pm #114990

    topoffice
    Expired Member
    Post count: 51

    Hey Guys;

    Any news? I already deactivated the sitemap function in Yoast and tried with google-sitemap-generator.4.0.8 . The result is the same. I think this plugin even tries to max out the 50000 listings per map that Google takes. So it’s basically worse than the server time outs I get from Yoast when breaking up the listings in pieces of 500.

    I would really appreciate if someone would address this shortly.

    Thanks,

    Martin

    February 1, 2016 at 3:25 pm #115070

    Paolo
    Site Admin
    Post count: 31206

    Message from hte developers:

    The reason is site has large data 202200+ place listings, 7 categories, 184700+ place tags and 16300+ location cities.

    So generating sitemap pages for (location + categories) and (location + tags) results in server timeout errors like “WordPress database error Query execution was interrupted for query”, “WordPress database error Lost connection to MySQL server during query” & “PHP Warning: mysql_connect(): Can’t connect to local MySQL server”.

    Because xml sitemap pages for (location + categories) and (location + tags) becomes too much number pages (ex: locations * tags AND locations * categories).
    So i have added new options under “GD -> MultiLocations -> Location Settings -> Yoast SEO XML Sitemaps Settings” to exclude location pages, (location + categories) pages & (location + tags) pages from xml sitemap.

    Options added to exclude location pages from Yoast SEO XML sitemap – CHANGED

    This changed updated at customer’s site https://www.autobodyshop.org/ and also at our test site http://ppl.directory/
    Please check here http://ppl.directory/wp-admin/admin.php?page=geodirectory&tab=managelocation_fields&subtab=geodir_location_setting

    Now its working fine when excluding (location + categories) pages and (location + tags) pages from xml sitemap. Pls see https://www.autobodyshop.org/sitemap_index.xml

    Let me know.

    Thanks

    Let us know if this is resolved now.

    February 1, 2016 at 4:36 pm #115138

    topoffice
    Expired Member
    Post count: 51

    Hey Paolo;

    Thanks for the efforts so far. 🙂

    https://www.autobodyshop.org/sitemap_index.xml still gives me a 500 server error. I have not touched/changed a thing!

    Location cities/tags/categories are highly important for me (an SEO thing with Google). I can’t drop them.
    Question: What do websites with a REAL database do? How do they create sitemaps? Google officially accepts individual site maps with up to 50000 entries/pages each. How is is possible that my setup fails with a “lame” 200K listings.

    Within Google Webmaster I already notice the negative impact of the sitemap issue. It currently considers ~60K as submitted (down from 120K last week).

    I appreciate your help. 🙂

    Martin

    February 1, 2016 at 4:43 pm #115140

    Paolo
    Site Admin
    Post count: 31206
    This reply has been marked as private.
  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 23 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket