Project:Chinese Word Splitter(中文分词)
Version:5.x-1.0
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I'm having a very strange problem with cron. It appears that somehow the search_index got interrupted when trying to index a node (usually the 7th or 8th node to be indexed). Mysteriously, a 'page not found' warning message is logged into watchdog. Here is the details of the log message.

Type page not found
Date Monday, June 9, 2008 - 15:07
User yan
Location http://www.hcscommunity.com/admin/logs/status/run-cron
Referrer http://www.hcscommunity.com/admin/logs/status
Message cgierrpage.html

I have no idea where the cgierrpage.html came from.

Any help ie greated appreciated.

Thanks,
Yan

Comments

#1

Priority:critical» normal

#2

Try running cron using the link in the admin interface (status report page).

#3

Status:active» postponed (maintainer needs more info)

#4

I chased it further down. The problem seems to be with CSplitter module's search preprocessing function (csplitter_search_preprocess). After I disabled this module, the error went away. But I still can't see where 'cgierrpage.html' came from...

#5

Project:Drupal core» Chinese Word Splitter(中文分词)
Version:5.7» 5.x-1.0
Component:search.module» Code
Status:postponed (maintainer needs more info)» active

Maybe PHP is running as CGI and the error handling isn't quite working... PHP tries to call up that nonexistent page or something.

Often the problem is a contrib module eating up too much memory during search indexing. Worth looking in the server/Apache error log.

Moving to CSplitter's issue queue, and making a guess as to the appropriate version &c.

#6

I found this page by searching 'cgierrpage.html'. I see this page not found in my log too after failed CRON job. If I run cron manually (admin/reports/status/run-cron) it runs, but then gives an error like the above (page not found 'cgierrpage.html' then 'Attempting to re-run cron while it is already running'. If I either run the file cron.php I see that it ran successfully. (The new feeds load) I don't use the Chinese word splitter module though, so I suppose it isn't an error directly in that module...

Best,

Busman

#7

I suggest you try to find the original cause of the error - look in your server error logs, or ask your host for help.

> I suppose it isn't an error directly in that module...
Indeed!