[mod-security-users] Problems with mod_security console - Can anyone help?

[Johnny S. <li...@op...>]

I recently upgraded to mod_security 2.1.4 and due to forgetting the 
mod_security console password, I simply re-installed it fresh on a 
CentOS 5x server.

I basically copied all the settings I had from the previous, working 
installation and I have the mlogc working and a sensor created and it 
seems to connect to the console (both are on the same machine), but it 
then cant seem to write the data. Below is a 
/var/log/mlogc/mlogc_error.log entry

Anyone have any ideas?


[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] File found, activating cURL.
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL: About to connect() 
to 192.168.10.2 port 8886 (#0)
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL:   Trying 
192.168.10.2...
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL: connected
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL: Connected to 
192.168.10.2 (192.168.10.2) port 8886 (#0)
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL: Server auth using 
Basic with user 'Gateway'
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] CURL: Connection #0 to 
host 192.168.10.2 left intact
[Thu Dec 13 19:30:38 2007] [4] [7874/9fe9008] Request returned with 
status 500: qA-xg8CoCgIAABy8Uo4AAAAG
[Thu Dec 13 19:30:38 2007] [2] [7874/9fe9008] Flagging server as errored 
after failure to submit entry qA-xg8CoCgIAABy8Uo4AAAAG with HTTP 
response code 500



Johnny