Dear SMW users,
this might not be a directly SMW related question, but maybe some of you have
experience with the job queue and job table?
In the Vienna History wiki, jobs do not get done when running runJobs.php. The
Job table shows that the jobs currently in the queue are locked: there are
Hi,
As you are running MW 1.22.* [0], you may have an interest in reading [0].
[0] https://www.wien.gv.at/wiki/index.php/Spezial:Version
[1]
https://www.mediawiki.org/wiki/Manual:Job_queue#Changes_introduced_in_MediaWiki_1.22
Cheers
On 9/24/14, Krabina Bernhard krab...@kdz.or.at wrote:
Dear
Hi,
The likelihood that it is related to SMW 1.8.0.5 is rather slim and
looking at [0] did not reveal related issues.
entries in the row job_token which results in the jobs not being done by
the script.
According to [1], job_token is a field that conveys process locks
on rows via process
Hi,
I believe the issue is the job_attempts field in the job table. I
believe each job is only attempted a certain number of times before
MediaWiki basically just gives up and ignores it. My guess is that that
column is greater than 0 for all the rows in the table; I think if you just
go into the
Hi,
column is greater than 0 for all the rows in the table; I think if you just
go into the database and call something like UPDATE job SET job_attempts =
0, they will get run again.
In case this solves the issue, I sincerely hope there is a different
way (a more standard way) to reset the
Hi,
runJobs.php will literally run forever. After the non-offending jobs are
cleared it's easy to see which are the offenders. Thus far I think all
offenders have been of type SMW::UpdateJob.
I don't think the problem is with the `SMW\UpdateJob` because it does
a simple shallow update of the
Hi,
We currently have five jobs that are stuck. All of them have 1 for
job_attempts.
One has job_cmd of refreshLinks in job namespace 10 and it is for a
template page.
The other four have job_cmd of SMW\UpdateJob in job namespace 0 and are for
standard pages. These pages do not seem to be
I have executed runJobs several times and the job_attempts remains at 1 for
those five jobs. We were thinking of doing a database backup today, then
delete those five jobs from the table, then run the SMW repair and
upgrade via the admin special page.
Even if this clears the job queue, we'd like
Hi,
I have executed runJobs several times and the job_attempts remains at 1 for
those five jobs. We were thinking of doing a database backup today, then
I'm curious about the job_attempts field as I would have expected to
see an increment for when the job (actually there has been an attempt
to
