Hi all,
mysql db has been starting in safe mode for 12 hours. I don't know if I
should stop it or if I do, what will happen. I'm hoping one of you can
help.
Here's how I got into this mess:
After a operating system change (CentOS 5 to CentOS 6), my Python script
could no longer connect with
Am 20.08.2014 um 16:39 schrieb Augori:
However, it's been 12 hours now and the thing is still restarting in safe
mode and I can't tell if it's making progress. The command I typed was
/usr/bin/mysqld_safe --skip-grant-tables
I think I forgot to include the ampersand () at the end which
Thanks! But if it's running in the background, how will I know when it has
completed?
On Wed, Aug 20, 2014 at 11:04 AM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 20.08.2014 um 16:39 schrieb Augori:
However, it's been 12 hours now and the thing is still restarting in safe
mode and I
Am 20.08.2014 um 18:55 schrieb Augori:
Thanks! But if it's running in the background, how will I know when it has
completed?
completed what?!
http://www.catb.org/esr/faqs/smart-questions.html#beprecise
what did you not understand in the paragraph below?
mysqld_safe has *nothing* to do
Hi All,
when I use the bg command, it says
1 job already in background
and continues to run in the foreground.
On Wed, Aug 20, 2014 at 11:04 AM, Reindl Harald h.rei...@thelounge.net
wrote:
Am 20.08.2014 um 16:39 schrieb Augori:
However, it's been 12 hours now and the thing is still
Am 21.08.2014 um 01:05 schrieb Augori:
when I use the bg command, it says
1 job already in background
and continues to run in the foreground.
*bullshit* if it is running in foreground you can't enter
anything because your terminal would be blocked, the bg
command only works if you
Maybe it's because I'm accessing it through a C Panel SSH Shell that it
acts differently than you expected. It doesn't matter anyway… I was able
to exit the shell and regain control of my shell. I'm giving up on the
upgrade approach for now, so let's consider this conversation concluded.
On
