Menu
▾
▴
devil-linux-discuss
|
From: Heiko Z. <he...@zu...> - 2012-03-15 13:03:42
|
Hey, 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'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). -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Dominic R. <dl...@ed...> - 2012-03-15 13:11:41
|
On 15/03/2012 13:03, Heiko Zuerker wrote: > Hey, > > is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql? yes (1.6.0-RC2-server x86) > If yes, is your mysql server starting on boot? yes, but I had to run mysql_upgrade (try: man mysql_upgrade)... > 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). HTH Dominic |
|
From: Heiko Z. <he...@zu...> - 2012-03-15 13:21:59
|
Quoting Dominic Raferd <dl...@ed...>: > On 15/03/2012 13:03, Heiko Zuerker wrote: >> Hey, >> >> is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql? > > yes (1.6.0-RC2-server x86) > >> If yes, is your mysql server starting on boot? > > yes, but I had to run mysql_upgrade (try: man mysql_upgrade)... I did that. I get the following error in the mysql.err file: ----------------------------------------- 120315 08:18:15 mysqld_safe mysqld from pid file /var/run/mysql.pid ended 120315 08:18:57 mysqld_safe Starting mysqld daemon with databases from /var/mysql 120315 8:18:58 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root! 120315 8:18:58 [ERROR] Aborting ----------------------------------------- When I start it on the command line via the init script, then it works fine and runs under the mysql user. I have this specified in the config file: MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid --datadir=/var/mysql" -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Dominic R. <dl...@ed...> - 2012-03-15 14:24:27
|
On 15/03/2012 13:21, Heiko Zuerker wrote: > Quoting Dominic Raferd<dl...@ed...>: > >> On 15/03/2012 13:03, Heiko Zuerker wrote: >>> Hey, >>> >>> is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql? >> yes (1.6.0-RC2-server x86) >> >>> If yes, is your mysql server starting on boot? >> yes, but I had to run mysql_upgrade (try: man mysql_upgrade)... > I did that. > I get the following error in the mysql.err file: > ----------------------------------------- > 120315 08:18:15 mysqld_safe mysqld from pid file /var/run/mysql.pid ended > 120315 08:18:57 mysqld_safe Starting mysqld daemon with databases from > /var/mysql > 120315 8:18:58 [ERROR] Fatal error: Please read "Security" section of > the manual to find out how to run mysqld as root! > > 120315 8:18:58 [ERROR] Aborting > ----------------------------------------- > > When I start it on the command line via the init script, then it works > fine and runs under the mysql user. > > I have this specified in the config file: > MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid --datadir=/var/mysql" > Hmm, it works for me. I have: MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid --datadir=/home/mysql --tmpdir=/home/bigtmp" So I guess in your case, but not mine, mysqld_safe is not picking up $MYSQL_PARM correctly? Has there been a change in CVS to /etc/init.d/mysqld or to /usr/bin/mysqld_safe? |
|
From: Dominic R. <dl...@ed...> - 2012-03-16 11:37:11
|
On 15/03/2012 14:24, Dominic Raferd wrote: > On 15/03/2012 13:21, Heiko Zuerker wrote: >> Quoting Dominic Raferd<dl...@ed...>: >> >>> On 15/03/2012 13:03, Heiko Zuerker wrote: >>>> Hey, >>>> >>>> is anybody using 1.6.0-RC2 (or the current CVS version) together with mysql? >>> yes (1.6.0-RC2-server x86) >>> >>>> If yes, is your mysql server starting on boot? >>> yes, but I had to run mysql_upgrade (try: man mysql_upgrade)... >> I did that. >> I get the following error in the mysql.err file: >> ----------------------------------------- >> 120315 08:18:15 mysqld_safe mysqld from pid file /var/run/mysql.pid ended >> 120315 08:18:57 mysqld_safe Starting mysqld daemon with databases from >> /var/mysql >> 120315 8:18:58 [ERROR] Fatal error: Please read "Security" section of >> the manual to find out how to run mysqld as root! >> >> 120315 8:18:58 [ERROR] Aborting >> ----------------------------------------- >> >> When I start it on the command line via the init script, then it works >> fine and runs under the mysql user. >> >> I have this specified in the config file: >> MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid --datadir=/var/mysql" >> > Hmm, it works for me. I have: > MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid > --datadir=/home/mysql --tmpdir=/home/bigtmp" > > So I guess in your case, but not mine, mysqld_safe is not picking up > $MYSQL_PARM correctly? Has there been a change in CVS to > /etc/init.d/mysqld or to /usr/bin/mysqld_safe? I think I caught this one. The reason for the problem is that variable $USER is not defined when mysqld starts at boot time (it should be 'root'). If you use the standard my.cnf (at /etc-cds/my.cnf and thence /etc/my.cnf) this doesn't matter because it defines user=mysql in [mysqld] section. But if you have a bespoke /etc/my.cnf without this definition, then mysqld is started up without any specified user and so it falls back to using the current user (root), and this then throws the error. [I confirmed this by testing.] If having $USER undefined at boot is 'by design' or unavoidable then /usr/bin/mysqld_safe can be patched to work thus: sed -i 's/"$USER" = "root"/`id -u` -eq 0/' mysqld_safe I've tested this and it works. Otherwise, if (as seems better to me) $USER can be defined before /etc/init.d/mysqld runs at boot time (as presumably it used to be before 1.6.0?), this patch should be unnecessary. At the end of working this out, I foolishly did rm /etc/init.d/mysqld (instead of rm /shm/etc-mods/init.d/mysqld) and now I can't restore the correct link-type to the underlying file at /etc-cd/init.d/mysqld (I've used a symbolic link but this isn't right I know). Can anyone help me do this? |
|
From: Heiko Z. <he...@zu...> - 2012-03-17 15:03:58
|
> -----Original Message----- > From: Dominic Raferd [mailto:dl...@ed...] > Sent: Friday, March 16, 2012 6:37 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] mysql on 1.6.0-RC2 and newer > > > > On 15/03/2012 14:24, Dominic Raferd wrote: > > On 15/03/2012 13:21, Heiko Zuerker wrote: > >> Quoting Dominic Raferd<dl...@ed...>: > >> > >>> On 15/03/2012 13:03, Heiko Zuerker wrote: > >>>> Hey, > >>>> > >>>> is anybody using 1.6.0-RC2 (or the current CVS version) together with > mysql? > >>> yes (1.6.0-RC2-server x86) > >>> > >>>> If yes, is your mysql server starting on boot? > >>> yes, but I had to run mysql_upgrade (try: man mysql_upgrade)... > >> I did that. > >> I get the following error in the mysql.err file: > >> ----------------------------------------- > >> 120315 08:18:15 mysqld_safe mysqld from pid file /var/run/mysql.pid > >> ended > >> 120315 08:18:57 mysqld_safe Starting mysqld daemon with databases > >> from /var/mysql > >> 120315 8:18:58 [ERROR] Fatal error: Please read "Security" section > >> of the manual to find out how to run mysqld as root! > >> > >> 120315 8:18:58 [ERROR] Aborting > >> ----------------------------------------- > >> > >> When I start it on the command line via the init script, then it > >> works fine and runs under the mysql user. > >> > >> I have this specified in the config file: > >> MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid -- > datadir=/var/mysql" > >> > > Hmm, it works for me. I have: > > MYSQL_PARM="--user=mysql --pid-file=/var/run/mysql.pid > > --datadir=/home/mysql --tmpdir=/home/bigtmp" > > > > So I guess in your case, but not mine, mysqld_safe is not picking up > > $MYSQL_PARM correctly? Has there been a change in CVS to > > /etc/init.d/mysqld or to /usr/bin/mysqld_safe? > > I think I caught this one. The reason for the problem is that variable $USER is > not defined when mysqld starts at boot time (it should be 'root'). If you use > the standard my.cnf (at /etc-cds/my.cnf and thence > /etc/my.cnf) this doesn't matter because it defines user=mysql in [mysqld] > section. But if you have a bespoke /etc/my.cnf without this definition, then > mysqld is started up without any specified user and so it falls back to using > the current user (root), and this then throws the error. [I confirmed this by > testing.] > > If having $USER undefined at boot is 'by design' or unavoidable then > /usr/bin/mysqld_safe can be patched to work thus: > > sed -i 's/"$USER" = "root"/`id -u` -eq 0/' mysqld_safe > > I've tested this and it works. Otherwise, if (as seems better to me) $USER can > be defined before /etc/init.d/mysqld runs at boot time (as presumably it > used to be before 1.6.0?), this patch should be unnecessary. I like your fix better actually. Applied to CVS. Thanks ! :) > At the end of working this out, I foolishly did rm /etc/init.d/mysqld (instead > of rm /shm/etc-mods/init.d/mysqld) and now I can't restore the correct link- > type to the underlying file at /etc-cd/init.d/mysqld (I've used a symbolic link > but this isn't right I know). Can anyone help me do this? Honestly I have no clue... :( I'd just copy the one from /etc-cd/ over. It'll get fixed during the next upgrade. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2012-03-15 18:29:33
|
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 |
|
From: Heiko Z. <he...@zu...> - 2012-03-17 14:23:06
|
> -----Original Message----- > From: Andrzej Odyniec [mailto:an...@ma...] > Sent: Thursday, March 15, 2012 1:29 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] mysql on 1.6.0-RC2 and newer > > 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? >From what I found on google, this points towards the devtmpfs not being mounted. Maybe we're missing a directory or some other command we need to execute for /dev to be proper? > As for now, I will return to 3.2.6. I'll include .11 in the next update -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2012-03-19 15:21:49
|
Heiko Zuerker wrote: > Maybe we're missing a directory or some other command we need to execute for > /dev to be proper? Perhaps something did not go well in the previous compilation. Next compilation gave good results, with no udev errors. Yesterday I put this build (32-bit) on the main router and on all my satelite routers and on MTA gateway machine. Everything so far is working properly. mysql too. Best Regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2012-03-22 16:05:53
|
Thanks for the update. This means I can release RC3 now. woohoo! Heiko Quoting Andrzej Odyniec <an...@ma...>: > Heiko Zuerker wrote: >> Maybe we're missing a directory or some other command we need to execute for >> /dev to be proper? > > Perhaps something did not go well in the previous compilation. Next > compilation gave good results, with no udev errors. Yesterday I put > this build > (32-bit) on the main router and on all my satelite routers and on MTA gateway > machine. Everything so far is working properly. mysql too. > > Best Regards > > -- > Andrzej Odyniec > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss -- Regards Heiko Zuerker http://www.devil-linux.org |
