| Bug #11603 | "Asked for 196608 thread stack, but got 126976" | ||
|---|---|---|---|
| Submitted: | 28 Jun 2005 6:11 | Modified: | 4 Jul 2005 13:59 |
| Reporter: | Sulaiman Aleem | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
| Version: | 4.1.12 | OS: | Linux (Red Hat Fedora 3) |
| Assigned to: | CPU Architecture: | Any | |
[28 Jun 2005 6:11]
Sulaiman Aleem
[29 Jun 2005 4:56]
Sulaiman Aleem
I was able to get MYSQL to install editing /etc/selinux/config to say: # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=permissive # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted I still got the thread warning but at least the install and restart is worked after changing enforcing to permissive. I hope that this helps. Thanx Allah
[4 Jul 2005 13:59]
MySQL Verification Team
HI! Thank you for writting to us. Regarding SELinux, we are preparing scripts that will deal with SELinux and RH AS/EL 4.0 security issues. However, those will take some time. Regarding thread stack warning, you can ignore it. It comes from the fact that our special glibc library, with which mysqld binary is linked, is patched with maximum of 128 K thread stack. However, default thread stack is set to 198 K, as this is required due to some bugs present in 2.3 glibc. As glibc binary which we use for static linking is a very stable 2.2 , there is nothing to worry about.
[14 Jul 2005 15:46]
Virgil Cui
I have the same problem as Sulaiman's. And strange enough, I have 2 boxes both running Redhat Fedora3 with mysql 3.23.58. One works fine after ugrade to 4.1.12; the other has the same problem. I have the exactly upgrade sequences for both machines. (also chown mysql:mysql /var/lib/mysql along with its subdirectorys and files)
rpm -Uvh MySQL-shared-compat-4.1.11-0.i386.rpm
rpm -Uvh MySQL-server-4.1.12-1.i386.rpm
rpm -Uvh MySQL-client-4.1.12-1.i386.rpm
rpm -Uvh MySQL-bench-4.1.12-1.i386.rpm
rpm -Uvh MySQL-devel-4.1.12-1.i386.rpm
rpm -Uvh MySQL-embedded-4.1.12-1.i386.rpm
In fact, the one has problem was fine after upgrade but before reboot. However, after reboot, it just keep failure.
In the syslog, I can see a lot of such errors.
====
Jul 14 09:32:44 m8 kernel: audit(1121347964.990:0): avc: denied {
write } for pid=3645 exe=/usr/sbin/mysqld name=mysql dev=hda2 ino=3859675 scont
ext=user_u:system_r:mysqld_t tcontext=root:object_r:var_lib_t tclass=dir
====
And in the boot.log, it shows the error as below
====
Jul 14 09:31:23 m8 mysql: MySQL PID file could not be found!
Jul 14 09:31:23 m8 lsb_log_message: MySQL PID file could not be foun
d! failed
Jul 14 09:31:23 m8 mysql:
Jul 14 09:31:23 m8 rc: Stopping mysql: succeeded
====
Anyway, after I change the selinux settings in /etc/selinux/config as Sulaiman mentioned in his previous message, and reboot the box. At this time, mysql still didn't come up. But it comes up now after I uninstall server package and install it again.
rpm -e --nodeps MySQL-server-4.1.12-1.i386.rpm
rpm -i MySQL-server-4.1.12-1.i386.rpm
BTW, the only difference in my mind between my 2 boxes is that. The fine one I applied all the available updates from Redhat before upgrade mysql. The pain one I upgraded to mysql, and then applied the last 3 days updates from Redhat.
Hopefully it can help.
