134.139.127.31 Cannot connect to work server

[jwwPhotos]

I did do the steps in Do this First.

I CAN open http://134.139.127.31 via my brower and get the OK

I CAN ping to 134.139.127.31 as well via IPconfig

I have tried this with and without my router to my DSL modem

My router is a DLINK DIR 655

I have tried this with my firewall disabled on all steps above

I have been able to successfully send other WU's within the same timeframe of failures.

I have rebooted

I have restarted my client

My client is CPU 6.23

I have -verbosity 9 enabled as well as DO NOT LOCK to specific core as I have a quad CPU

Code: Select all

[01:51:48] + Attempting to send results [October 22 01:51:48 UTC]
[01:51:48] - Reading file work/wuresults_06.dat from core
[01:51:48]   (Read 6346264 bytes from disk)
[01:51:48] Connecting to http://134.139.127.31:8080/
[01:51:48] - Couldn't send HTTP request to server
[01:51:48] + Could not connect to Work Server (results)
[01:51:48]     (134.139.127.31:8080)
[01:51:48] + Retrying using alternative port
[01:51:48] Connecting to http://134.139.127.31:80/
[01:51:48] - Couldn't send HTTP request to server
[01:51:48] + Could not connect to Work Server (results)
[01:51:48]     (134.139.127.31:80)
[01:51:48] - Error: Could not transmit unit 06 (completed October 11) to work server.
[01:51:48] - 73 failed uploads of this unit.

As far as all 6 queues waiting for the same server? No.. I have them all reported in their individual threads as required by the Do This First

The reason I had a post up above that listed several servers was because you had asked and I posted ALL errors to all servers so you could get an idea of my issues. Again, I also have them reported in each separate thread as I realize that different persons are responsible for different servers. So no worries that the responsible parties will not find those.

If you would like I can PM you the entire list of failed transmissions concerning all 6 queues.

Hope this helps!
jww

[toTOW]

With all the network issue you have, are you sure that your ISP is not blocking something (I've often seen proxies that can download, but produce errors on upload) ?

[jwwPhotos]

That's not a bad thought, but if the IP is blocked by my ISP I would not be able to ping to it as well as get the OK via the browser. I can hit the server just fine.

It is my feeling the folding client times out before the server responds to the send request for some reason. I think whoever is admin to these servers might possibly find root cause if they inspect their logs.

It simply sounds worse than it is as last time I checked of all that I have reported in the 6 queues failing, ALL but 2 (this being one of them) are listed on the server status as REJECT.

The good news is I still have other queues finish their WU's and able to successfully send work back to other servers.

Hope this helps.

[bruce]

When you see a server status of REJECT, there's no point in saying anything beyond an initial report which might lead to an earlier reset of the server than if nobody reports it. Even that initial report is questionable, however, since [some? all?] servers automatically reset themselves after some period of inactivity.

It's probably worth concentrating on those clients which are trying to upload to a server that looks good on serverstat and which responds "OK" in your browser to see if we can identify problems with your firewall or something like that.

[jwwPhotos]

Gotcha..

However just to be clear, this particular server's status says it is working fine which is why I left the detail in my post from Wed Oct 21, 2009 11:46 pm.

Please reread that post and let me know if you have any suggestions.

[bruce]

With all the network issue you have, are you sure that your ISP is not blocking something (I've often seen proxies that can download, but produce errors on upload) ?

Are the failed uploads larger than the ones which successfully upload? It's possible that your ISP blocks files larger than a certain size.

Is your client configured for Small/Normal/Big WUs? Try configuring it for Big and then do a -send all -verbosity 9

[jwwPhotos]

Bigger? Hmmm in looking.. some yes, some no, but I have been sending larger files than any of these for quite some time without any issues. I bascially have a commercial account and have no restrictions of any sort.

By looking at the log file, the entire send process for all 6 queues to fail takes all of 10 seconds. If there was a limit on my ISP, it would fail after transmitting for some time as it would send until it hit that limit.

I will make the client changes you suggest and reboot and let you know what I find. Rather than giving those results now, I will give it till tomorrow afternoon running these new changes and post an update.

Thanks so much for your help!
jww