Greetings,
quick intro: I have been a mediawiki user for a long time (wikipedia and within companies) but I only had a couple of stints at administering one. I am in the process of setting one up for my neighborhood - or about 65 families.
It pretty much all works but as my neighbors includes anything from very hightech people to very lowtech grandpas I have to put extra-care in making sure there are no counter-intuitive things happening.
One of the counter-intuitive things that -is- happening is that when I create a new page from a pre-existing redlink the link does not become blue until I use the /purge action in the URL. I checked with showJobs.php and the job to update the page's cache is there. Somehow however, the jobs do not get triggered. I.e. as $wgJobRunRate is set to the default (1), every http request should take one job off the queue, right? But I'm not seeing this. It seems like the queue just gets longer.
I'm wondering, is this perhaps something that has to do with short urls? (they are otherwise functional) Or anything else in my .htaccess? It just seems like mediawiki doesn't see some page reloads or some newly created pages as enough to trigger the jobs queue to move forward.
Thoughts?
Kind regards,
Manu
Two Yeah things might be happening.
Try opening the page with the red link in a private/incognito mode tab to check if it is your browser caching or the server.
second try running runjobs.php and ensuring that its just not a queue issue
On Wed, Jun 8, 2016 at 3:28 PM, Emanuele D'Arrigo manu3d@gmail.com wrote:
Greetings,
quick intro: I have been a mediawiki user for a long time (wikipedia and within companies) but I only had a couple of stints at administering one. I am in the process of setting one up for my neighborhood - or about 65 families.
It pretty much all works but as my neighbors includes anything from very hightech people to very lowtech grandpas I have to put extra-care in making sure there are no counter-intuitive things happening.
One of the counter-intuitive things that -is- happening is that when I create a new page from a pre-existing redlink the link does not become blue until I use the /purge action in the URL. I checked with showJobs.php and the job to update the page's cache is there. Somehow however, the jobs do not get triggered. I.e. as $wgJobRunRate is set to the default (1), every http request should take one job off the queue, right? But I'm not seeing this. It seems like the queue just gets longer.
I'm wondering, is this perhaps something that has to do with short urls? (they are otherwise functional) Or anything else in my .htaccess? It just seems like mediawiki doesn't see some page reloads or some newly created pages as enough to trigger the jobs queue to move forward.
Thoughts?
Kind regards,
Manu _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Dear Nick,
apologies for my incredibly late reply, it is very ungracious of me.
Running runjobs correctly updates the links and turns them into blue. I have not tried with the browser in incognito yet because meanwhile I disabled the Mediawiki-based caching, seemingly solving the problem. So I'm tempted to say it was a server-side issue. I'm hoping that the 150 or so occasional users of the wiki won't load the server to the point that caching will be necessary. Still, I am puzzled as to why the job queue continued to grow no matter the http requests from my browser and the $wgJobRunRate set to 1. Perhaps I'm not understanding how the job queue works.
Again, apologies for the late reply and thank you for your help!
Kind regards,
Manu
On 8 June 2016 at 21:52, John phoenixoverride@gmail.com wrote:
Two Yeah things might be happening.
Try opening the page with the red link in a private/incognito mode tab to check if it is your browser caching or the server.
second try running runjobs.php and ensuring that its just not a queue issue
On Wed, Jun 8, 2016 at 3:28 PM, Emanuele D'Arrigo manu3d@gmail.com wrote:
Greetings,
quick intro: I have been a mediawiki user for a long time (wikipedia and within companies) but I only had a couple of stints at administering
one. I
am in the process of setting one up for my neighborhood - or about 65 families.
It pretty much all works but as my neighbors includes anything from very hightech people to very lowtech grandpas I have to put extra-care in
making
sure there are no counter-intuitive things happening.
One of the counter-intuitive things that -is- happening is that when I create a new page from a pre-existing redlink the link does not become
blue
until I use the /purge action in the URL. I checked with showJobs.php and the job to update the page's cache is there. Somehow however, the jobs do not get triggered. I.e. as $wgJobRunRate is set to the default (1), every http request should take one job off the queue, right? But I'm not seeing this. It seems like the queue just gets longer.
I'm wondering, is this perhaps something that has to do with short urls? (they are otherwise functional) Or anything else in my .htaccess? It just seems like mediawiki doesn't see some page reloads or some newly created pages as enough to trigger the jobs queue to move forward.
Thoughts?
Kind regards,
Manu _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
With low activity wikis, I have found that creating a cron of runjobs.php works best. Relying on the default behavior only gets a fraction of the total jobs run.
On Friday, August 12, 2016, Emanuele D'Arrigo manu3d@gmail.com wrote:
Dear Nick,
apologies for my incredibly late reply, it is very ungracious of me.
Running runjobs correctly updates the links and turns them into blue. I have not tried with the browser in incognito yet because meanwhile I disabled the Mediawiki-based caching, seemingly solving the problem. So I'm tempted to say it was a server-side issue. I'm hoping that the 150 or so occasional users of the wiki won't load the server to the point that caching will be necessary. Still, I am puzzled as to why the job queue continued to grow no matter the http requests from my browser and the $wgJobRunRate set to 1. Perhaps I'm not understanding how the job queue works.
Again, apologies for the late reply and thank you for your help!
Kind regards,
Manu
On 8 June 2016 at 21:52, John <phoenixoverride@gmail.com javascript:;> wrote:
Two Yeah things might be happening.
Try opening the page with the red link in a private/incognito mode tab to check if it is your browser caching or the server.
second try running runjobs.php and ensuring that its just not a queue
issue
On Wed, Jun 8, 2016 at 3:28 PM, Emanuele D'Arrigo <manu3d@gmail.com
wrote:
Greetings,
quick intro: I have been a mediawiki user for a long time (wikipedia
and
within companies) but I only had a couple of stints at administering
one. I
am in the process of setting one up for my neighborhood - or about 65 families.
It pretty much all works but as my neighbors includes anything from
very
hightech people to very lowtech grandpas I have to put extra-care in
making
sure there are no counter-intuitive things happening.
One of the counter-intuitive things that -is- happening is that when I create a new page from a pre-existing redlink the link does not become
blue
until I use the /purge action in the URL. I checked with showJobs.php
and
the job to update the page's cache is there. Somehow however, the jobs
do
not get triggered. I.e. as $wgJobRunRate is set to the default (1),
every
http request should take one job off the queue, right? But I'm not
seeing
this. It seems like the queue just gets longer.
I'm wondering, is this perhaps something that has to do with short
urls?
(they are otherwise functional) Or anything else in my .htaccess? It
just
seems like mediawiki doesn't see some page reloads or some newly
created
pages as enough to trigger the jobs queue to move forward.
Thoughts?
Kind regards,
Manu _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On 13 August 2016 at 01:10, John phoenixoverride@gmail.com wrote:
With low activity wikis, I have found that creating a cron of runjobs.php works best. Relying on the default behavior only gets a fraction of the total jobs run.
How often do you run runjobs.php via cron? Or what criteria do you use to decide the frequency?
For me I have a low enough volume wiki that the overall queue doesn't grow too quickly so I run a cron every 10 minutes, primarily because I don't want email based notifications to lag too much.
On Saturday, August 13, 2016, Emanuele D'Arrigo manu3d@gmail.com wrote:
On 13 August 2016 at 01:10, John <phoenixoverride@gmail.com javascript:;> wrote:
With low activity wikis, I have found that creating a cron of runjobs.php works best. Relying on the default behavior only gets a fraction of the total jobs run.
How often do you run runjobs.php via cron? Or what criteria do you use to decide the frequency? _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org