User talk:Beetstra

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

Link Watchers[edit]

Hi, we spoke a couple of months ago about LiWa in fawiki's channel and apparently you missed the last message i left you. I was on a Wikibreak until now and upon return, i noticed that the problem was still standing. Any thoughts? Thanks. -- Arian Talk 08:25, 25 October 2016 (UTC)

I'll have to have a look at that .. I guess for some commands you are not 'trusted' .. I'll ping you when I have a minute to have a look at it. --Dirk Beetstra T C (en: U, T) 08:30, 25 October 2016 (UTC)

Link analysis seems to have stalled[edit]

Everything seems to be present and functioning from IRC-side, however, the link analysis and thus the writing of link analysis is not present, see special:contributions/COIBot. Thinks poked at the analysis through IRC seem to queue and progress, just no output. No warnings are generated. syslog looks okay Syslogs: case: 151824 secs. coibot: 141 secs. commander: 0 secs. diffreader: 938 secs. linksaver: 85 secs. output: -1 secs. parser: 964 secs. script: -1 secs. special: 13027317 secs. Yours flummoxedly.  — billinghurst sDrewth 22:11, 28 October 2016 (UTC)

@Billinghurst: The bot has a massive backlog .. I guess it does not do too much of analysis to speed up getting rid of it. --Dirk Beetstra T C (en: U, T) 13:49, 29 October 2016 (UTC)
Really? it says that it is stepping through the backlog output files, writing nothing; it undertakes its xwiki requests, and writes nothing to meta. I must be missing something as backlog and status reports have been many times worse.  — billinghurst sDrewth 03:02, 30 October 2016 (UTC)
Not really :-) .. it got logged out. Solved .. I hope. Please let me know if there are more problems. --Dirk Beetstra T C (en: U, T) 03:23, 30 October 2016 (UTC)
Okay, that makes sense. It is writing again. If there is a check that can be run, beyond staring at its absence, please let me know.  — billinghurst sDrewth 10:48, 30 October 2016 (UTC)
I think it tells you as an error message in a channel. Maybe should be added to my bot-monitoring channel. --Dirk Beetstra T C (en: U, T) 10:54, 30 October 2016 (UTC)

Announcing a new mailing list for Meta-Wiki administrators[edit]

Hello!

As a regular administrator on Meta-Wiki, you're allowed to subscribe to the recently created metawiki-admins mailing list. This is a closed mailing list for announcements, asking for help and discussion between Meta-Wiki administrators. If you wish to subscribe, please fill the form at this page and then contact Savh or MarcoAurelio via Special:EmailUser using your administrator account so they can verify the authenticity of your request and address. You'll find more information on the mailing list description page. Should you have any doubts or questions, feel free to contact any of us. We hope that this tool is useful for all.

Best regards,
-- MarcoAurelio and Savh 12:30, 9 November 2016 (UTC)
Mailing list administrators for metawiki-admins mailing list.

Message sent to members of Meta:Administrators/Mass-message list. Please see there to subscribe or unsubscribe from further mass messages directed to the whole group of administrators.

Bot[edit]

Hi! I wonder why the bot does this kind of stuff? Repeating each minute that the link is already blacklisted does not seem like a good plan :) Regards, —MarcoAurelio 15:51, 21 November 2016 (UTC)

Also:

[17:02] mafk    COIBot join rc channel #es.wikibooks
[17:03] mafk    COIBot join lw channel #es.wikibooks

seems not to work. Can you do some magic? Thanks! —MarcoAurelio 16:04, 21 November 2016 (UTC)

The former is strange, seems like it is looping somewhere. I'll try to have a look.
The latter .. sigh .. it is something that needs a rewrite by copy from from LiWa3 .. probably too many channels in one module. Also for this, I'll try to have a look. I hope to have some time mid December for a bit better bot maintenance work. --Dirk Beetstra T C (en: U, T) 03:18, 22 November 2016 (UTC)

Please restart COIBot[edit]

Hi. I think COIBot needs a restart. It is not responding to any IRC commands. I left you a message at wikitech regarding this as well. Regards, —MarcoAurelio 16:06, 27 November 2016 (UTC)

@MarcoAurelio: I have started the bot again this morning - it appeared to have crashed. I'll check a bit in a couple of hours. (sorry for the late reply, I have limited access to the servers at the moment). --Dirk Beetstra T C (en: U, T) 05:54, 1 December 2016 (UTC)
Found a lost 15 minutes. Made some code adaptations. Problem seems to be that the LinkSaver has serious work on some domains, and that stalls the bot. I have built in a bit of a catch to keep it a bit calmer. --Dirk Beetstra T C (en: U, T) 14:36, 1 December 2016 (UTC)

COIBot living though not editing[edit]

Hi. COIBot lives in IRC and appears to be functioning as expected, however, it is not writing edits to meta, and backlog shows a number of reports queued. Thanks.  — billinghurst sDrewth 11:07, 15 December 2016 (UTC)

Funny, it just started editing ... I'll have a proper look at it later this weekend. --Dirk Beetstra T C (en: U, T) 13:30, 15 December 2016 (UTC)

