Jump to content

User talk:Madman

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Madman (talk | contribs) at 05:50, 3 November 2017 (→Bot stuck?: minor). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Bot stuck?

Hi Madman, can you check on your bot - it created the new entries at Wikipedia:Inactive administrators/2017, but does not appear to have generated notifications. — xaosflux Talk 19:37, 2 October 2017 (UTC)[reply]

Working now, if it was you: thanks! — xaosflux Talk 01:16, 3 October 2017 (UTC)[reply]
Uh oh, I saw "working now" on the 3rd and assumed the initial report was due to the delay between report and notification cron jobs (to make sure report is done running, since it can take some time), didn't really follow up, but looking at it today it looks like notifications still haven't been sent out? Am I missing something? Should I kick off the task manually and investigate or has it been handled by another party? — madman 19:51, 16 October 2017 (UTC)[reply]

Bot appears to be down still, as far as I am aware noone else is working on issues with your bot. — xaosflux Talk 14:26, 20 October 2017 (UTC)[reply]

@Xaosflux: – Acknowledged; I meant whether the notifications had been handled by another party. Since I don't see any on Talk pages, I'll kick off notify1. I suppose the notify2 date will have to be adjusted to be sometime after the 1st, which will require a bit of manual configuration for the next few tasks, but I've done it before. Apologies for the inconvenience. — madman 02:36, 23 October 2017 (UTC)[reply]
I see what happened with the notify1 task when it was run automatically:
Oct 01 01:15:17 inactive.notify1 [debug] {"login":{"result":"Failed","reason":"Incorrect password entered. Please try again."}}
Oct 01 01:15:17 inactive.notify1 [error] Unable to log in and get authentication tokens
That's... pretty freaking weird seeing as it did the report 75 minutes prior and there was no problem. Looking into it. — madman 02:39, 23 October 2017 (UTC)[reply]
And that result from the API was clearly incorrect seeing as the inactive.update ("Removing administrators no longer inactive as of November 2017") task is still running; all the tasks have the exact same configuration. I'd say this was just a glitch but I'd be more comfortable if I could find a Phabricator ticket or some wikitech e-mail traffic indicating there were known issues around that time. Will continue to look into it. Should the second round of notifications for November admins be on the 10th or so? Does that seem reasonable? — madman 02:42, 23 October 2017 (UTC)[reply]
For the November batch, please do round2 notifications on or about Nov 15th. This will have no impact to the December people (who should not be double listed from the November list). — xaosflux Talk 02:56, 23 October 2017 (UTC)[reply]
Will do, and acknowledged (the report task never double-lists). Cheers, — madman 03:57, 23 October 2017 (UTC)[reply]
December 2017

Looks like the new cycle was not created either - can you tell if this is pending? — xaosflux Talk 13:47, 1 November 2017 (UTC)[reply]

Got {"login":{"result":"Failed","reason":"Incorrect password entered. Please try again."}} again. I'm... completely baffled. I guess I'll try changing the bot's password through frontend and config and see if that helps? In the meantime I'll run report and notify1 from console... — madman 04:22, 3 November 2017 (UTC)[reply]
Are you using Special:BotPasswords or normal web passwords? May want to try BotP's. — xaosflux Talk 04:26, 3 November 2017 (UTC)[reply]
If you are, there is a bug that that error will appear if you are using an IP not in the BotPasswords whitelist you define. — xaosflux Talk 04:29, 3 November 2017 (UTC)[reply]
Normal Web password. I can try the latter. It's weird that the behavior is inconsistent though. I'd run it from my own host to see if that changes anything, but running it on Tools means other people can be added to the project. (Though I haven't figured out what the implications of that are re sharing passwords to the MadmanBot account.) — madman 04:30, 3 November 2017 (UTC)[reply]
See also phab:T137805. — xaosflux Talk 04:35, 3 November 2017 (UTC)[reply]
Oh, that's interesting. Yes, the bot is using action=login, of course. Looks like I have to switch to either BotPasswords or OAuth (BotPasswords being the quicker option, of course). Thanks for the info. — madman 05:40, 3 November 2017 (UTC)[reply]
Successfully using a BotPassword now but will look into switching to OAuth in the future; BotPasswords makes me worry I may have missed a needed right (I did catch the right to e-mail users). I'll be keeping a close eye on it and hope reliability improves. — madman 05:48, 3 November 2017 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Madman&oldid=808496927"