Hi, Doug, Chris!
MySQL does not have "transaction" support (protection for writing at
the same time)... if two people try to write to the same table in the same
nanosecond or so (very unlikely), this might happen - my best guess.
I had spoken with Tim about a year and a half ago about this and we
decided it should not affect us too much - one solution would have been to
go with PostgreSQL, which does have "transaction" support and it is still
free. But MySQL was already installed and ROOT is very happy with MySQL
so...
It looks like this is what happened - maybe two elog sessions trying to
write at the same time to the RUN table? Or maybe not...
Anyway, maybe registering elog with the "process" table so that only the
first session can write would be a good solution. If this is already done,
then I do not know how the server got hung.
It sounds like either the MySQL server or blast05 got hung later on, as
rebooting blast05 solved the problem...
Adrian
> > Run log windows open but do not close properly otherwise everything
> > runs smoothly.
>
> i would guess that this is the same mysql problem? because they worked
> until mysql got overloaded. as a matter of fact, ALL of the fields
> should work now!
> --chris
>
> >
> >
> > Cheers,
> > Douglas
> >
> > 26-415 M.I.T. Tel: +1 617 258 7199
> > 77 Massachusetts Avenue Fax: +1 617 258 5440
> > Cambridge, MA 02139, USA E-mail: hasell@mit.edu
>
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST