I'm having no issues currently. Mine are uploading and downloading like clock work so far.I'm guessing the inability to upload completed data or get new Amicable tasks is expected at this point?
It all worked on computer 1 on Saturday when I pulled down 20 jobs, set a host file entry for sech.me and processed them all. I have removed the host file entry, and I can traceroute to sec.me without an issue.I'm having no issues currently. Mine are uploading and downloading like clock work so far.
Have you checked your preferences settings?
This is the second time I had by oldest 3700X rig crash in the last 2 weeks.Non responsive to terminal, ssh and boinc remote. I suspect some hardware failure is in my future. It's my dual 1080Ti rig. I need it to last another week.
Once the host file is fixed if you go under 'transfers' in BOINC Manager and select one of the tasks and hit 'Retry now' it seems to get them transferring at least for me. I'm guessing it waits to retry after so many failures or something, but I'm not 100% sure. I don't know if that would affect your ability to get new tasks, but maybe depending on how many you have already pulled down?It all worked on computer 1 on Saturday when I pulled down 20 jobs, set a host file entry for sech.me and processed them all. I have removed the host file entry, and I can traceroute to sec.me without an issue.
On computer 2, I added the project... but now that I look at it, that boinc install isn't detecting my GPU. *sigh* may not fix that one tonight.
Boinc seems to have cashed something. I restarted the client and amicable immediately started working correctly. Gave up on getting boinc to see the 1080ti on the other pc for the night - GPU options don’t even show up in the GUI, so it may not be a quick fix. Worst case, i leave the 1080ti on F@H.Once the host file is fixed if you go under 'transfers' in BOINC Manager and select one of the tasks and hit 'Retry now' it seems to get them transferring at least for me. I'm guessing it waits to retry after so many failures or something, but I'm not 100% sure. I don't know if that would affect your ability to get new tasks, but maybe depending on how many you have already pulled down?
id boinc
shows boinc to be member of group "boinc" only, then try:sudo usermod -a -G video boinc
Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo
02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
Rosetta@home __ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 14 days Marathon
Universe@home _ __ __ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 5 days City Run
Amicable Numbers _ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 5 days Cross Country
t.b.a. 3 days Sprint
NumberFields@home __ __ __ ▄▄ 1 day Javelin Throw
__ __ __ ▄▄ 1 day
__ __ __ ▄▄ 1 day
__ __ __ ▄▄ 1 day
1 day
02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo
I’ve seen several of those, and for me they have been getting stuck. One has been processing for 1 Day, 22 hours.Keep an eye on your Rosetta rigs. I've got a new task that's taking 2.6 GB of RAM!
Keep an eye on your Rosetta rigs. I've got a new task that's taking 2.6 GB of RAM!
The decisions from which project to request how much new work, and which of the queued tasks then to start (or stop to start others instead) are happening locally in the boinc client, based on a variety of criteria. (Very long-term criteria, such as which projects hasn't been run much during the past few weeks or so, and shorter term criteria, e.g. which tasks might miss the reporting deadline if they are left at the bottom of the queue for much longer.) Just like you have observed, these client-side decisions are neither transparent nor intuitive.am annoyed WCG has ignored the rule of 7 tasks at a given time for this. Sometimes it seems to wanna work on those and other times its non stop Rosetta.
The decisions from which project to request how much new work, and which of the queued tasks then to start (or stop to start others instead) are happening locally in the boinc client, based on a variety of criteria. (Very long-term criteria, such as which projects hasn't been run much during the past few weeks or so, and shorter term criteria, e.g. which tasks might miss the reporting deadline if they are left at the bottom of the queue for much longer.) Just like you have observed, these client-side decisions are neither transparent nor intuitive.
The setting at the WCG website which you are referring to is acting on the WCG server side: The server will not let the client keep more than 7 tasks buffered.
Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo
02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
Rosetta@home __ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 14 days Marathon
Universe@home _ __ __ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 5 days City Run
Amicable Numbers _ __ __ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ 5 days Cross Country
t.b.a. .. .. .. ▄▄ ▄▄ ▄▄ 3 days Sprint
NumberFields@home __ __ __ ▄▄ 1 day Javelin Throw
__ __ __ ▄▄ 1 day
__ __ __ ▄▄ 1 day
__ __ __ ▄▄ 1 day
? ? ? 1 day
02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18
Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo
Tried it, but no luck. I had about 30 minutes to work on it including installing the ram. Ran out of time, but at least the ram is upgraded@Endgame124, a shot in the dark:
Ifid boinc
shows boinc to be member of group "boinc" only, then try:
sudo usermod -a -G video boinc
After that, restart the boinc service, or reboot.
I don't remember whether or not this is actually necessary, but give it a try.
This outage ended up lasting less than an hour as planned, and did not affect any of the full-hour stats updates as far as I have seen. I never even noticed the Pentathlon site to go offline.PSA from the organizers:
The hosting company of the Pentathlon website has scheduled a 1-hour downtime for later today. *If* the outage happens during the finish of City Run and start of Cross Country, SETI.Germany will acquire stats through a backup server and update the Pentathlon site afterwards.
Today's PSA from the organizers:Another outage is scheduled for Wednesday.