| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 86602 | 2008-01-22 03:31:00 | MySQL & nscd | Erayd (23) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 632766 | 2008-03-07 23:15:00 | Odd, It does sound like you do not have the local GID / UID for MySQL synced correctly with the auth DB and maybe MySQL cannot get correct access to one of it's control files as there is a mixture of GID / UID? which would explain why it will not even work off the local passwd / group data. Even if the above is true it still would not explain why enabling nscd with caching allows MySQL to start correctly. Only thing I can come up with is that somehow libnss-mysql is not returning the UID & GID to the MySQL daemon correctly, but somehow nscd is correcting the data? Logs to look at would be the MySQL log, with full debugging enabled and the system security log to see if there are any issues with authentication or any issues with accessing files. In the boot log just look to see if the network comes up after MySQL. |
ughnz (8297) | ||
| 632767 | 2008-03-07 23:34:00 | Odd, It does sound like you do not have the local GID / UID for MySQL synced correctly with the auth DB and maybe MySQL cannot get correct access to one of it's control files as there is a mixture of GID / UID? which would explain why it will not even work off the local passwd / group data.This cannot be the case. The MySQL database managing users & groups does not contain the information for MySQL - this is stored in passwd/group only, forcing it to fallback every time. I did this in an attempt to work around possible issues with libnss-mysql, but it doesn't seem to have helped. The UID/GID in passwd & group match the original UID/GID that MySQL was installed with. Even if the above is true it still would not explain why enabling nscd with caching allows MySQL to start correctly.Agreed, it's very weird. Only thing I can come up with is that somehow libnss-mysql is not returning the UID & GID to the MySQL daemon correctly, but somehow nscd is correcting the data?That's a thought. I have also tried starting mysqld manually, and it spits out a stack trace and a bunch of stuff about glibc. Googling it gets me nowhere. Nor did upgrading MySQL & glibc. Logs to look at would be the MySQL log, with full debugging enabled and the system security log to see if there are any issues with authentication or any issues with accessing files.I'll see what I can do here when I get home this evening. In the boot log just look to see if the network comes up after MySQL.The network comes up before MySQL, and it's definitely working, because my nfs exports are mounted correctly. |
Erayd (23) | ||
| 632768 | 2008-03-08 00:02:00 | Are you using the statically or dynamically linked version of MySQL? I wonder if the you are using the statically linked version and you are having a glibc conflict? |
ughnz (8297) | ||
| 632769 | 2008-03-08 00:41:00 | Are you using the statically or dynamically linked version of MySQL? I wonder if the you are using the statically linked version and you are having a glibc conflict?Statically linked version, and the error message did say something about that. It reckoned upgrading glibc would fix the problem though, and it didn't. |
Erayd (23) | ||
| 632770 | 2008-03-08 00:51:00 | Statically linked version, and the error message did say something about that. It reckoned upgrading glibc would fix the problem though, and it didn't. Maybe try the dynamically linked version? or do a source build? At least it looks like the solution is coming a bit closer? |
ughnz (8297) | ||
| 632771 | 2008-03-08 01:32:00 | Maybe try the dynamically linked version? or do a source build? At least it looks like the solution is coming a bit closer?Source build will be the next step, although I don't much like the idea of non-tracked files crapping all over my system :(. Thanks very much for the help so far :thumbs: :clap |
Erayd (23) | ||
| 632772 | 2008-03-08 06:04:00 | If you do recompile it might be an idea to use the Debian build system. "apt-get source <blah>" can be used to get a package and "dpkg-buildpackage -rfakeroot" in the source directory should build it. Make sure all build dependencies are installed in advance. | TGoddard (7263) | ||
| 1 2 | |||||