[04:23:34] I'm broke [04:23:58] whops wrong tab [06:27:51] So... [06:28:01] what causes "wikitools.api.APIError: (u'blocked', u'You have been blocked automatically by MediaWiki.')" I wonder. [06:28:20] It looks like logging in fails, and then that error gets raised when the bot tries to edit. [07:57:29] Ivy: where are you trying to edit from? I believe all of toolforge is blocked from anonymous editing [07:58:17] Ivy: also you probably want to use &assert=user to prevent logged out edits in general [18:50:54] legoktm: So the login is failing and then yeah, it's getting blocked because of that Toolforge range thing. [18:51:05] It seems to fail logging in intermittently. [18:51:09] Like maybe 30 times in 2017. [18:51:52] https://p.defau.lt/?U96lC6q6oAfWi7BBaIBlqQ [18:52:23] Those are all the times it failed that I have logs for. [18:53:14] Also, I was and still am opposed to the IP block. I think assert=user and not making the edit is worse than making the edit """"""""ANONYMOUSLY"""""""". [18:53:39] But that's not really relevant, since it's the failed login that's more concerning. [18:53:51] I ran the script manually and it worked. But it failed two weeks in a row via cron. [18:54:21] And people on-wiki are like "why didn't this report update?!" and I'm like "yeah, Idk, bro." [19:01:00] a common reason for scripts started via cron to fail is .. that they have been run manually before [19:01:09] then file permissions are changed to the user who ran it [19:01:15] and later the cron user cant write [19:01:37] try running it manually as the same user that has the cron entry [19:01:49] (using sudo -u) and then see what happens [19:02:15] also watch for email from cron that may have more hints for why it fails [19:06:03] mutante: There are are like 100 reports and this is only happening sometimes for some of them. [19:06:12] The .login() call is returning Failed for some reason. [19:06:19] And then the edit fails because the IP is blocked. [19:06:27] But the .login() call works much/most of the time. [19:07:11] I could try logging in a bunch, maybe. [19:07:16] Or add more verbose logging. [19:08:23] yea, that sounds reasonable. sorry i dont know anything about this specific issue, i was just sharing general experience with failed crons [19:09:01] Sure. :-) [19:09:29] mutante: Maybe a bunch of other bots/scripts are logging in at the same time and it's hitting a rate limit of some kind? [19:09:33] Was a guess of mine. [19:09:50] That would explain the intermittent behavior. [19:13:04] that sounds possible, yea. try the verbose logging thing [19:22:32] I should, but that's work. :-(