No. IABot appears to be operating normally now, barring the backend being bogged down a bit.

Yea. It is.

There are still some Internet Archive services down and one of them is impacting the bot. Please be patient as the remaining services are brought back up.

@Novem_Linguae Check the poll link now?

Update lists{F57640781}

In T371454#10261248, @jrbs wrote:

(Gentle reminder that 22 people are receiving an email every time someone comments here ;) )

List is regenerating right now. Should be able to get in under the wire.

You appear to be in that category.

Oh whoops. I'm excluding users in the category "Users_who_do_not_wish_to_receive_ACE_messages"

And yet it still is. This script has not been altered over the years. I see no reason why it's excluding you.

I don't see anything in the program that should be excluding you. None of the set filters in the script applies to you.

Can confirm SQL is marking you as eligible. Checking filters...

In T371454#10261157, @Pppery wrote:

I get "This election has not yet started. It is scheduled to start on 25 October 2024 at 00:00." when I go to https://en.wikipedia.org/wiki/Special:SecurePoll/vote/812

I think you somehow got omitted from the voter roll - your name isn't at https://vote.wikimedia.org/wiki/SecurePoll:1691/list/need-list either.

In T370603#10254570, @Whoop_whoop_pull_up wrote:

They were doing just fine (and not just running, but successfully fetching archiveURLs) in the days before yesterday, though, when the Internet Archive wasn't in any better of a shape than it is now.

See, frex, batch jobs #21542 (the most-recent over-100-entries batch job of mine to successfully finish) and #21547 (the most-recent over-15-entries batch job of mine to successfully finish), both submitted on 21 October.

Even batch jobs submitted more recently, such as #21558, which jammed after just two articles, and #21566, which successfully completed its run only, I suspect, due to being so short that it avoided jamming by pure luck, still managed to successfully fetch archiveurls for one article apiece.

Given the state of Internet Archive, that shouldn't be surprising at this time.

In T371454#10245702, @Novem_Linguae wrote:

Hey Joe,

How are you? I hope you had a great weekend. Before I forget, below are the "translations" we can program into SecurePoll.

• messages: intro -

[[:w:en:Wikipedia:Administrator elections|Election main page]] • [[:w:en:Wikipedia talk:Administrator elections|Report problems or issues]]

'''''Instructions'''''
*'''Use the radio buttons.''' Please use the radio buttons below to indicate your preference for each candidate with "Support", "Oppose", or “Abstain”. An “Abstain” vote does not affect the outcome in any way.
*'''Vote in a single sitting.''' Voting must be done in a single sitting. 
*'''You may change your vote by starting over.''' After your vote has been accepted, you may change your vote any time before the close of voting. To do so, reuse the voting interface and a fresh default ballot page will be displayed. You will need to complete the process again from scratch. For this reason, consider keeping a private record of your vote. Your new ballot page will override the old one.

• messages: jump-text - This poll is set up for the 2024 English Wikipedia Administrator Election. Please click the button below to be sent to the secure voting server. Please note that when you vote certain information including your IP address and user agent will be collected to allow scrutineers to ensure the integrity of the vote. That information will be deleted 90 days after the election concludes and will only be visible to scrutineers and staff election advisors
• messages: return-text - 2024 English Wikipedia Administrator Election
• messages: unqualified-error - Your account does not meet the requirements to vote in this election. If you believe you are receiving this message in error, please post on the [[:w:en:Wikipedia talk:Administrator elections|election talk page]].
• questions: messages: text - 2024 English Wikipedia Administrator Election candidates

I believe @Cyberpower678 is working on the voter rolls and will post those here as soon as he has them.

Just to confirm, the vote link will end up being https://vote.wikimedia.org/wiki/Special:SecurePoll/vote/1691 ?

Thanks a lot. Looking forward to your feedback.

In T371454#10219154, @Novem_Linguae wrote:

Just poking around SecurePoll in my localhost. I'm happy to leave WMF T&S to creating the actual election in a week or two. But so I can be a better software engineer for Extension:SecurePoll, I'm trying to get my head wrapped around the different election types and how I would hypothetically configure this one.

Adding myself to the ticket as I will be supplying the voter rolls.

@Shizhao Would you be able to roll that edit back for the time being?

https://zh.wikipedia.org/w/index.php?title=Module:Citation/CS1/Configuration&diff=prev&oldid=82481555 appears to have broken the bot's ability to read the CS1 configuration.

Looking into this.

That's not exactly how the Dead option works. Dead and Alive are not set globally. They are set individually at the URL level. Only Permadead and Permalive are global states. As such when setting URLs in the domain as dead, no global status is actually being applied.

Should be resolved now. There was excessive load on the bot’s DB and the availability pipeline got backed up by a few days. The bot appears to have caught back up again.

I unfortunately, forgot about this tool entirely. Would somebody be willing to take this tool over?

Just confirming, you have moved away from Miraheze and WikiTide is now your wikis' homes? May I ask what prompted the move?

That's interesting. That may be simple enough to implement, I think.

I don't recall this ever existing before. Was this recently introduced?

In T327851#9209700, @Kailash29792 wrote:

504 once again.

Actually, I think you just clued me in as to what’s happening here. It might be the ident only consumer can’t actually make any API requests, thus it can’t resolve the categories. When you switch to the full consumer, the problem goes away.

