Access log flooded with page not found errors from automated bots

[koki]

Per the summary, the Drupal access log is full of page not found errors from automated bots pounding on the website. This must be unnecessarily increasing server CPU load, database activity and bandwidth.

Possible solution: try Bad Behaviour module for Drupal.

Download page: ​http://drupal.org/project/badbehavior

These BadBehavior files also required: ​http://www.bad-behavior.ioerror.us/download/

Features and Benefits of BadBehavior here: ​http://www.bad-behavior.ioerror.us/documentation/benefits/

[mmadia]

With the recent upgrades to D6 and migrating off of WebFaction, is this still an issue?

[koki]

Spam bots are still an issue, although more or less under control now. Adding this module may still be worthy, but I don't have the time right now. If we can keep this ticket open as a reminder, that would be nice; if that's not possible, no big deal.

[nielx]

Website tickets don't have a version.

[pulkomandy]

Website tickets also don't have a milestone currently.

[waddlesplash]

No more Drupal access log, so no more worrying about bots.