To Monkey:
I agree on closing. Mine also seems to be working as expected now.
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I´ve closed this bug seeing the last comment.
Thank You for making Ubuntu better.
** Changed in: ubuntu
Status: New => Fix Released
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification because you are a member of Ub
Ok, upgraded my server today and seems like the problem is fixed.
Start-Date: 2010-08-02 18:16:54
Upgrade: mysql-client (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6),
mysql-client-core-5.1 (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6),
mysql-server-5.1 (5.1.41-3ubuntu12.5, 5.1.41-3ubuntu12.6), mysql-clie
"and runlevel[2345]"
should be
"and runlevel [2345]"
You need the space.
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Max,
curious...I should have mentioned this earlier.
"and runlevel[2345]"
I checked the original installed scripts in /etc/init/mysql.conf for
three machines and none of them have that conditional. However, some
other scripts do use it, and it apparently works there. Perhaps this is
another issue
Experienced this problem following a simple upgrade of a few packages
including mysql (see below). Afterward mysql did not start on boot.
I tried appending "IFACE=lo" to "net-device-up" as recommended above,
but this made no difference. To fix I had to remove the line "and
runlevel[2345]".
Not su
Will, that probably explains why your fix works. As I don't know the
logic in starting the interfaces, it may be possible that lo is
sometimes not the first to start and that caused your issue. Hopefully,
my description may allow others to determine where their problem is at.
Also, I do have a not
GerryG
In my.cnf I bind to 127.0.0.1 as I do not need external connections to
mysql for this particular server. Thanks for the reasoning and posts.
Will
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification because you are
Will Brooks,
I had assumed that "net-device-up" conditioned on only the first, which would
likely be "lo". But, perhaps not. I'll try that IFACE=lo. The following
explains my reasoning.
Could you tell me your bind for mysqld in /etc/mysql/my.cnf, from the
four options below? There are some sligh
GerryG, you mention this but I wanted to confirm that it worked for me.
I changed /etc/init/mysql.conf
start on (net-device-up
and local-filesystems
and runlevel[2345])
stop on runlevel [016]
to
start on (net-device-up IFACE=lo and local-filesystems)
stop on runlevel [016]
T
As shown in
http://ubuntuforums.org/showthread.php?t=1470738
many people are effected by this, if mysqld must be bound to an interface other
than "lo". Most of the problems appear to results from a timing issue, where
upstart attempts to start the mysqld daemon before the specific network
interf
I believe this thread is relevant:
http://ubuntuforums.org/showthread.php?t=1470738
Their solution is not adequate for me because I do not wish to bind
mysql to eth0.
--
Upstart does not successfully start mysql on boot
https://bugs.launchpad.net/bugs/610085
You received this bug notification b
12 matches
Mail list logo
