Jeff,

Yes, you are right.
I read this mail after sent answer to original from Ethan:)
So, read my answer.

Igor

Jeff Squyres wrote:
After looking through the logs, Ethan and I *think* that this was just a query that was too large (i.e., it used too much CPU, and therefore it was killed).

Can someone with a little more knowledge than us have a look at the logs and let us know if we're right?


On Feb 11, 2010, at 2:05 PM, Ethan Mallove wrote:

  
Hi,

I'm getting a 500 Internal Server Error using bquery.pl.  I can --ping
successfully:

  $ client/bquery.pl --ping --server=http://open-mpi-mtt.appspot.com/ --password=xxxxx --username=sun
  Ping is successful.

But an actual query gets an error:

  $ client/bquery.pl --server=http://open-mpi-mtt.appspot.com/ --password=xxxxx --username=sun --query --gqls="select * from TestRunPhase where status=1" --dir="bquery-test"
  Error at http://open-mpi-mtt.appspot.com//client
  500 Internal Server Error

-Ethan
_______________________________________________
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel

    

  


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4859 (20100211) __________

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru

Reply via email to