Summary: | dev-db/mysql-5.0.18-r30 won't restart - pid and sock are still present error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Scott <scott> |
Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | major | ||
Priority: | Highest | ||
Version: | 2005.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Scott
2006-02-03 11:28:32 UTC
the row 324 of /etc/init.d/mysql should be: while [[ -n "$PID" ]] \ please change it to while [[ -f "${pidfile}" ]] || [[ -n "$PID" ]] \ if this solve I will change the script Hello, Just changed it but it still doesn't work. I can only try it on the one box right now as the other is running a MEMORY table so I can't restart often. pluto ~ # /etc/init.d/mysql restart * Re-caching dependency info (mtimes differ)... * Stopping mysql (pid=) ... * Stopping mysqld (0) [ ok ] * ... "/var/run/mysqld/mysqld-500.pid" and/or "/var/run/mysqld/mysqld-500.sock" are still present. Please check that no server is running and remove them. [ !! ] pluto ~ # /etc/init.d/mysql restart * ... * Starting mysql (/etc/mysql/my.cnf) [ ok ] pluto ~ # /etc/init.d/mysql restart * Stopping mysql (pid=) ... * Stopping mysqld (0) [ ok ] * ... "/var/run/mysqld/mysqld-500.pid" and/or "/var/run/mysqld/mysqld-500.sock" are still present. Please check that no server is running and remove them. [ !! ] pluto ~ # /etc/init.d/mysql restart * ... "/var/run/mysqld/mysqld-500.pid" and/or "/var/run/mysqld/mysqld-500.sock" are still present. Please check that no server is running and remove them. [ !! ] pluto ~ # /etc/init.d/mysql restart * ... * Starting mysql (/etc/mysql/my.cnf) [ ok ] pluto ~ # ok thanks, now I'm pratically certain that under certain circumstances mysql don't delete the pid file, the next init script will remove it prior to start mysql. copy "http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/dev-db/mysql/files/mysql-slot.rc6-r3?rev=1.2" or $PORTDIR/dev-db/mysql/files/mysql-slot.rc6-r3 onto /etc/init.d/mysql and restart it. Please report success or not (In reply to comment #3) > ok thanks, now I'm pratically certain that under certain circumstances mysql > don't delete the pid file Yeah, confirmed here... pluto ~ # cp /etc/init.d/mysql /etc/init.d/mysql-bak; cp /usr/portage/dev-db/mysql/files/mysql-slot.rc6-r3 /etc/init.d/mysql pluto ~ # /etc/init.d/mysql restart * Caching service dependencies ... [ ok ] * Stopping mysql (pid=) ... * Stopping mysqld (0) [ ok ] * ... * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (1) [ !! ] pluto ~ # /etc/init.d/mysql restart * ... * Starting mysql (/etc/mysql/my.cnf) [ ok ] pluto ~ # /etc/init.d/mysql restart * Stopping mysql (pid=) ... * Stopping mysqld (0) [ ok ] * ... * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (1) [ !! ] pluto ~ # /etc/init.d/mysql restart * ... * Starting mysql (/etc/mysql/my.cnf) * MySQL NOT started (1) [ !! ] pluto ~ # /etc/init.d/mysql restart * ... * Starting mysql (/etc/mysql/my.cnf) [ ok ] pluto ~ # Scott, I've not been so clear, I've changed $PORTDIR/dev-db/mysql/files/mysql-slot.rc6-r3 without revbump, because I'm gathering bug fixes before to force a reemerge using "-r31" for mysql ebuilds, this is why I gave you the link to cvs sources. If you synced and are using the correct ebuild please provide more information on the service monitoring you're using in place of baselayout. (In reply to comment #7) .... > If you synced and are using the correct ebuild please provide more information > on the service monitoring you're using in place of baselayout. Obviously speaking of init.d _not_ of ebuild here Closing as there is no more slotted mysql in the tree, and this problem derived directly from that. Best regards, CHTEKK. |