Yes, it's resolved. I can't replicate your other issue at all. When I copy your submission list into a bot job it resolves categories just fine.

I don't know what you're doing to trigger that error, but when I copy your job list into the text field and submit it, I get https://iabot.wmcloud.org/index.php?page=viewjob&id=15129

iabot also affected too.

Looking at my code, it is correctly passing a timestamp to prevent edit conflicts. This appears to be an issue with MW itself. It shouldn't be letting an edit through when the timestamp is older than the last action on the page. It would seem MW doesn't acknowledge page moves as a conflict able action. Nothing that can be done here on my end.

Should be done

Let me run it really quick. I wish it can run on it's own.

In T340089#8955462, @robkam wrote:

User rights for InternetArchiveBot on five wikis is now bot. However InternetArchiveBot and Cyberpower678 both need to visit sdiy.wikitide.com and scruffy.wikitide.com please, in order to have the user rights set.

Thought I did, but I have definitely done it now. :-)

@robkam where are these wikis going to be primarily running now?

@robkam Can you confirm any of these moves? Can you give appropriate access? I noticed scruffy wiki is closed off to the bot on Miraheze and is unable to actually do anything there. I'm also closed off to it.

I've got a concern. The primary wikis that claimed to be migrated are still operating on Miraheze.

@Agent_Isai I'm going to need confirmed permissions on all wikis, or write permissions at least. InternetArchiveBot will need the bot flag on all applicable wikis, or the global bot flag. I can't move forward without this.

I think it's just a simple case of reassigning the already configured wikis from Miraheze to WikiTide.

Any update on this?

I've only been getting this response. From what I gather, I have not been able to send a single email, as I only get this error.

2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error: Uncaught PHPMailer\PHPMailer\Exception: The following From address failed: : MAIL FROM command failed,Our system has detected an unusual rate of messages originating from this\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:,451,SMTP server error: MAIL FROM command failed Detail: Our system has detected an unusual rate of messages originating from this\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr: SMTP code: 451 in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php:2030
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:Stack trace:
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:#0 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php(1678): PHPMailer\PHPMailer\PHPMailer->smtpSend()
2023-05-25 14:41:19: mod_fastcgi.c.487) FastCGI-stderr:#1 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php( in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php on line 2030
2023-05-25 14:43:07: http-header-glue.c.1499) read() 9 13: Connection reset by peer
2023-05-25 14:43:07: gw_backend.c.2275) response not received, request sent: 982 on socket: unix:/var/run/lighttpd/php.socket.iabot-0 for /api.php?action=statistics&format=flat, closing connection
2023-05-25 15:09:16: http-header-glue.c.1499) read() 8 9: Connection reset by peer
2023-05-25 15:09:16: gw_backend.c.2275) response not received, request sent: 978 on socket: unix:/var/run/lighttpd/php.socket.iabot-1 for /api.php?action=statistics&format=flat, closing connection
2023-05-25 20:32:05: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error: Maximum execution time of 30 seconds exceeded in /data/project/iabot/master/app/src/Core/APII.php on line 263
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error: Uncaught PHPMailer\PHPMailer\Exception: The following From address failed: : MAIL FROM command failed,Our system has detected an unusual rate of messages originating from this\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:,451,SMTP server error: MAIL FROM command failed Detail: Our system has detected an unusual rate of messages originating from this\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr: SMTP code: 451 in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php:2030
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:Stack trace:
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:#0 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php(1678): PHPMailer\PHPMailer\PHPMailer->smtpSend()
2023-05-26 04:06:42: mod_fastcgi.c.487) FastCGI-stderr:#1 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php( in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php on line 2030
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error: Uncaught PHPMailer\PHPMailer\Exception: The following From address failed: : MAIL FROM command failed,Our system has detected an unusual rate of messages originating from this\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:,451,SMTP server error: MAIL FROM command failed Detail: Our system has detected an unusual rate of messages originating from this\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:sender address. To protect our users from abuse this sender address has\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:been temporarily rate limited. Please try again later.\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use\r
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr: SMTP code: 451 in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php:2030
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:Stack trace:
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:#0 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php(1678): PHPMailer\PHPMailer\PHPMailer->smtpSend()
2023-05-26 04:06:58: mod_fastcgi.c.487) FastCGI-stderr:#1 /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php( in /data/project/iabot/master/vendor/phpmailer/phpmailer/src/PHPMailer.php on line 2030

I cannot reproduce any process issue on my machine with ANY PHP version regarding this. I have tried and tried and tried, and it loads successfully in all cases. I don't believe I am inducing a segfault. This endpoint loads and works fine for a while after a web service restart and then stops randomly working. I'm more inclined to believe that issue lies outside of PHP? @bd808

Well segfaults are insanely difficult to determine especially if random on identical calls to the same endpoint delivering identical results. :/ Would there be any indication that it could be a crash outside of PHP? I can certainly see if I can find the segfault inducing code on my end.

Waiting for sysadmin support on Internet Archive end.

The PHP timeouts and sendmail issues are not what we are worried about, as those are fixable on our end. We don't know what the establishing connection failed: socket: unix:/var/run/lighttpd/php.socket.iabot-0: Resource temporarily unavailable is for or how to fix it as that is what is causing the intermittent 500 error, which happens with increasing frequency until we reboot the web service.