As a network admin i would recomend you do that. I had mail gateways that keep getting taken down a number of years ago till i started setting max number of connections and other such fun stuff. Reboot fixes it for a day till they decide to come back.
This kind of stuff has been a continuous pain. We moved to a new PHBB server when the old board kept crashing because of stuff like this. We experienced "Ground Hog Day" for a while when searchbots crashed the place and when the server reset, it rolled back to the same backup "save point" and everything past that point was lost. It was the morning of June 23, 2006, every day for several days.
I got the IP address of the 'bot, but I don't think banning it will do any good. It's not registering and posting; it's just searching. It does try to post as I can look at users online feature and see IP #xxxxxxx " listed fifty times viewing every sub forum and "posting a message", but it can't because it's not a registered user.
From the error message it looks like a DB parameter threshold has been reached for a particular user. Clearling the attribute for the indicated user might be one step in the fix process, but obviously the root cause seems to be the bot attack.
[&:] Huh?
That's the same kind of geek speak I see on the PHBB help forums. I've been looking at those and it says I have to enter a specifically worded query into some search function in the admin data base and then frazzle the gimbits and mizzen the mainmasts until framises and whosits coincide with the paramaters of the whosit.
I'm old school. I'd prefer to track down who ever let this search bot lose and snatch him up by the stacking swivel.