I'm a trying to get Drupal to run a new VPS server. Everything runs well except the sitemap and redirecting after a manual cron run. Does anybody know what php.ini or apache configuration might cause the xml sitemap to not be called? It works when the php handler is dso, but that causes the file permissions to mess up. So I have to run suphp. Then it doesn't allow the sitemap or cron redirect to work. It might have something to do with drupal_goto(). I don't know.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Please explain what you mean by redirecting after a manual cron run.

Adam S’s picture

Adam S commented

I started opening files to see what is going on searching for clues. Here is what I have found so far.

I click on the link in the admin/report/status menu that links to http://example.com/admin/report/status/run-cron.

I searched that database in the menu_router table for admin/report/status/run-cron. It loads loads the file system.admin.inc and calls the function system_run_cron() which in turn calls the function drupal_goto(admin/system/status).

Cron actually runs successfully. Something happens with the drupal_goto(admin/system/status) function. It does not redirect me to http://example.com/admin/system/status . Instead it throws a page not found error.

The other place that I get the problem with a page not found error is when I use the http://example.com/sitemap.xml .

I know that is probably is not the right place to be asking the support question, it's a server configuration problem, but someone might know based on this information what's going on.

Adam S’s picture

Adam S commented
Status: Active » Closed (fixed)

I just rebuilt the server and migrated the site again. Cron didn't work and neither did xmlsitemap on the first go. I thought it was interesting that it said cron ran successfully after I tried to view the sitemap then it wrote 'page not found.' So I tried again. This time I got a 500 internal error trying to view the sitemap. I tried again and it works. Weird. So, this is not a sitemap issue. I'm going to close it.

Thanks for reading this anyway.

jenlampton’s picture

jenlampton
she / her
commented
Title: Migrated to new VPS server, XML sitemap does not work. » Migrated to new VPS server, XML sitemap throws 500 error
Status: Closed (fixed) » Active

I'm having the same issue on a Linux VPS. What did you do to solve the problem?
Jen

Adam S’s picture

Adam S commented

I really don't remember the problem. However, that period must have been the worst three weeks in my life. We eventually moved to hotdrupal.com .

jenlampton’s picture

jenlampton
she / her
commented

Hah, I've been with Holistic Solutions (hotdrupal.com) for some time, and I'm experiencing this problem. I did however find this post: http://drupal.org/node/485432 which suggests upgrading XMLsitemap to the 2.x branch for performance reasons. I suspect I was running out of memory in PHP and that's why I'm getting the 404.

I've upped my memory to 128M and upgraded the module. (The upgrade process was not smooth, I generated tons of SQL errors by running update.php, and in the end decided to disable and uninstall the 1.x branch and install the 2.x branch fresh)

Jen

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Yeah its most likely a memory issue. Sometimes PHP has weird ways of saying its out of memory.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed

If you're running into a memory problem during cron, your best bet is to move up to the 2.x version. There's not much we can do here.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.