Re: [Devil-Linux-discuss] mysql on 1.6.0-RC2 and newer

[Andrzej O. <an...@ma...>]

Heiko Zuerker wrote:
> is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql?
> If yes, is your mysql server starting on boot?

I did a review of my servers and I have one, bare metal, which starts mysql - 
for some time unnecessarily. He was needed by the php forum on Apache, but now 
this forum does not exist. On this server was working compilation with kernel 
3.2.6. However, mysql started on boot every time and did not fall.

> Starting Apache2: [  OK  ]
> Starting MYSQL Server: [  OK  ]

After this is running on ps list:

> root@Front:~ # ps -ef|grep mysql
> root      1806     1  0 18:39 ?        00:00:00 /bin/sh /usr/bin/mysqld_safe --user=mysql --pid-file=/var/run/mysql.pid --datadir=/var/mysql
> mysql     2124  1806  0 18:39 ?        00:00:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/mysql --plugin-dir=/usr/lib/mysql/plugin --log-error=/var/mysql/Front.err --pid-file=/var/run/mysql.pid --socket=/tmp/mysql.sock --port=3306

Today I compiled new image from last CVS (this with changed network script) 
and additionally patch and grsecurity 3.2.11, because I have had yesterday 
strange issue with 3.2.9 on one of satelite routers -- this router did not 
translated one (just one!) of internal addresses via NAT (but before change to 
3.2.9 all was ok). So I try 3.2.11...

Under this compilation on the mentioned server mysql is starting correctly 
too. But in both cases, there is no questions to mysql server, so daemon only 
waits. But waits stable.

> I'm having trouble with 2 of my mysql servers and want to make sure  
> it's not related to my configuration.
> (This is holding up the final 1.6 release).

Maybe this is configuration problem?

BTW. On this mentioned server I have very old nontypical SCSI disk with 
Adaptec controller. After upgrade from 3.2.6 (old udevd) to 3.2.11 (new 
udevd), this is the first time, I see on console this messages from udevd:

> Mounting other file systems...
> /dev/sda1 on /var type ext4 (rw)
> /dev/sde1 on /var/mailer type ext4 (rw)
> udevd[700]: failed to create queue file: No such file or directory
> 
> udevd[700]: failed to create queue file: No such file or directory
> 
> udevd[700]: failed to create queue file: No such file or directory
> 
> /dev/sdf4 on /var/iso type ext3 (rw)

and this messages are later repeated. BTW. this disk is workin correctly. What 
do you think about it after your successful battle with the new udevd?

As for now, I will return to 3.2.6.

Best Regards

-- 
Andrzej Odyniec