Here is a quick summary of what happened in the past 8 hours:
An admin mistake (SQL command update result set outcome=6;validate_state=2 where id=84114386;) accidentally set all the results in the database into an outcome=validate error state (the first semicolon in the command should be a comma!).
Show me someone who say's they have not done that kind of thing and I'll show you a liar.
Looks like you have done a good job of recovery and also a big thanks from me for
running such a stable and trouble free project - From the crunchers point of view. I can imagine it gives you a few headaches though.
Warning! This post contains atrocious spelling, and terrible grammar. Approach with extreme edginess.
It's not the speed, but the quality - Until I get a faster computer
An admin mistake (SQL command update result set outcome=6;validate_state=2 where id=84114386;) accidentally set all the results in the database into an outcome=validate error state (the first semicolon in the command should be a comma!).
Show me someone who say's they have not done that kind of thing and I'll show you a liar.
Looks like you have done a good job of recovery and also a big thanks from me for
running such a stable and trouble free project - From the crunchers point of view.
Thank you very much for the kind comments. We try hard not to make mistakes, but we're human!
You'll get to love the --i-am-a-dummy mysql client setting. Also available with a less offensive name under --safe-updates. If you do an UPDATE without a WHERE clause, it will give an error. Saved my a** a couple of times.
I think you can set it in my.ini under the [client] section, to make it the default.
You'll get to love the --i-am-a-dummy mysql client setting. Also available with a less offensive name under --safe-updates. If you do an UPDATE without a WHERE clause, it will give an error. Saved my a** a couple of times.
I think you can set it in my.ini under the [client] section, to make it the default.
So far it's been sent out six times. I know my machine is
stable (1 yr on EAH), and at least one other wingman
is stable too. Both got errors anyway. Help!
The trouble is that with this bug there are very few workunits that can't be finished valid with the 4.07 App (probably the 4.09 Linux Beta had the same problem, which should be fixed in 4.12).
RE: Here is a quick summary
)
Show me someone who say's they have not done that kind of thing and I'll show you a liar.
Looks like you have done a good job of recovery and also a big thanks from me for
running such a stable and trouble free project - From the crunchers point of view. I can imagine it gives you a few headaches though.
Warning! This post contains atrocious spelling, and terrible grammar. Approach with extreme edginess.
It's not the speed, but the quality - Until I get a faster computer
So true. This is the first
)
So true. This is the first downtime I can remember for quite some time, and most participants probably didn't even notice it because of work caches.
CU
H-BE
RE: RE: An admin mistake
)
Thank you very much for the kind comments. We try hard not to make mistakes, but we're human!
Cheers,
Bruce
Director, Einstein@Home
It happens. Reminds me of
)
It happens. Reminds me of some server mistakes I made when I was really tired. Great job getting it fixed so quickly!
You'll get to love the
)
You'll get to love the --i-am-a-dummy mysql client setting. Also available with a less offensive name under --safe-updates. If you do an UPDATE without a WHERE clause, it will give an error. Saved my a** a couple of times.
I think you can set it in my.ini under the [client] section, to make it the default.
RE: You'll get to love the
)
Good idea -- I will pass this on to our admin!
Bruce
Director, Einstein@Home
One of my WU's got hit
)
One of my WU's got hit too:
http://einsteinathome.org/workunit/34956676
So far it's been sent out six times. I know my machine is
stable (1 yr on EAH), and at least one other wingman
is stable too. Both got errors anyway. Help!
RE: One of my WU's got hit
)
Ouch!
The trouble is that with this bug there are very few workunits that can't be finished valid with the 4.07 App (probably the 4.09 Linux Beta had the same problem, which should be fixed in 4.12).
BM
BM
My first validate
)
My first validate error:
wuid=35000079
Another one:wuid=35044433
)
Another one:
wuid=35044433