[afnog] help with ACID installation

Sergio Carrilho seergio.carrilho at gmail.com
Thu May 12 11:55:47 EAT 2005


Ayitey
>Check the obvious first, do you have the socket in the right place i.e.
'/var/lib/mysql/mysql.sock'

Yes. I checked this and it's in there. but I have a doubt in here(I'm
not too familiar in working with sockets).  when mySQL is running the
command "ls -la" in "/var/lib/mysql/" gives me the following output:

drwxr-xr-x   5 mysql mysql 4096 May 12 10:23 .
drwxr-xr-x  20 root  root  4096 May  3 10:43 ..
drwx------   2 mysql mysql 4096 May  3 11:16 mysql
srwxrwxrwx   1 mysql mysql    0 May 12 10:23 mysql.sock
drwx------   2 mysql mysql 4096 May  3 11:48 snort
drwx------   2 mysql mysql 4096 May  3 11:16 test

Is the value "0" normal in here? And when mysql is not running the
file "mysql.sock" is not there

>I have also seen some problems using the later versions of mysql i.e. the
>client program trying to connect is an older version than the server itsself.
I'm running server version 3.23.58, so I think there's no problem here

the error logs I see (/var/log/mysqld.log) are just:

"Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
http://www.innodb.com/ibman.html
/usr/libexec/mysqld: ready for connections"

Benjamin:
I tried to start it in the command line as you proposed by it doenst
work. the file /etc/my.cnf looks like this (I inserted the [client]
part):

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[client]
socket=/var/lib/mysql/mysql.sock

It still gives me same error!

It seems to me that it is loggint the snort alerts but acid is not
able to comunicate with it too get the data. I ran

echo "SELECT count(*) FROM event" | mysql snort -u root -p

and the output was:
count(*)
484



More information about the afnog mailing list