I followed the tutorial and setup local nr and nt databases and was able to get them working on the web interface, and was able to link them to my blast2go, and select the local server as a www-blast database.
A problem I am encounter however, is that no matter what I blast, i get no results returned. When I blast manually on the web server, I get a result, when I feed it to blast2go, and start the blast, everything gets no results returned.
This is somewhat odd. I even tried asking for my server for an Blast XML response, when I used the web server to search, and that worked just fine.
There is not much to go on, since there is no error anywhere... I was wondering if you had encountered this before? blast on NCBI right now works horrible for me, sometimes 5-10 minute per query... so I need to get the local one working asap.
My properties file for blast2go show: Blast.url=http://137.122.148.173/blast/blast.cgi Blast.urls=http://www.ncbi.nlm.nih.gov/blast/Blast.cgi,http://137.122.148.173/blast/blast.cgi Blast.blastdb=nt
Thank you for your time. Adrian
P.S. The URL is not accessible externally, only for people on intranet, but blast is run from a machine that has access to intranet. Hopefully that doesn't screw things up, there are no proxies setup.
EDIT1 Re-posted on: http://seqanswers.com/forums/showthread.php?p=123017 https://groups.google.com/forum/#!topic/blast2go/id6FnS3wVuU
find and read the access and error logs of your server, the answer will be there
It's not that simple. I am blasting stuff right now, and getting no results returned, and yet the apache error log shows errors from November 19th:
So this does not show up at every single blast attempt.
troubleshooting a system that is not accessible to the outside world and one that you cannot post an error for is not particularly enticing - you need to formulate "answerable" questions
You are right, troubleshooting without errors can be challenging. There is no sign of problems in the httpd access and error logs because there is no problem with httpd.
From the blast2go log i see:
When I actually go an issue that command:
I get the result in xml format:
So the problem is in blast2go reading the output. It doesn't seem to be a timeout issue based on how long it takes blast2go to decide there is no results and how long it takes me to get the results. The time is identical.
I was wondering if someone who linked blast2go with local www-Blast perhaps ran into something similar and found a solution.
If you want to run the analysis faster why can't you run the blast on command line and generate a XML output and import the blast xml output into blast2go.
Brilliant. outfmt 5.