Good Catch,

It should be connecting to 127.0.0.1, but i did in fact orginally
pointing at 192.168.88.131, but was having this problem, and after
searching for hours, I found that it might be the ip address, to
switch it to the loopback address.

So where do you think its getting the second ip address.

Thanks,

Mike

On Wed, Aug 4, 2010 at 5:34 PM, dan (ddp) <[email protected]> wrote:
> On Wed, Aug 4, 2010 at 5:36 PM, Mike Smith <[email protected]> wrote:
>> Hello,
>>
>> So why would it connect then later give me these error, but it seems
>> to be logging to the Web UI. Any Ideas.
>>
>> Thanks,
>>
>> Mike
>
> The web ui does not use the database.
>
>>
>>
>> 2010/08/04 15:07:38 ossec-dbd: Connected to database 'ossec' at '127.0.0.1'.
>> 2010/08/04 15:07:38 ossec-dbd: INFO: Started (pid: 8672).
>> 2010/08/04 15:11:36 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>
> This seems odd. The first line has the database connecting to
> 127.0.0.1, but the last line mentions 192.168.88.131. Which should it
> be connecting to? Which is configured?
>
>> 2010/08/04 15:13:40 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>> 2010/08/04 15:14:24 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>> 2010/08/04 15:24:36 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>> 2010/08/04 15:28:24 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>> 2010/08/04 15:28:40 ossec-dbd(5202): ERROR: Error connecting to
>> database '192.168.88.131'(ossec): ERROR: Can't connect to MySQL server
>> on '192.168.88.131' (111).
>> r...@ossec2-local:/var/www/ossec#
>>
>

Reply via email to