Bot This user account is an AWB-based bot operated by Krinkle (talk). It is flagged as a bot.

It is not a sock puppet, but rather an automated or semi-automated account for making repetitive edits that would be extremely tedious to do manually.
Administrators: if this bot is malfunctioning or causing harm, please block it.

taskscontribscountlogspage moves block userblock logflag logglobal contribs flag bot

± This user is in fact a bot.

KrinkleBot is a pywiki-based bot that keeps Commons:Auto-protected files up to date.


See alsoEdit

In case of tools-labs grid failureEdit

If the fileprotectionsync job is stuck in the job queue (wikitech:Open Grid Engine), use the following instructions to resume the regularly programmed schedule:

$ ssh
$ become krinklebot

# Inspect the logs (recently modified?)
$ ls -l fileprotectionsync.*
-rw-rw---- 1 tools.krinklebot tools.krinklebot 48719 Oct 14 22:52 fileprotectionsync.err
-rw-rw---- 1 tools.krinklebot tools.krinklebot 82040 Oct 14 22:52 fileprotectionsync.out

$ tail fileprotectionsync.*
==> fileprotectionsync.err <==
Updating page [[Commons:Auto-protected files/wikipedia/fr]] via API
[Tue Oct 14 22:58:50 2014] there is a job named 'fileprotectionsync' already active
[Tue Oct 14 22:58:52 2014] there is a job named 'fileprotectionsync' already active

==> fileprotectionsync.out <==

# If the recent log contains only "job named .. already active" lines, it means the job queue
# is stuck. Kill the ghost processes to restore the schedule.

$ qstat
------ 0.00000 fileprotec tools.krinkl **    00/00/0000 00:00:00
------ 0.00000 fileprotec tools.krinkl **    00/00/0000 00:00:00

# Run "jstop fileprotectionsync" as many times as there are entries for it
$ jstop fileprotectionsync
$ jstop fileprotectionsync

# There should never be more than one entry due to `jsub -once`, but
# when it's stuck there's tends to also be more than one entry somehow.

# Verify crontab.txt and `crontab -l` match
$ crontab -l
$ cat crontab.txt

# The bot will automatically run within 15minutes (per cron schedule)

If the grid is entirely unresponsive, you can run it manually:

$ ./
Read in another language