Gavin Carr wrote:
> The rest of your log seems to be doing the right thing. Here in the
> first part, the plugin's clearly recognising this is a new ip
> address, but it looks as if the write to the db is failing somehow.
> It's not a locking issue - the lock is already held at this point.
>
> So I'm not sure why this is failing - could you have been out of disk
> space or something? What's the expected behaviour on a dbm tied write
> in this kind of situation (e.g. out of disk space)? Should it die or
> does it just fail via return code? Line in question is:
>
> $db{$key} = sprintf $fmt, time, ++$new, $black, 0;
No, not out of disk space. The log has already rotated out, and I forgot to
save a copy of it. While it was repeatedly failing on this ip address, it
was still actively counting hits on other blacklisted and moving others from
grey to white.
I am just learning perl, so will have to wait till later to disect that
line.
Sam
