Cronjob part locked by other process

Previous topic

General

Next topic

Author	Message
Célian VEYSSIÈRE	Friday 12 February 2010 6:49:15 am Hello, I have a problem with the Cronjob and I can not find what can be blocked. What can block ? Running cronjobs/workflow.php Cronjob part locked by other process: 15154 Running cronjobs/unpublish.php Running cronjobs/rssimport.php Cronjob part locked by other process: 13963 Running cronjobs/indexcontent.php Starting processing pending search engine modifications Done Running cronjobs/hide.php Cronjob part locked by other process: 13963 Running cronjobs/subtreeexpirycleanup.php Running cronjobs/internal_drafts_cleanup.php Cleaning up internal drafts... ï»¿Erreur de segmentation in the log : Fri Feb 12 14:50:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Cronjob part locked by other process: 28904 Fri Feb 12 15:00:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Cronjob part locked by other process: 1705 Fri Feb 12 15:10:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Cronjob part locked by other process: 5486 Fri Feb 12 15:20:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Cronjob part locked by other process: 10328 Fri Feb 12 15:30:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Cronjob part locked by other process: 15154 Fri Feb 12 15:40:01 CET 2010 Running cronjob part 'workflow' Running cronjobs/workflow.php Checking for workflow processes Status list L'événement de processus de workflow est reporté à l'exécution de la commande cron(4): 8 0 out of 8 processes was finished I don't found the reason of blocking. Thank you in advance.
Gaetano Giunta	Friday 12 February 2010 7:43:14 am The segfault in the 1st run of the cronjobs will leave some lock files pending. Subsequent cronjob runs will not do anything for 24 hours. Then they will find the leftover lock files are too old and try to delete them. You can easily delete them by hand, they are in a subdir of var/siteaccess/cache. Take care about the os users that run those cronjob; Sometimes you might run eg. the cronjobs as root, and leave a stale lock file that cannot be later removed when trying to run cronjobs as another user... Principal Consultant International Business Member of the Community Project Board

Author

Message

Célian VEYSSIÈRE

Friday 12 February 2010 6:49:15 am

Hello,

I have a problem with the Cronjob and I can not find what can be blocked.

What can block ?

Running cronjobs/workflow.php
Cronjob part locked by other process: 15154

Running cronjobs/unpublish.php

Running cronjobs/rssimport.php
Cronjob part locked by other process: 13963

Running cronjobs/indexcontent.php
Starting processing pending search engine modifications
Done

Running cronjobs/hide.php
Cronjob part locked by other process: 13963

Running cronjobs/subtreeexpirycleanup.php

Running cronjobs/internal_drafts_cleanup.php
Cleaning up internal drafts...
ï»¿Erreur de segmentation

in the log :

 Fri Feb 12 14:50:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Cronjob part locked by other process: 28904
Fri Feb 12 15:00:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Cronjob part locked by other process: 1705
Fri Feb 12 15:10:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Cronjob part locked by other process: 5486
Fri Feb 12 15:20:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Cronjob part locked by other process: 10328
Fri Feb 12 15:30:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Cronjob part locked by other process: 15154
Fri Feb 12 15:40:01 CET 2010
Running cronjob part 'workflow'
Running cronjobs/workflow.php
Checking for workflow processes
Status list
L'événement de processus de workflow est reporté à l'exécution de la commande cron(4): 8

0 out of 8 processes was finished

I don't found the reason of blocking.

Thank you in advance.

Gaetano Giunta

Friday 12 February 2010 7:43:14 am

The segfault in the 1st run of the cronjobs will leave some lock files pending.

Subsequent cronjob runs will not do anything for 24 hours. Then they will find the leftover lock files are too old and try to delete them. You can easily delete them by hand, they are in a subdir of var/siteaccess/cache.

Take care about the os users that run those cronjob; Sometimes you might run eg. the cronjobs as root, and leave a stale lock file that cannot be later removed when trying to run cronjobs as another user...

Principal Consultant International Business
Member of the Community Project Board