I'm getting the above message on every cron run... I don't know why this won't work, but search_cron won't complete when I use curl or wget from crontab (or from the command line). However, if I am logged into the website and go to the Elysia Cron status page, then click the 'run' link next to search_cron, it runs without a hitch. It's not a timeout issue, because I have set timeout to 240 seconds (more than enough to complete search_cron a hundred times or so...).

Do you know anything I could do to fix this? I've switched search cron to do 10 nodes at a time, and set minimum word length to 50 characters (I use apachesolr, so I don't even need an index created).

Comments

gotheric’s picture

gotheric commented
Status: Active » Fixed

That message is shown when cron chain in interrupted before its natural end. This is usually for two reasons:
- timeout: the process has reached the "time limit" for the execution (defined in settings), and has been stopped
- the job as invoked a "die" or an "exit" to force the end of the execution (which is WRONG for a cron job).

I don't think the "search_cron" could do a die or an exit (it's a core hook, so i suppose is well coded ^_^), so i think your problem is about timeout.

However you can think about putting search_cron in a separate channel, so it will run alone (no other jobs can take execution time and he can't block the execution of jobs after it).

Status: Fixed » Closed (fixed)

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

tezalsec’s picture

tezalsec commented
Status: Closed (fixed) » Active

Hi,

I get the same error "Unexpected termination of cron job search_cron manually started, aborted." when running the search_cron, but it isn't for sure caused by the abovementioned reasons.

How strange it may sound. it looks like the interruption it is caused by the indexing process not indexing some new pages of mine, but actually executing/following them, and with that ending the process of indexing, ending up without showing any errors (only in the watchdog), and just displaying one of these new pages (content type page). Afterwards looking then in de db I see these pages have not been indexed in the table search_index.

I have never seen this behaviour before, could anyone explain this??

Cheers

tezalsec’s picture

tezalsec commented
Title: Unexpected temination of cron context search, aborted. » Unexpected termination of cron search, aborted.
tezalsec’s picture

tezalsec commented

Never mind, I figured out what was causing it. I don´t know if I completely understand and agree with the infrastructure of the search indexing being able to do this though.

I misused page nodes to instantly execute custom module functions and reroute automatically to another page. This apparently confused the indexing mechanism. I should have just used menu_callback to create links that execute functions by clicking them and set up the rerouting within the function itself.

Cheers.

tezalsec’s picture

tezalsec commented
Status: Active » Closed (fixed)