Linux client unable to send blocks.
I haven't been able to send a block back yet! So far I've gotten maybe 15 or 20 of these. It's able to connect to the server to retrieve the proth test, but then can't connect to submit the finished block. Very irritating, since I'm not helping the project at all if my processed data sits in the submit queue forever :( Here is what I see:
[Fri Jan 2 16:31:32 2004] client process [v1.2.1] invoked
[Fri Jan 2 16:31:32 2004] priority set to idle
[Fri Jan 2 16:31:32 2004] connecting to server
[Fri Jan 2 16:31:32 2004] logging into server
[Fri Jan 2 16:31:32 2004] requesting a block
[Fri Jan 2 16:31:35 2004] got proth test from server (k=55459, n=5351626)
[Fri Jan 2 16:31:35 2004] server packet cached to disk
[Fri Jan 2 16:31:35 2004] AMD Athlon(tm) Processor detected. Enabling cpu specific optimizations.
[Fri Jan 2 16:57:38 2004] resolving hostname
[Fri Jan 2 16:57:38 2004] opening connection
[Fri Jan 2 17:00:47 2004] temporarily unable to connect to server -- block added to submit queue
[Fri Jan 2 17:04:21 2004] iteration: 10000/5351642 (0.19%) k = 55459 n = 5351626
I hope it can be solved! Thanks!
Linux version 1.2.0 (sb.bz2)
I've downloaded sb.bz2 and it appears to work fine.
1) On my dual Athlon (RedHat 9) system it appears to run a hair slower 247 down from 250. Time will tell.
2) Doesn't appear to leave network connection file open, which is a good thing.
3) I will monitor to see if it is restarted by sbwrap. Prior versions would need to be restarted a couple times a day (on average).
Thanks.
Linux version 1.2.0 (sb.bz2) update
So far no core dumps, but the linux client (sb.bz2) still occasionally "hangs" on communication with the host. In each case the last line logged is "Receiving from server" the next line should be "Logging into server", but that was never logged.
I think this loss of communications may be related to high network activity (on this side). Two RedHat linux sb clients had been running without problems for almost 24 hours. I added two additional linux sb clients to a newly booted SuSE machine. I then started up a SuSE update adding a lot of packages to the installlation (it took over two hours to complete the update). Three of the four linux sb clients experienced a "hang" during that period (Both SuSE and one RedHat). All of the "hangs" had the "receiving from server" message as their last log message.
If I can do anthing else to help let me know.
Thanks.
Re: Linux version 1.2.0 (sb.bz2) update
Quote:
Originally posted by poundsja
So far no core dumps, but the linux client (sb.bz2) still occasionally "hangs" on communication with the host. In each case the last line logged is "Receiving from server" the next line should be "Logging into server", but that was never logged.
I think this loss of communications may be related to high network activity (on this side). Two RedHat linux sb clients had been running without problems for almost 24 hours. I added two additional linux sb clients to a newly booted SuSE machine. I then started up a SuSE update adding a lot of packages to the installlation (it took over two hours to complete the update). Three of the four linux sb clients experienced a "hang" during that period (Both SuSE and one RedHat). All of the "hangs" had the "receiving from server" message as their last log message.
If I can do anthing else to help let me know.
Thanks.
yeah, this is quite common right now and we know about it.. hopefully that will be fixed :)