Conversation

Notices

1. Embed this notice
   Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Saturday, 31-Dec-2022 21:18:28 JST Albert ARIBAUD ✎

   • brand?ₖₒᵖᶠ
   • Ajira

   @brandkopf
   Worse than that: the system runs low on memory, so the OOM killer kills a process but not necessarily one that was needing memory right now. MariaDB may be an accidental casualty here. :(
   @akira

   • Embed this notice
     Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Saturday, 31-Dec-2022 20:48:18 JST Albert ARIBAUD ✎

     in reply to

     • brand?ₖₒᵖᶠ

     @brandkopf
     Do you have a cache system ?

   • Embed this notice
     brand?ₖₒᵖᶠ (brandkopf@mastodon.art)'s status on Saturday, 31-Dec-2022 20:48:19 JST brand?ₖₒᵖᶠ

     in reply to

     btw. I counted about 1500 instances which are requesting my page within 3 seconds .... :(

   • Embed this notice
     brand?ₖₒᵖᶠ (brandkopf@mastodon.art)'s status on Saturday, 31-Dec-2022 20:48:20 JST brand?ₖₒᵖᶠ

     Unfortunately my small portfolio page always has problems as soon as I post a link to it on Mastodon because of the enormous rush of all Mastodon instance crawlers.
     I hope I can fix this somehow.

     Do you have experience with this? ?

     https://sommerlich.art

   • Embed this notice
     Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Saturday, 31-Dec-2022 21:01:47 JST Albert ARIBAUD ✎

     in reply to

     • brand?ₖₒᵖᶠ
     • Ajira

     @brandkopf @akira Right now your site shows a 'Error establishing a database connection". If the issue is the afflux of bots just checking for the page, that should not result in database accesses.

   • Embed this notice
     brand?ₖₒᵖᶠ (brandkopf@mastodon.art)'s status on Saturday, 31-Dec-2022 21:01:48 JST brand?ₖₒᵖᶠ

     in reply to

     • Ajira

     @akira @aaribaud I use fail2ban for bot blocking... but I dont know if it is wise to ban all mastodon instances from my page... maybe there are some side effects like that my page is then blacklisted by the instances?

   • Embed this notice
     Ajira (akira@framapiaf.org)'s status on Saturday, 31-Dec-2022 21:01:56 JST Ajira

     • brand?ₖₒᵖᶠ

     @brandkopf @aaribaud you can install a bot blocker with automatic blacklist update perhaps it can help. Take a look on this project : https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker

   • Embed this notice
     Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Saturday, 31-Dec-2022 21:04:25 JST Albert ARIBAUD ✎

     in reply to

     • brand?ₖₒᵖᶠ
     • Ajira

     @brandkopf
     Any logs showing which part of the server fails?
     @akira

   • Embed this notice
     Albert ARIBAUD ✎ (aaribaud@mastodon.art)'s status on Saturday, 31-Dec-2022 21:22:50 JST Albert ARIBAUD ✎

     in reply to

     • brand?ₖₒᵖᶠ
     • Ajira

     @brandkopf
     What you could do is, next time you publish content, you start watching the system for memory-hungry processes, and look for processes that increase their memory consumption when the bot swarm hits. Not sur if there's a tool for this -- detecting processes which keep requesting more memory, whether their total memory consumption is high or not.
     @akira