Hi,
is there any solution to this major issue (mysql serever not working in
ubuntu 10.04) ?
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Assignee: Canonical Server Team (canonical-server) = Chuck Short (zulcss)
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of
Targeting to 10.04.1 as mysql is a very popular server application. If
a solution cannot be found in time, then it needs to be targeted to an
SRU or 10.04.2.
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Importance:
Does ANYONE have a solution for: ERROR 2002 (HY000): Can't connect to local
MySQL server through socket '/var/run/mysqld/mysqld.sock'
Can I install an old version or something? I MUST get this server up. Nothing
will get it to run.
--
infinite loop in /etc/init/mysql.conf if mysqld is not
On 7 July 2010 05:34, stininkey skunkenheimer jdie...@twonails.com wrote:
Does ANYONE have a solution for: ERROR 2002 (HY000): Can't connect to local
MySQL server through socket '/var/run/mysqld/mysqld.sock'
Can I install an old version or something? I MUST get this server up. Nothing
will
In my case it must have been webmin that's put something in the my.cnf
file that it doesn't like.
I'll have to find out what it doesn't like and file a separate bug
against webmin, as the cause - but meanwhile I can confirm there is a
bug with the startup script. It doesn't fail gracefully, just
Oh - the startup problem is disguised as a permissions problem, but
actually it's because the db file is on an NTFS partition - so it's not
webmin.
But - a startup error would be nice...!
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
The bug doesn't exist in Debian since they don't use Upstart - OT, but
IMHO it was way too early to introduce Upstart since it doesn't even
provide the same level of functionality as SysV, but that's another
story... The important thing when migrating though is not to make
assumptions when
Hit the same issue, when there was a typo in my.cnf, mysql-server is a
stuck in an infinite post-start loop.
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of Ubuntu
Server
I will try to describe all what I have find on this problem which start
with the upgrade from 8.04 to 10.04.
First (I forgot how the problem began...), I remove mysql-server :
$ sudo apt-get remove mysql-server --purge
$ sudo apt-get autoremove
$ sudo apt-get autoclean
and I also remove the
Not sure how I did it, but I succeeded in removing the password for
root. I can now connect to the database. But if I try to change the root
password of mysql using sudo dpkg-reconfigure mysql-server-5.1, I get
:
stop: Unknown instance:
and another loop I can break with Ctrl+C. And the password
just my 2 cents: The problem was (in my case) that at the time mysql
upstart job is fired /var/run isn't mounted. There should be a tempfs in
/var/run. Additional apparmor prevents mysql to put its sock under
/var/run instead of /var/run/mysqld.
How can I tell upstart to start after
@Mr. Bug - I think you've got other problems if /var/run is not mounted
by the time mysql starts. And mysql is already set to start after all
local filesystems.
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug
How about the attached upstart job?
** Attachment added: mysql.conf
http://launchpadlibrarian.net/49996397/mysql.conf
** Attachment removed: mysql.conf
http://launchpadlibrarian.net/49996397/mysql.conf
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
Sorry, slight modification
** Attachment added: mysql.conf
http://launchpadlibrarian.net/49996491/mysql.conf
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of Ubuntu
Server
@Chuck - preliminary testing seems to indicate that the upstart job in
your package will allow mysql to enter started status even when it does
not start successfully. I'll try look at creating something a little
cleaner in the next couple of days.
--
infinite loop in /etc/init/mysql.conf if
Please note that the cause of the problem is that /etc/init/mysql.conf
is trying to start mysqld as user root. If you start as user mysql
everything works fine.
The infinte loop described above in
while ! /usr/bin/mysqladmin --defaults-file=$HOME/debian.cnf ping
do
sleep 1
done
When using EBS snashots on EC2, debian-sys-maint is different on new
servers, so it stuck forever.
Also init/mysql.conf use:
exec /usr/sbin/mysqld
and I see error when running it like that:
100528 11:00:25 [ERROR] Fatal error: Please read Security section of the
manual to find out how to
I'm experiencing the same hang. But it also hangs on stop/restart when
there is an error in the my.cnf. This is really annoying..
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member
I updated to version 5.1.41-3ubuntu12.1 yesterday and my problems with
mysql hanging on start up have gone away.
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of Ubuntu
Server
@Sam Barker - you must have inadvertently fixed whatever error was
causing the /usr/bin/mysqladmin --defaults-file=$HOME/debian.cnf ping
command to fail. Try breaking your my.cnf as others have suggested, and
you'll see the infinite loop still exists.
** Tags added: regression-release
--
I'll take that back. Its failing again after a reboot.
After I get the hung instance stopped sudo dpkg-reconfigure mysql-
server-5.1 fixes the problem until reboot.
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug
Nominating for Lucid per zul's request
** Also affects: mysql-dfsg-5.1 (Ubuntu Lucid)
Importance: Undecided
Status: New
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member
For those who are having problems with this can you try the version in
my ppa when it builds:
https://edge.launchpad.net/~zulcss/+archive/server-bug-fixes
thanks
chuck
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this
Infinite loop is bad - kills my HA clusters if there's an error, as the
service cannot be migrated away from the node with the issue. Certainly
propose re-instating the limit, as this is a regression.
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
On Wed, May 05, 2010 at 03:17:12PM -, Joe Holloway wrote:
As a side note, I've now completely lost my /etc/init/mysql.conf file
and can't seem to get it back through the package manager regardless of
purging/reinstalling packages. That concerns me a bit, but I can't
pinpoint the
In the old /etc/init.d/mysql script, there was a similar check status
loop, but it only spun 14 times before exiting. If there were a
problem with your server, you'd only block for max of ~14 seconds while
trying to ping the server before breaking out.
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13
This affects me as well.
in /etc/mysql/conf.d there was a symlink to /home/user/my.cnf[mysql]
-begin my.cnf
default-character-set = utf8
[mysqld]
default-character-set = utf8
character-set-server = utf8
character_set_database =
I have the same problem in a clean install of 10.04 (iso downloaded
today). I believe I had the same problem when I did an upgrade of 9.10
to 10.04 yesterday - I had to kill the install of mysql-server which had
hung, but I've done the complete install today.
Synaptic hangs on start mysql and the
The skip-bdb option is no longer supported in mysql 5.1.
Was the original hardy my.cnf file modified before the upgrade? If so
dpkg should have prompted you to review the changes between between the
locally modified hardy version and the new maintainer lucid version of
my.cnf.
** Changed in:
Comparing old and new I don't think there were any changes, although
there is a 'log' entry that might not have been original. I do not
recall seeing any prompt on this but it's possible that I missed it -
the upgrade from 8.04 to 10.0.0.4 was a long process, and a lot of it
ran overnight while I
Could paste a diff between your old hardy my.cnf file and the lucid one?
--
infinite loop in /etc/init/mysql.conf if mysqld is not running.
https://bugs.launchpad.net/bugs/551130
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Here 'tis. my.cnf is a copy of my.cnf.pkg-dist and my.cnf.old is my
old one. I should say that it is possible that I was asked about
whether to keep the old one or install the new one, and I might have
said keep the old one. I just don't recall.
$ diff my.cnf my.cnf.old
29a30,40
33 matches
Mail list logo
