Me G5 Mac has four completed yello tasks that ’ave been stuck at “Uploadin’” fer a few days. They be marked “No reply” in th’ database: should I abort them at me end? Would ye like me t’ try ’n copy th’ results afore doin’ so?

____________

Was that a Siren I heard?

Go ahead and abort them. There was not work for Mac in this round, though some machines got told otherwise. The older app version is in the database, but the
executable was not in the download area. If you had it already, fine, but if not, it would fail to download. I don't know if that is your problem or not.

I didn't make a version for Mac this time around because the Mac I use for it is dead, probably due to bad capacitors. I have repacement caps, and just need to find some time to open it up, remove the mother board, and then remove the bad caps and solder in new ones. Then cross my fingers and turn it back on.
____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Also, I think the IP address changed. I had to reboot my windows machines in order for them to be able to contact the project.
____________
Dublin, CA
Team SETI.USA

Also, I think the IP address changed. I had to reboot my windows machines in order for them to be able to contact the project.

Don't know what to say, but it did not work like that. They could not find the new address for several days. The only thing that worked was rebooting. This is with xp64, and 6.10.6.

FWIW, I see this problem any time any project changes the IP address. It SHOULD work as you say, but it doesn't.
____________
Dublin, CA
Team SETI.USA

I wonder if we've demonstrated another bug in BOINC?
____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Go ahead and abort them.

There was not work for Mac in this round, though some machines got told otherwise. The older app version is in the database, but the executable was not in the download area. If you had it already, fine, but if not, it would fail to download.

They had definitely run, I guess from an app I’d previously looted. 'n a few tasks were uploaded (& reported) earlier in th’ run.

I wonder if we've demonstrated another bug in BOINC?

I’ve aborted th’ tasks, but I still can nah seem t’ get them reported:

But accordin’ t’ th’ status page, th’ servers are up. Be thar no way t’ get BOINC t’ use a new IP without rebootin’ th’ system?

Once I realized the IP address had changed I edited DNS to propoagate the change. It can take up to an hour for those changes to propagate. But then it is available to your computer. Is it not connecting to the project?

If your client won't connect to the project, you could try stopping it (the client core, not just the manager) and restarting, to see if that clears it, instead of having to reboot the machine (which seems extereme).

So I think this indicates a bug in BOINC. At the time of the upload, it should look up the IP address in DNS and use that for the connection, instead of using some previous, possibly stale value.
____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

BOINC 6.x may handle thin’s differently. I’ll get around t’ updatin’ eventually …

It might be a waste o’ time t’ call up th’ DNS on every connection, but ’twould seem only prudent when retryin’ after failin’ t’ connect. (I had no problem reachin’ th’ website wit’ me browser th’ day after th’ upload first stalled.)

____________

Was that a Siren I heard?

This bug has been around for a LONG time. Every so often a project will start up using a dynamic DNS, and this forces them to change to a static address. It was supposed to have been fixed a while back. A library changed for something. But it didn't solve the problem.
____________
Dublin, CA
Team SETI.USA

This bug has been around for a LONG time. Every so often a project will start up using a dynamic DNS, and this forces them to change to a static address. It was supposed to have been fixed a while back. A library changed for something. But it didn't solve the problem.

That sounds familiar. Probably the thing.
____________
Dublin, CA
Team SETI.USA