Summary: | mysql does not start up properly | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Daniel <deepee> |
Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 175783 | ||
Bug Blocks: | |||
Attachments: | SysV Init output |
Description
Daniel
2007-04-01 22:37:46 UTC
i doubt apache has anything to do with it ... once you boot up, if you run `/etc/init.d/mysql status`, does it show a similar error ? You are so right: during boot-up init.d reports: * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (0) [ !! ] Although mysqld is running, "/etc/init.d/mysql status" reports the above error, too. I think the previously described problem (apache/mysql) is is a kind of side-effect regarding my very complex service-setup: - local slapd, local nsswitch.conf configured to use pam_ldap and nss_ldap - local named chrooted The following services do not start up properly: named (chroot) mysql (don't know exactyl why, I think it has to do with not running named) asterisk (depend use mysql) apache2 (depend use mysql) mit-krb5kdc (because default realm is configured in DNS-Zone, and named is not started) mit-krb5kadmin (because kdc has not been started) Any other services startup quite fine. Just one more question: What is the reason named is started first (before any other service?). I thought slapd is more "important", because it resolves the chroot-lookup via nsswitch.conf, to allow named to be started chrooted? slapd is configured using IP addresses only so it does not depend on a working DNS. Just for your information I attach the init.d-output during boot-up (from serial console) into an attachment, so you can see the order the services will be started. Created attachment 115312 [details]
SysV Init output
The issue is with the mysql init script - the one on bug #175783 should fix this. *** This bug has been marked as a duplicate of bug 175783 *** |