On Thu, September 21, 2006 10:12, Ben wrote: > Hi Rob, > Just 'cos I got it working on one machine doesn't say so much - > thanks for having a go. > > It may be a good idea to get a tail on the mysql log ( hostname.err ) This is the complete MySQL error log. As it is a fresh install, there's not much in it (I cleaned it after I got MySQL working). It's correct that MySQL was started at 6:36 this morning. 060920 17:49:50 mysqld started 060920 17:49:50 InnoDB: Started; log sequence number 0 43655 060920 17:49:50 [Note] /usr/local/libexec/mysqld: ready for connections. Version: '5.0.24a' socket: '/var/mysql/mysql.sock' port: 3306 Source distribution 060920 23:19:46 [Note] /usr/local/libexec/mysqld: Normal shutdown 060920 23:19:46 InnoDB: Starting shutdown... 060920 23:19:48 InnoDB: Shutdown completed; log sequence number 0 43655 060920 23:19:48 [Note] /usr/local/libexec/mysqld: Shutdown complete 060920 23:19:49 mysqld ended 060921 06:36:01 mysqld started 060921 6:36:02 InnoDB: Started; log sequence number 0 43655 060921 6:36:03 [Note] /usr/local/libexec/mysqld: ready for connections. Version: '5.0.24a' socket: '/var/mysql/mysql.sock' port: 3306 Source distribution > Also, because I had put mysql into a custom directory, I needed to > change some of the variables in my.cnf - that may make a difference also. I installed in /usr/local but wanted a different datadir and a different location of my.cnf than /etc. I took care of that. > The following are what I used - (you must change the paths accordingly!) > [client] > #password = your_password > port = 3306 > socket = /opt/var/mysql.sock > <--- make sure this is to the correct sock! > sometimes old socks are left lying around. It's next to impossible to have old socks lying around: this is a fresh install of both OS (Slackware) and software on another machine than the one before. I wanted to make sure that I'm not going to have problems with the remains of any previous install. > basedir = /opt > datadir = /opt/lib/mysql Is this datadir in your [client] section? > tmpdir = /tmp > language = /opt/share/mysql/english > character-sets-dir = /opt/share/mysql/charsets My my.cnf contains this: [client] port = 3306 socket = /var/mysql/mysql.sock [mysqld] port = 3306 socket = /var/mysql/mysql.sock datadir = /var/mysql root@server:/var/mysql# ls total 20552 drwxr-x--- 6 mysqld mysqld 4096 2006-09-21 06:36 . drwxr-xr-x 17 root root 4096 2006-09-20 22:14 .. drwx------ 2 mysqld mysqld 4096 2006-09-20 20:17 apache -rw-rw---- 1 mysqld mysqld 5242880 2006-09-21 06:36 ib_logfile0 -rw-rw---- 1 mysqld mysqld 5242880 2006-09-20 17:43 ib_logfile1 -rw-rw---- 1 mysqld mysqld 10485760 2006-09-20 23:19 ibdata1 drwx------ 2 mysqld mysqld 4096 2006-09-20 17:26 mysql srwxrwxrwx 1 mysqld mysqld 0 2006-09-21 06:36 mysql.sock -rw-rw---- 1 mysqld root 790 2006-09-21 06:36 server.err -rw-rw---- 1 mysqld mysqld 5 2006-09-21 06:36 server.pid drwxr-x--- 2 mysqld mysqld 4096 2006-09-21 06:36 tmp So, it's all there. > I commented out the dbd.m4 file amends in the buildsteps of 15 Sept > - because they aren't necessary (the mysql.h logic in build.m4 is > just unreliable, IMO) Instead, for the include of the files in mysql.h etc., > it should be dealt with when you run configure as follows: > > CFLAGS="-DHAVE_MYSQL_H -I/usr/local/include/mysql/ -L/usr/local/lib/ > mysql/" ./configure [------------ your configure details ----------] > > I am not sure, but I am guessing you didn't run configure like that - > because as you said, HAVE_MYSQL_H wasn't being identified. Maybe you did that? > Let me know! No, I didn't run configure like that. I changed srclib/apr-util/Makefile later to include most details but didn't have "-DHAVE_MYSQL_H". Going to try that. Thanks, Rob --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|