This looks like the Console has encountered an invalid transaction but
it is not handling it gracefully. It may be just one transaction that
your sensor is trying to send over and over again.
You should be able to find the transaction somewhere on the sensor
(look into the mlogc error log for failed transactions), but there
should also be a copy in the Console, somewhere in the logs/pending or
logs/invalid subfolder in var/data/main/console (or something like
that--I don't have a version running near me at the moment to check
the exact path).
Removing the transaction file from the sensor (just delete it) will
take care of this one instance, but the problem will need to be fixed
in the Console.
On Mon, Oct 27, 2008 at 3:48 PM, Clayton Dillard
> Thanks for the follow-up. Here is our version information:
> ModSecurity Console 1.0.5 (7 April 2008)
> [root@... logs]# java -version
> java version "1.6.0_10"
> Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
> Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)
> [root@... logs]# which java
> I have attached our log file as well.
> On Mon, 2008-10-27 at 13:13 +0000, Ivan Ristic wrote:
> I have seen that message, but not in a long while. Are you running the
> most recent version of the Console?
> If the answer is no--please upgrade. If the answer is yes, please send
> me the Console logs and I will look into the problem for you.
> On Mon, Oct 27, 2008 at 1:10 AM, Clayton Dillard
> <claytondillard@...> wrote:
>> After our ModConsole server died, we reinstalled on a new box. The
>> work fine but we're seeing tons of these errors in the console:
>> Failed processing RPC request: For input string: "0, 0"
>> Anyone know what's up with this?
>> - Clay
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> Build the coolest Linux based applications with Moblin SDK & win great
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> mod-security-users mailing list