anteater.blueprint.org:80 ?????

[PinHead]

Why does this address keep showing up in my log files?

At first I thought it was just a DNS issue that would be resolved in a day or so.

But now every week or so, the client (ncbi) tries to connect to this address.

<shrug>?
---------------

Sun Nov 9 00:47:47 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Sun Nov 9 01:11:54 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Sun Nov 9 16:54:27 2003 ERROR: [777.000] {ncbi_socket.c, line 1255} [SOCK::s_Connect] Failed pending connect to anteater.blueprint.org:80 (Timeout) {errno=115,Operation now in progress}
Sun Nov 9 16:54:27 2003 ERROR: [777.000] {ncbi_connutil.c, line 799} [URL_Connect] Socket connect to anteater.blueprint.org:80 failed: Timeout
Mon Nov 10 03:07:30 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Mon Nov 10 03:46:48 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Mon Nov 10 07:41:11 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates
---------------

[rsbriggs]

Sun Nov 9 00:47:47 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Sun Nov 9 01:11:54 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Not related to the question you asked, but, did you notice that the node that you extracted the log entries from is non-functional? That's a fatal error which, so far as I know, requires starting over from a clean install...

[tpdooley]

the can't set coordinates error is just informational (my error logs are littered with the things and I'm getting the points I'd expect); the can't find anteater error is something I see on my various machines when my wonderful ISP decides to disconnect us..

[Stardragon]

Not to worry, anteater.blueprint.org is dedicated to your result uploads. We have been re-architecting some things on our end, so this is just one of the changes.
All it really means is that your connection timed out, but the address is correct.

With respect to the "cannot set co-ordinates" error, it is harmless, as stated on our Bugs&Fixes page. It had appeared because of a structural difference of the current protein, and we are addressing the issue so it will not recur in the future. However, it has no ill effect on your results.

[PinHead]

Not sure if I totally agree with the "harmless" part of it. It seems that when the coordinates error shows up repeatedly, my production goes down until a restart occurs. If it shows up once or twice and then continues without anymore coordinate errors, the production seems normal.



This ofcourse is just an observation and I have done no real testing of the theory!

[Brian the Fist]

You are actually somewhat correct, however it is the other way around..

You see that error occurs only when the protein gets really stuck and it times out a lot. If you'd only told us this 2 weeks ago, I could have found it a lot faster