It is back in the same situation again; only writing a quickcreate. Yet it is gobbling up backlog files (without report writing), I am wondering whether it is churning through a case of some sort? Logs say
<COIBot> Syslogs: case: 410209 secs. coibot: 274 secs. commander: 1 secs. diffreader: 1963 secs. linksaver: 11 secs. output: 108 secs. parser: 3627 secs. script: -1 secs. special: 3569180 secs.
[21:55] <LiWa3_3> Syslogs: diffreader: 16 secs. linkanalyser: 91 secs. linkparser: 6115 secs. linkreporter: 864293 secs. linkwatcher: 147 secs. output: -1 secs. script: -1 secs.

but I cannot tell/remember what I am looking for.  — billinghurst sDrewth 11:45, 27 December 2016 (UTC)

Still without writinig
Syslogs: case: 474467 secs. coibot: 521 secs. commander: 0 secs. diffreader: 5382 secs. linksaver: 249 secs. output: 367 secs. parser: 25934 secs. script: -1 secs. special: 3633438 secs
Syslogs: diffreader: 13 secs. linkanalyser: 256 secs. linkparser: 1822 secs. linkreporter: 928550 secs. linkwatcher: 3106 secs. output: -1 secs. script: -1 secs.
 — billinghurst sDrewth 05:18, 28 December 2016 (UTC)
There has been reports! ;-)
Syslogs: case: 9970 secs. coibot: 937 secs. commander: 0 secs. diffreader: 2211 secs. linksaver: 399 secs. output: -1 secs. parser: 7313 secs. script: -1 secs. special: 3752307 secs.
Syslogs: diffreader: 3 secs. linkanalyser: 61 secs. linkparser: 3501 secs. linkreporter: 1047430 secs. linkwatcher: 578 secs. output: -1 secs. script: -1 secs.
So presumably it was just something BIG!  — billinghurst sDrewth 13:51, 29 December 2016 (UTC)

FYI. It is apparent that when it gets into a backlog file-reading phase that COIBot stops writing reports. This means that the current situation of nearly 7k files (oscillating up and down) is meaning that we have no reports and at this rate we won't get any for a while.—The preceding unsigned comment was added by Billinghurst (talk)

LiWa3 is on an instance that cannot be cleared, and there are three python scripts on it that take away most of the processor speed. It has been tried to move LiWa3, but that also does not seem to work. I guess I will have to live to wait that the other tasks die ... Until then likely no automatic reports, though it should save the requested ones (COIBot and LiWa3 are independent of each other), but thos reports are then likely missing the last data. --Dirk Beetstra T C (en: U, T) 03:38, 9 January 2017 (UTC)

The bot was off processing for a couple of days, and the report that it generated was User:COIBot/LinkReports/airkobokan.com which is not very big. I do note that it has a simple http line. So noting it for the next time it disappears processing again.  — billinghurst sDrewth 10:20, 22 January 2017 (UTC)

@Billinghurst: you could try an on-irc restart linksaver. That should kill the linksaver and automatically spawn a new one. The report it is then saving is lost (if any). Regarding this morning, I killed it from the console. I'll have a look what it said before that. --Dirk Beetstra T C (en: U, T) 10:30, 22 January 2017 (UTC)
@Billinghurst: .. it may just have been logged out from meta .. it was editing on en.wikipedia ... --Dirk Beetstra T C (en: U, T) 10:42, 22 January 2017 (UTC)
?-: is there an online test for its status? I don't like pinging all the time when it is just a case of waiting— as it can be on occasions.  — billinghurst sDrewth 11:07, 22 January 2017 (UTC)
@Billinghurst: it had contributions on en.wikipedia. --Dirk Beetstra T C (en: U, T) 11:30, 22 January 2017 (UTC)
Oh, you mean something else. No, there isn't. syslog linksaver on IRC however might give some info towards what is happening .. --Dirk Beetstra T C (en: U, T) 11:31, 22 January 2017 (UTC)
It has stopped writing again, though it is still feeding-in reports; and linksaver looks to be happily churning away.  — billinghurst sDrewth 09:43, 27 January 2017 (UTC)
And again only on Meta. I tried to log it back in just now, let's see what it does. --Dirk Beetstra T C (en: U, T) 13:03, 27 January 2017 (UTC)
YesY  — billinghurst sDrewth 10:28, 28 January 2017 (UTC)

Seems that COIBot may be logged out of meta and enWP. No reports for about twelve hours at either. Running syslog linksaver shows that it is running and believes that it is saving reports
Line 5: * 2017-2-11 @ 23:36:55 - Saving report Wikipedia:WikiProject_Spam/LinkReports / mystellar.org on en.wikipedia.org
 — billinghurst sDrewth 23:41, 11 February 2017 (UTC)

Gone west! Looks like it is sitting waiting for input. Linksaver is there waiting ... staring (restarts made no change). Everything just seems there and just twiddling their virtual thumbs awaiting a feed.  — billinghurst sDrewth 10:43, 27 February 2017 (UTC)

Tried to log it in again .. just did that this morning .. I don't understand why COIBot loses its login so often, much more than XLinkBot. --Dirk Beetstra T C (en: U, T) 11:31, 27 February 2017 (UTC)
Okay, if logged out, then linksaver sits there looking stupid. Got it. Makes sense.  — billinghurst sDrewth 12:01, 27 February 2017 (UTC)