Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Users
[Top] [All Lists]

Re: [Snort-users] Can't connect to db after upgrade

Subject: Re: [Snort-users] Can't connect to db after upgrade
Date: Mon, 31 Dec 2007 09:18:53 -0700



On 12/30/07 7:34 AM, "Stephen Bernacki" <snort@f.copacetic.net> wrote:

James Lay wrote:
Hey all!

After doing an upgrade to snort from 2.4 to 2.8, I now get:

Dec 29 13:10:56 gateway snort[16646]: FATAL ERROR: database:
mysql_error: Can't connect to MySQL server on '172.16.1.2' (110)

I can connect manually with:

[13:16:30 me@gateway:~$] mysql -u snort -p -D snort
Enter password:
[snip]

You didn't specify what operating system you're running, but under Linux
(CentOS 4.5), /usr/bin/perror returns:

centos4> perror 110
OS error code 110:  Connection timed out

Your manual connection is likely succeeding because it's using the local
mysql unix domain socket, not the TCP socket that snort is trying to use.

To troubleshoot further, try specifying the protocol and host to connect
to on the mysql command line:

centos4> mysql -h 172.16.1.2  --protocol=tcp  -u snort -p -D snort

You should now experience the same type of error that Snort is seeing.
 From this point I'd recommend checking your local firewall rules,
making sure that the locally running MySQL has a tcp socket listening on
the port you think it does, or configuring Snort to use the local MySQL
unix domain socket instead.

Steve


I'll be butched...that's TOTALLY what happened.  I have snort/mysql
installed on 4 machines and this is the only one with this issue.  I looked
but couldn't see how to config snort to use unix domain sockets.  I checked
the firewall and all seemed well as this is the same machine.  Very weird!
Can someone point me in the right direction for telling snort to use unix
domain sockets?

Thanks all!

James



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users

<Prev in Thread] Current Thread [Next in Thread>