Tasks not crunching

Message boards : Number crunching : Tasks not crunching
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904587 - Posted: 3 Dec 2017, 9:25:35 UTC
Last modified: 3 Dec 2017, 9:26:07 UTC

There are 47 tasks sitting in my computer, have been there for several days they have not done a stitch of work. Some are due for submittal in a week. Two have already timed out.

How can I make them get off their butts and go to work?

Steve Gaber
Oldsmar, FL USA
ID: 1904587 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 9618
Credit: 123,866,376
RAC: 82,607
Australia
Message 1904590 - Posted: 3 Dec 2017, 9:39:40 UTC - in response to Message 1904587.  
Last modified: 3 Dec 2017, 9:43:25 UTC

There are 47 tasks sitting in my computer, have been there for several days they have not done a stitch of work. Some are due for submittal in a week. Two have already timed out.

?
Looking at your details, there are presently 20 Seti tasks in progress and the earliest they are due is the 3rd of January. None have errored out.
The Skynet POGS shows 6 in progress, none due until the 9th of this month. None have errored out.
Asteroids at home shoew 6 in progress, none due until the 13th of this month. 5 have errored out. 2 were cancelled by the server on the day they were sent, 3 others had an error while computing, but you have returned valid work after the dates those errored out (3 WUs reported today).

So if nothing is being processed at the moment, I suggest you check your settings to see if you have suspended any of the projects, paused processing, or due to your settings for when work is processed, processing has stopped due to other programmes running on your system.
Easiest method would probably be to exit BOINC, then restart it. If still no WUs are being processed then check the Manager Event log for messages about suspended or disabled processing.
Grant
Darwin NT
ID: 1904590 · Report as offensive
bluestar

Send message
Joined: 5 Sep 12
Posts: 2622
Credit: 1,939,672
RAC: 35
Message 1904609 - Posted: 3 Dec 2017, 14:19:22 UTC

ID: 1904609 · Report as offensive
Bill Greene
Volunteer tester

Send message
Joined: 3 Jul 99
Posts: 80
Credit: 89,902,532
RAC: 32,161
United States
Message 1904623 - Posted: 3 Dec 2017, 15:57:56 UTC - in response to Message 1904590.  

Inserting into this thread to avoid having to open another. Recent W10 update occurred about the same time SETI server went down. Now my GPU's are idle while the CPU's are at 100% (as set). I am getting computational errors on GPU tasks on both SETI and Einstein. Drivers are up to date. Before I begin backing out and reloading everything, anyone else experiencing this problem?
ID: 1904623 · Report as offensive
rob smith Special Project $250 donor
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 15879
Credit: 296,162,734
RAC: 327,905
United Kingdom
Message 1904639 - Posted: 3 Dec 2017, 17:41:26 UTC

