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.

The 503 errors and DB ERRORs you've been getting were unrelated issues.

I'm not aware of any issues that should prevent the bot from doing what it's supposed to do. At this point, this ticket is merely addressing a major performance penalty the bot is currently incurring as a result of the bug regarding data ingesting.

This should be fixed hopefully today.

In T326609#8515415, @Marshelec wrote:

It worked ! It has successfully analysed the article: Tellico Dam where it was previously failing. It analysed 44 links, rescued 40, and added 12 archives. It took 703 minutes to run (longer than I would have expected prior to the recent problems), but it worked :). I have yet to check through the archives, but they look good in a quick inspection. Many thanks, M

In T321740#8515333, @Aoidh wrote:

It works for me when I just checked it. I ran it again on a page that earlier today brought me to a blank white page the way SunDawn described but now works: https://en.wikipedia.org/w/index.php?diff=prev&oldid=1132886366

In T321740#8515257, @SunDawn wrote:

Thank you for your work, but the tool broke again. The browser only displayed an empty page when the "Analyze" button is clicked.

In T326609#8515315, @Marshelec wrote:

Thanks, I just tried to analyse the article Tellico Dam again, but no good - same message about missing token. If I understand your comment about a Bot job correctly, it refers to scheduling in a queue ? I have set up a queued job for this article to see if that does the trick.

IABot has been whitelisted on CloudFlare.

You get that error when you refresh the UI on any action request without resubmitting form data. The tool uses tokens and checksum hashes to ensure requests are not accidentally repeated, and that malicious users can't exploit any CSRF vulnerabilities. In short, they're security features meant to keep you safe. All you need to do is click the submit button again when that happens.

Alright, give it a try now.

What's happening here is because the bot is taking longer to work on the article, it's hitting the server-side execution time limit and timing out. Ordinarily large articles are blocked from even running on the tool, where the user is instead directed to running a bot job instead with the desired article(s). I can try to push the time limit a little higher to get around this, but this will only be temporary. The limit exists to prevent rogue processes from indefinitely hanging up a connection resource, that would end up blocking someone else from using the tool.

If you want to follow the progress on getting the underlying issue fixed, you can subscribe to T326609

In T321740#8512577, @Nathan_Obral wrote:

Cyberpower, I apologize for being cross and angry the past few weeks. You kept your word and fixed it by EOD Monday. The bot largely works although it does time out on a few pages (but that could be a browser cache issue on my end).

Again, I apologize for the angry tone of my posts in this thread. The issue is fixed and again you kept your promise to fix it. Thank you and cheers.

There we go. It's EOD, Monday. Just as promised. Sorry for the wait. Tool should be working now.