User Details
- User Since
- Nov 14 2014, 4:15 PM (462 w, 1 d)
- Availability
- Available
- IRC Nick
- Cyberpower678 or CP678 or Skynet
- LDAP User
- Cyberpower678
- MediaWiki User
- Cyberpower678 [ Global Accounts ]
Yesterday
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.
Fri, Sep 22
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
Wed, Sep 20
Fri, Sep 15
Wed, Sep 13
Tue, Sep 12
iabot also affected too.
Aug 12 2023
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.
Jul 12 2023
Jul 11 2023
Should be done
Let me run it really quick. I wish it can run on it's own.
Jun 22 2023
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?
May 26 2023
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
May 22 2023
May 21 2023
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
May 17 2023
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.
May 12 2023
May 11 2023
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.
May 3 2023
May 1 2023
Apr 13 2023
Feb 27 2023
Feb 22 2023
Feb 17 2023
Feb 2 2023
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.
Feb 1 2023
This should be fixed hopefully today.
Jan 30 2023
Jan 29 2023
Jan 27 2023
Jan 25 2023
Jan 11 2023
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.
Jan 10 2023
If you want to follow the progress on getting the underlying issue fixed, you can subscribe to T326609
There we go. It's EOD, Monday. Just as promised. Sorry for the wait. Tool should be working now.