Quoting Manfred Antar <[EMAIL PROTECTED]>:
Manfred,
! ! IT WORKS ! ! for the first time is several weeks:-)
! THANKS !
I followed your steps and added a couple of my own below just in case someone
else is having problems.
|
| Ed
| I think i did this
| Build and install the gcc32 port
Quoting Manfred Antar <[EMAIL PROTECTED]>:
| At 08:54 AM 8/2/2002 -0700, Edwin Culp wrote:
| >This doesn't make much sense and is probably not related but I've had the
| >problem for about a month and thought it was going to go away but it
| hasn't.
| >I really don't know where to start loo
On Fri, 2 Aug 2002 10:08:47 -0700 (PDT)
Julian Elischer <[EMAIL PROTECTED]> wrote:
> there are several possibilities:
> 1/ do a ktrace on teh spinning process for a couple of seconds and see
> what syscalls it is doing.
stopped jikes with ctrl-c looks always like:
90998 sh RET read 65
Quoting Manfred Antar <[EMAIL PROTECTED]>:
| The same thing happend to me a few weeks ago when I did an upgrade from
| 3.23.49 ==> 3.23.51
| I think what I ended up doing was to use the gcc3.2 from ports, and I built
| it staticlly.
| First i installed gcc3.2 the made sure /usr/local/bin
there are several possibilities:
1/ do a ktrace on teh spinning process for a couple of seconds and see
what syscalls it is doing.
2/ if it's spinning in the kernel, you can drop into ddb
and do a
tr
to see where it is in the kernel...
c to continue..
do this several times to ge a sortof 'prof
Quoting Marc Recht <[EMAIL PROTECTED]>:
| > I really don't know where to start looking. Just after the KSE changes at
| > the beginning of July I upgraded mysql. Since then I have had
| intermittent
| > problems with mysql hanging far too often. It takes 100% of the resources
| > and has
At 08:54 AM 8/2/2002 -0700, Edwin Culp wrote:
>This doesn't make much sense and is probably not related but I've had the
>problem for about a month and thought it was going to go away but it hasn't.
>I really don't know where to start looking. Just after the KSE changes at
>the beginning of July
> I really don't know where to start looking. Just after the KSE changes at
> the beginning of July I upgraded mysql. Since then I have had intermittent
> problems with mysql hanging far too often. It takes 100% of the resources
> and has to be killed. I get no errors in the mysql log nor in t
