s which contain your precious data!
070201 4:30:42 [ERROR] Can't init databases
070201 4:30:42 [ERROR] Aborting
070201 4:30:42 [Note] /usr/sbin/mysqld: Shutdown complete
070201 04:30:42 mysqld ended
070201 04:35:21 mysqld ended
At 04:30, my server makes the
I am running mysql version 3.23.47 on a RedHat Linux 6.2 box with very
low loading. The Linux is acting as a gateway for my company which
connects to an ISP via ADSL.
The daemon safe-mysqld and mysqld keep shutting down
accasionally,especially when ADSL disconnects.
-
Hi!
On Nov 16, Erik Price wrote:
> Until the next release is available, I must use the
> dreaded "kill -9" shell command to shut down the MySQL daemon, which
> may corrupt data in the database
It shouldn't if you'll execute FLUSH TABLES before.
Actually,
mysqladmin shutdown && sleep 60 && k
Hello all,
As I have written about in two earlier threads this week (you can read
them in the mysql.com archives at these URLs:
http://lists.mysql.com/cgi-ez/ezmlm-cgi?1:sss:91326#b
and
http://lists.mysql.com/cgi-ez/ezmlm-cgi?1:sss:91495#b
), I am unable to execute the "shutdown" command in my
Dan,
Thanks for that comprehensive answer. It doesn't seem like the FreeBSD
solution will be one that I will try to implement into my installation
of Darwin, as it draws on skills and knowledge that I definitely don't
have -- though it would be educational to take a look into Darwin's
threading
In the last episode (Nov 14), Erik Price said:
> > What OS do you use ?
> >
> > The behaviour you're describing I've seen two-three years ago on
> > FreeBSD due to some bug/deficiency in FreeBSD threads. Since then
> > it was fixed (in FreeBSD I mean).
>
> Interesting! I'm using Darwin 1.3.1 (f
If I remember correctly, on SCO I did a
mysqladmin shutdown | mysqladmin
This produced an error message, but also unblocked the shutdown.
Erik Price wrote:
> --- Sergei Golubchik <[EMAIL PROTECTED]> wrote:
>
>> What OS do you use ?
>>
>> The behaviour you're describing I've seen two-three ye
--- Sergei Golubchik <[EMAIL PROTECTED]> wrote:
> What OS do you use ?
>
> The behaviour you're describing I've seen two-three years ago on
> FreeBSD
> due to some bug/deficiency in FreeBSD threads.
> Since then it was fixed (in FreeBSD I mean).
>
> Regards,
> Sergei
Interesting! I'm using D
On Wed, 14 Nov 2001 08:38:04 -0800, Bill Adams <[EMAIL PROTECTED]> wrote:
>>> /usr/local/mysql/bin:mysql$ mysqladmin -u root -p shutdown
>>>
>>> But this one doesn't work for me, even though I am using the proper
>>> password and am the proper user. Executing this command just leaves me
>>> ha
Hi!
On Nov 14, Bill Adams wrote:
> >
> > PS: If I run the mysqladmin shutdown command, then check "top" in
> > another console, both the daemon and the mysqladmin command continue to
> > run indefinitely -- and I have waited an hour to see if it's just slow.
> > That doesn't seem to be the case
--- "Mike(mickalo)Blezien" <[EMAIL PROTECTED]> wrote:
> Have you tried ./mysqladmin -u root -p shutdown
>
> when in the 'bin' folder otherwise typing mysqladmin, it will check
> the server
> PATH, to find the mysqladmin
>
>
> Mike(mickalo)Blezien
Hmm... isn't this the same thing as /usr/local/
--- Bill Adams <[EMAIL PROTECTED]> wrote:
> This seems like an OS bug to me. All of the things you mention in
> your last
> email should stop mysql from running.
>
> What happens if you do (where safe_mysqld is running) 'fg' and
> then CTRL+c? Does that just hang too?
>
> Do you need the debug
>
> PS: If I run the mysqladmin shutdown command, then check "top" in
> another console, both the daemon and the mysqladmin command continue to
> run indefinitely -- and I have waited an hour to see if it's just slow.
> That doesn't seem to be the case.
>
This seems like an OS bug to me. All o
--- Bill Adams <[EMAIL PROTECTED]> wrote:
> > One option is to use
> >
> > /usr/local/mysql/bin:mysql$ mysqladmin -u root -p shutdown
> >
> > But this one doesn't work for me, even though I am using the proper
> > password and am the proper user. Executing this command just
> leaves me
> > hangi
Erik Price wrote:
> All,
>
> Well, I solved the mystery of the missing Unix socket. It needs to be
> defined at the time the daemon is started with:
> --socket=/path/to/socket. Well, at least in my installation it does.
>
> But now I'm having the OPPOSITE problem -- shutting down the server
>
All,
Well, I solved the mystery of the missing Unix socket. It needs to be
defined at the time the daemon is started with:
--socket=/path/to/socket. Well, at least in my installation it does.
But now I'm having the OPPOSITE problem -- shutting down the server
(the daemon). I've searched the
On Thu, Dec 21, 2000 at 09:22:40PM +0200, Sinisa Milivojevic wrote:
> Lutz Jaenicke writes:
> > On Thu, Dec 21, 2000 at 07:30:23PM +0200, Sinisa Milivojevic wrote:
> >
> > 1. It doesn't help (no surprise, as this would have meant that HP's compiler
> >and gcc having the same problem which
17 matches
Mail list logo