Oh no - not another "victim" of MS's sadly deficient nVida drivers.
Two things to do:
First ensure that Windows is barred from updating drivers;
Second visit the nVidia website and get the full driver for your GPU from there, then do a "clean" installation of the drivers, and when the installation is over reboot the machine (even if it isn't required).
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1904639 · Report as offensive
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904641 - Posted: 3 Dec 2017, 18:15:56 UTC - in response to Message 1904590.  

There are 20 tasks marked "Ready to start" shown in my BOINC Manager, but not moving. There are 47 tasks in progress shown in my S@H account. Two so far have timed out. There are others for which the deadline is 9 December and will probably time out if I don't get them running again. POGS and Asteroids are running apace.
ID: 1904641 · Report as offensive
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904642 - Posted: 3 Dec 2017, 18:30:13 UTC - in response to Message 1904641.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.
ID: 1904642 · Report as offensive
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 729
Credit: 122,925,093
RAC: 103,946
United States
Message 1904649 - Posted: 3 Dec 2017, 19:08:10 UTC - in response to Message 1904642.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.

Default Windows drivers may not be the ticket. You need to do a clean install of the driver from the website.

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1904649 · Report as offensive
rob smith Special Project $250 donor
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 15879
Credit: 296,162,734
RAC: 327,905
United Kingdom
Message 1904656 - Posted: 3 Dec 2017, 19:54:07 UTC

Uninstalling the updated driver will probably (almost certainly) NOT work as the first thing Windows will do is install its own deficient driver again and you will be no further forward.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1904656 · Report as offensive
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 729
Credit: 122,925,093
RAC: 103,946
United States
Message 1904657 - Posted: 3 Dec 2017, 20:07:30 UTC - in response to Message 1904656.  

Just a thought, but I have not heard of problems with AMD drivers, only NVidia, and that is what we are dealing with here.

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1904657 · Report as offensive
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904663 - Posted: 3 Dec 2017, 21:10:43 UTC - in response to Message 1904649.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.

Default Windows drivers may not be the ticket. You need to do a clean install of the driver from the website.


OK. After uninstalling Driver Support -- a third party utility??-- and restarting the S@H project, it's working again. One task is already complete and two are running.

Thanks, guys.

Steve Gaber
Oldsmar, FL USA
ID: 1904663 · Report as offensive
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904664 - Posted: 3 Dec 2017, 21:13:54 UTC - in response to Message 1904663.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.

Default Windows drivers may not be the ticket. You need to do a clean install of the driver from the website.


OK. After uninstalling Driver Support -- a third party utility??-- and restarting the S@H project, it's working again. One task is already complete and two are running.

Thanks, guys.

Steve Gaber
Oldsmar, FL USA


I just suspended POGS and Asteroids so maybe SETI can catch up.
Steve Gaber
Oldsmar, FL USA
ID: 1904664 · Report as offensive
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 729
Credit: 122,925,093
RAC: 103,946
United States
Message 1904681 - Posted: 3 Dec 2017, 22:53:10 UTC - in response to Message 1904663.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.

Default Windows drivers may not be the ticket. You need to do a clean install of the driver from the website.


OK. After uninstalling Driver Support -- a third party utility??-- and restarting the S@H project, it's working again. One task is already complete and two are running.

Thanks, guys.

Steve Gaber
Oldsmar, FL USA

Yes, that is a third party utility. Not needed at all.

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1904681 · Report as offensive
Steven Gaber

Send message
Joined: 19 Jan 13
Posts: 75
Credit: 1,731,190
RAC: 1,015
United States
Message 1904718 - Posted: 4 Dec 2017, 2:55:40 UTC - in response to Message 1904681.  

Yes, this seems to have started when Driver Update was installed. So I uninstalled it and will see if that does the trick. Thanks.

Default Windows drivers may not be the ticket. You need to do a clean install of the driver from the website.


OK. After uninstalling Driver Support -- a third party utility??-- and restarting the S@H project, it's working again. One task is already complete and two are running.

Thanks, guys.

Steve Gaber
Oldsmar, FL USA

Yes, that is a third party utility. Not needed at all.


Driver Support is one of those sneaky buggers that look like they're official, but are really not. They say they're free, but really not. I hate that deceptive crap and don't know why the big guys like Microsoft or the Federal Trade Commission allow it.
ID: 1904718 · Report as offensive
Bill Greene
Volunteer tester

Send message
Joined: 3 Jul 99
Posts: 80
Credit: 89,902,532
RAC: 32,161
United States
Message 1904767 - Posted: 4 Dec 2017, 14:05:10 UTC - in response to Message 1904639.  

Thanks, Bob. Did some of those but will do clean updates from nVidia. Every time MS updates, things go astray.
ID: 1904767 · Report as offensive
Bill Greene
Volunteer tester

Send message
Joined: 3 Jul 99
Posts: 80
Credit: 89,902,532
RAC: 32,161
United States
Message 1904855 - Posted: 4 Dec 2017, 21:13:55 UTC - in response to Message 1904767.  

Well, completely removed and reinstalled BOINC along with SETI. Haven't applied lunatics yet since but I did roll back to nVidia driver 378.49 restarting after each change. I'm about to roll back on the Windows update but thought I would first see if anyone has suggestions on what may be causing this problem. It seems to have started with the last Windows update but is only affecting use of the GPU's for both SETI and Einstein. Following are the errors with SETI ...

12/4/2017 4:08:10 PM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit
12/4/2017 4:08:48 PM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit
12/4/2017 4:09:24 PM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit
12/4/2017 4:10:01 PM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit
12/4/2017 4:10:38 PM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit

And then they subsequently fail entirely. Help appreciated.
ID: 1904855 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 9618
Credit: 123,866,376
RAC: 82,607
Australia
Message 1904926 - Posted: 5 Dec 2017, 6:38:22 UTC - in response to Message 1904855.  

Well, completely removed and reinstalled BOINC along with SETI. Haven't applied lunatics yet since but I did roll back to nVidia driver 378.49 restarting after each change. I'm about to roll back on the Windows update

For things like this, rolling back isn't the way to go. Make sure the OS is current with all it's updates, then re-install the driver freshly downloaded from Nvidia.
Grant
Darwin NT
ID: 1904926 · Report as offensive
Bill Greene
Volunteer tester

Send message
Joined: 3 Jul 99
Posts: 80
Credit: 89,902,532
RAC: 32,161
United States
Message 1904955 - Posted: 5 Dec 2017, 12:34:45 UTC - in response to Message 1904926.  

Well, completely removed and reinstalled BOINC along with SETI. Haven't applied lunatics yet since but I did roll back to nVidia driver 378.49 restarting after each change. I'm about to roll back on the Windows update

For things like this, rolling back isn't the way to go. Make sure the OS is current with all it's updates, then re-install the driver freshly downloaded from Nvidia.


Thanks for the advice. These GPU rejects have been ongoing for about a week starting with the Nov 27 Windows update. My first fix attempt was to make sure all drivers were up to date with downloads from nVidia. That didn't work so I rolled back on drivers to no avail. Attempted to roll back yesterday on Windows but that was unsuccessful.
I'm going to start fresh by making sure Windows 10 is up to date and that all drivers are again current. If that doesn't work, I will attempt another roll back on Windows. I continue to appreciate any help.
ID: 1904955 · Report as offensive
Scott Hinnrichs
Volunteer tester

Send message
Joined: 25 May 99
Posts: 3
Credit: 378,517
RAC: 0
United States
Message 1905432 - Posted: 7 Dec 2017, 23:28:18 UTC

My Windows Vista computer doing service on SETI@HOME received a warning:

SETI@home: Notice from server
NVIDIA GPU: Upgrade to the latest driver to process tasks using your computer's GPU
12/6/2017 4:39:02 PM

It is still running CPU + GPU jobs right now, but I don't know for how long given the GPU Driver version warning.

Vista Nvidia driver updates stopped with 342.01, which is what it is running.

Will there be an exception made to allow the older computers without ongoing Nvidia GPU updates to contribute moving forward?
ID: 1905432 · Report as offensive
rob smith Special Project $250 donor
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 15879
Credit: 296,162,734
RAC: 327,905
United Kingdom
Message 1905494 - Posted: 8 Dec 2017, 5:59:23 UTC

In your case it might indicate a broken driver or an incorrectly updated - I do wish someone would sort the driver messages, one message for three very different issues is a grade one PITA.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1905494 · Report as offensive
1 · 2 · Next

Message boards : Number crunching : Tasks not crunching


 
©2018 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.