Customizing SMF > Modifications and Packages
httpBL
locutusweb:
--- Quote from: snoopy_virtual on October 19, 2011, 05:46:32 AM ---This mod needs the table smf_log_httpbl to work properly, so when you install the mod, one of the first things it does is to check if that table already exists.
If that table already exists the mod is supposed to go to the next step and don't show any error (and if it doesn't exists is supposed to create it). You shouldn't get any error there.
I suppose they must have changed the way the Packages Manager works in SMF 2.0.1 when creating new tables and it was trying to create the table again anyway (even if the mod was telling it to ignore it) so that's why you were getting the error saying "Table 'smf_log_httpbl' already exists".
You should have ignored that error and continue with the installation anyway.
The big problem now is when you removed that table from the database. The mod now cannot work at all.
I think the easiest solution now (if you haven't sort it already using another solution) would be this:
* Uninstall the mod.
* Check that the table 'smf_log_httpbl' still doesn't exist (or delete it if it does).
* Install the mod again.
--- End quote ---
Sadly, I had to rebuild my smf forum after my host have been hacked. I am using my old DB; but when I install the mod I get the error "Table 'smf_log_httpbl' already exists". Since I have a clean install can't uninstall the mod, but when I delete the mentioned table I get the error "Table 'smf_log_httpbl' doesn't exist". I am in kind of loop.
Inti31:
I might to remember about that - rename that table to "smf_log_httpBL" and then it will work... - please note the capital BL at the end.
thought this were already said in this topic...
i had that problem in the past also - and thats the solution
cheers Inti31
locutusweb:
Thanks, that didn't work either. :'(
At the end I deleted all references to httpbl in the DB and changed the install script to force install.
Kolya:
One thing that always bugged me about this mod is how it fills up the logs. It also wasn't very useful for me to know how many spammers it caught since day one. So in the end I wrote a cronjob that runs once a week. It empties the log and sets back the number of caught spammers to zero. That way this number actually becomes useful because now I can see if it's more or less than last week. Anyway, here's the file to run as cron:
<?php
// Connection details
$db['host'] = 'localhost';
$db['user'] = '';
$db['pass'] = '';
$db['db'] = '';
// MySQLconnection
$link = mysql_connect($db['host'], $db['user'], $db['pass']);
if (!$link) die('Could not connect: ' . mysql_error());
//Select database
mysql_select_db($db['db'], $link);
//Delete httpBL mod log
$query = "TRUNCATE smf_log_httpBL";
mysql_query($query, $link);
//Update httpBL catch count number
$query = "UPDATE smf_settings SET value=0 WHERE variable='httpBL_count'";
mysql_query($query, $link);
// Close database connection
mysql_close($link);
?>
busterone:
Interesting.
I do look through the logs myself. I look for consistent hits by the same ips over a period of time and what they are attempting to do (register, login, etc). I don't have a db size issue to be concerned about though, so I usually just manually clear the logs on the average of once per week.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version