-
Hi,
I’m getting 500 response on my sitemap link. https://bitmoneytalk.com/post-sitemap1.xml
Sometimes, critical error.Check the attached image
I have provided my details.
Thank you for help me.
-
Hello,
I have just tried it but I was able to navigate through all your sitemaps without any problem. Could you give us more details about how this is happening to you so we can try to replicate it? Is it random or does it happens always to you?
Looking forward to help you.
When I make a new post, and then I visit the first post sitemap, I will get that error.
But when I try to reload and reload the page, it will work fine without errors.
So what I did is that I have to visit the first post sitemap too often if there are new posts.
Hi,
It sounds like a hosting related issue.
It seems that creating a new post and then the subsequent clearing of the cache is causing the issue. Please talk to your web hosting provider and ask them to take a look at this. They should be able to check the error log and derive a solution.
Let us know how it goes.
Hi,
I have two separate server. one for the database and one for the files. I have a dedicated server for the files and a cloud server for the database. I have full root access to all my servers. Could you please tell me what exactly is the issue? I have tried to use the sitemap of jetpack and I don’t have any issue with it.
So I think it’s not a hosting issue but I think it’s a plugin issue.
I hope you can help me fix this.
I am using an external cron(easy cron) and disable the wordpress cron. Does it affect that? or there is no connection in any way?
Hello,
Thank you for contacting Rank Math and sorry for any inconvenience that might have been caused due to that.
I don’t think that this related to the CRON since the sitemap is reporting an error 500. Could you please check the server error logs for any details about this?
Looking forward to helping you. Thank you.
I’m not sure if this is the log you are looking for.
[03-May-2020 06:25:02] NOTICE: error log file re-opened
[04-May-2020 07:44:27] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[04-May-2020 09:54:23] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[04-May-2020 12:39:04] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[04-May-2020 13:47:29] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[04-May-2020 14:19:17] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[04-May-2020 22:56:17] WARNING: [pool bitmoneytalk.com] child 8490, script ‘//home/admin/web/bitmoneytalk.com/public_html/wp-admin/admin-ajax.php’ (request: “POST /wp-admin/admin-ajax.php”) execution timed out (35.975143 sec), terminating
[04-May-2020 22:56:17] WARNING: [pool bitmoneytalk.com] child 8490 exited on signal 15 (SIGTERM) after 172.433711 seconds from start
[04-May-2020 22:56:17] NOTICE: [pool bitmoneytalk.com] child 9126 started
[04-May-2020 23:54:27] WARNING: [pool bitmoneytalk.com] child 18107, script ‘//home/admin/web/bitmoneytalk.com/public_html/wp-admin/admin-ajax.php’ (request: “POST /wp-admin/admin-ajax.php?action=rocket_database_optimization&nonce=ec6632072e”) execution timed out (35.031766 sec), terminating
[04-May-2020 23:54:27] WARNING: [pool bitmoneytalk.com] child 18107 exited on signal 15 (SIGTERM) after 618.935757 seconds from start
[04-May-2020 23:54:27] NOTICE: [pool bitmoneytalk.com] child 19779 started
[05-May-2020 00:06:53] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 02:59:17] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 06:31:10] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 11:15:18] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 11:26:09] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 13:36:20] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 13:57:17] NOTICE: Terminating …
[05-May-2020 13:57:17] NOTICE: exiting, bye-bye!
[05-May-2020 13:57:17] NOTICE: fpm is running, pid 4627
[05-May-2020 13:57:17] NOTICE: ready to handle connections
[05-May-2020 13:57:17] NOTICE: systemd monitor interval set to 10000ms
[05-May-2020 14:09:29] WARNING: [pool bitmoneytalk.com] server reached max_children setting (16), consider raising it
[05-May-2020 14:36:08] NOTICE: Terminating …
[05-May-2020 14:36:08] NOTICE: exiting, bye-bye!
[05-May-2020 14:38:58] NOTICE: fpm is running, pid 668
[05-May-2020 14:38:58] NOTICE: ready to handle connections
[05-May-2020 14:38:58] NOTICE: systemd monitor interval set to 10000msAnd this one is the syslog error
May 5 14:45:01 bitmoneytalk CRON[3556]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 5 14:45:01 bitmoneytalk CRON[3557]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
May 5 14:45:01 bitmoneytalk CRON[3559]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue letsencrypt)
May 5 14:45:01 bitmoneytalk CRON[3558]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup)
May 5 14:47:14 bitmoneytalk systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 5 14:48:29 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
May 5 14:48:29 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
May 5 14:48:29 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
May 5 14:48:29 bitmoneytalk systemd[1]: Started nginx – high performance web server.
May 5 14:48:29 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
May 5 14:48:30 bitmoneytalk systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 5 14:48:30 bitmoneytalk apachectl[4996]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
May 5 14:48:30 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
May 5 14:48:32 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
May 5 14:48:32 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
May 5 14:48:32 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
May 5 14:48:32 bitmoneytalk systemd[1]: Started nginx – high performance web server.
May 5 14:48:32 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
May 5 14:48:33 bitmoneytalk apachectl[5175]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
May 5 14:48:33 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
May 5 14:48:38 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
May 5 14:48:38 bitmoneytalk apachectl[5509]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
May 5 14:48:38 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
May 5 14:48:38 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
May 5 14:48:38 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
May 5 14:48:38 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
May 5 14:48:38 bitmoneytalk systemd[1]: Started nginx – high performance web server.
May 5 14:48:39 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
May 5 14:48:39 bitmoneytalk apachectl[5687]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
May 5 14:48:39 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
May 5 14:48:39 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
May 5 14:48:39 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
May 5 14:48:39 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
May 5 14:48:39 bitmoneytalk systemd[1]: Started nginx – high performance web server.
May 5 14:48:39 bitmoneytalk systemd[1]: Reloading The Apache HTTP Server.
May 5 14:48:39 bitmoneytalk apachectl[5782]: AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using bitmoneytalk.com. Set the ‘ServerName’ directive globally to suppress this message
May 5 14:48:39 bitmoneytalk systemd[1]: Reloaded The Apache HTTP Server.
May 5 14:48:39 bitmoneytalk systemd[1]: Stopping nginx – high performance web server…
May 5 14:48:39 bitmoneytalk systemd[1]: Stopped nginx – high performance web server.
May 5 14:48:39 bitmoneytalk systemd[1]: Starting nginx – high performance web server…
May 5 14:48:39 bitmoneytalk systemd[1]: Started nginx – high performance web server.
May 5 14:50:01 bitmoneytalk CRON[6317]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue letsencrypt)
May 5 14:50:01 bitmoneytalk CRON[6319]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-rrd)
May 5 14:50:01 bitmoneytalk CRON[6318]: (admin) CMD (sudo /usr/local/vesta/bin/v-update-sys-queue backup)
May 5 14:50:42 bitmoneytalk systemd[1]: Started Session 17 of user root.
May 5 14:51:03 bitmoneytalk systemd[1]: Started Session 18 of user root.Hi there,
Thanks for the follow up.
You need to debug the number of allowed hp-fpm processes on your server since this seems to be frequently terminating and restarting Nginx.
I’ve tried to reduce the number of links on the sitemap but this also seem to cause your site to enter debug mode.I am passing this on to our dev team for closer investigation and we will be getting back to you in a short while.
Thank you.
Thank you.
I need to solve this as soon as possible because it’s hurting my SEO now. When I check some keywords I am now on the 2nd page of the search results which before is on the first page. 🙁 🙁 🙁
Hello,
I am afraid none of the issues you have highlighted are related to Rank Math so it is not something we can fix.
The error contains the solution:
Got error ‘PHP message: PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini.
You have to increase your input vars limit.
‘PHP message: PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /home/admin/web/bitmoneytalk.com/public_html/wp-content/plugins/wordfence/waf/bootstrap.php on line 283’, referer:
Seems like something to do with WordFence.
If you determine some issue is happening only because of Rank Math (the error goes away when Rank Math is disabled), let us know so we can help.
For the server related issue, we would recommend talking to your web host.
Thank you.
I am currently migrating my website to another host. I will let you know if I still get the error. Thank you.
I HAVE DEACTIVATED YOUR SITEMAP and USING THE GOOGLE XML SITEMAP with no errors.
So basically, the problem is not my hosting, not other plugin I use. Rankmath is the culprit here.
This is my new sitemap
https://bitmoneytalk.com/sitemap.xmlI hope you can fix your sitemap soon.
Hello,
Thank you for contacting Rank Math today and for sharing these findings.
We will be digging deeper into this issue and reach out should we seek some help from your end.
Looking forward to helping you. Thank you.
Ok, I hope you can fix this issue.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
The ticket ‘Sitemap Error’ is closed to new replies.