Failed to access core package.

[Turbo_T]

I am trying to figure out why my SMP will not start work and seems to be stuck calling the server for a Core update. See message below:

18:01:46:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
18:01:46:WU00:FS00:Connecting to web.stanford.edu:80
18:01:46:ERROR:WU00:FS00:Exception: Failed to access core package.
18:03:23:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
18:03:23:WU00:FS00:Connecting to web.stanford.edu:80
18:03:23:ERROR:WU00:FS00:Exception: Failed to access core package.
18:06:00:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
18:06:00:WU00:FS00:Connecting to web.stanford.edu:80
18:06:00:ERROR:WU00:FS00:Exception: Failed to access core package.
18:10:14:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
18:10:14:WU00:FS00:Connecting to web.stanford.edu:80
18:10:15:ERROR:WU00:FS00:Exception: Failed to access core package.

Any help is much appreciated, I just got my system rebuilt and I am looking forward to churning out some WU's

Don

[bollix47]

@Turbo_T
Unfortunately there have been some recent assignment errors and you've received work that is inappropriate for your system. This thread that I've moved your post to does have one solution for fixing your problem but if you need additional help just post back here and let us know.

Basically you want to delete work/?? but how you go about that depends on your setup. Some have had success using Advanced Control (aka FAHControl) to delete and re-add the slot (this is the preferred method as it informs the WS which then reissues the work immediately instead of waiting for the timeout). Others have found that pausing the slot, quitting the client, deleting the appropriate work folder (work/00 in your case) and restarting the client works for them (the work server is not informed and the work will have to timeout before being reissued).

NB: there appears to be some confusion as to whether the WS is informed when deleting the appropriate work folder ... removing the slot and re-adding it definitely informs the WS so that is the preferred method at this time.

[BlackSun59]

Deleting the slot and re-adding it worked. Now folding a 7520. Thanks again, all.

[billford]

Basically you want to delete work/00 but how you go about that depends on your setup. Some have had success using Advanced Control (aka FAHControl) to delete and re-add the slot. Others have found that pausing the slot, quitting the client, deleting the appropriate work folder (work/00 in your case) and restarting the client works for them.

I've had both those methods work for me, but if I've interpreted the logs correctly it's better to delete and recreate the slot as then the WS is informed of the dump.

Seems reasonable to me- if you delete the work folder the client finds an in-use slot with nothing to identify what it was doing, deleting the slot leaves an identifiable WU with nowhere to put it!

So it can put it in the bit bucket and report back to the WS that that WU is available for re-issue.

It would be handy if someone (from PG?) could confirm (or refute) that- I don't dump WUs without good reason, but when I do I'd prefer to know that the WS knew about it asap rather than waiting for it to time out.

[Turbo_T]

Deleting the work unit folder worked for me, Thanks!!

Having a handy WU delete button on the console might be a good upgrade to the client GUI.

Don

[bruce]

So it can put it in the bit bucket and report back to the WS that that WU is available for re-issue.

It would be handy if someone (from PG?) could confirm (or refute) that- I don't dump WUs without good reason, but when I do I'd prefer to know that the WS knew about it asap rather than waiting for it to time out.

Confirmed.

There's one more option that we rarely recommend: There is a command-line parameter string that allows you to you delete WUs and inform the server the WU can be reassigned. (Nobody uses it because restarting with a command-line string is cumbersome.)

[billford]

Confirmed.

Thanks.

Didn't know about the command line method but I agree- CLI's are usually cumbersome to use. Not to mention dangerous in some cases if you make the wrong typo!

[hairyman]

Deleting the slot and re-adding it worked. Now folding a 7520. Thanks again, all.

Working now also for me, doing a 6370 WU

[apeman556]

Hello all
I had exactly the same problem with my CPU slot, I took bollix47's advice and just deleted the appropriate slot and then added it again and now all is well and my pc is happily folding again. No reboot required and I didn't have to stop the GPU slots folding either.

Hope this helps and thanks for the fix. Cheers
Ian

[awsum140]

I had the same problem with my laptop. The first thing I did was delete and re-add the slot. That didn't work. Then I deleted the work unit directory. That didn't work either. The next time I re-booted everything went back to normal. The setup is an i5 running Win7/Pro64 and I am guessing something gets cached somewhere. Unfortunately, I can't say which deletion actually did the trick, but doing both and a reboot might work for most.

[Veritas360]

Hello,

New to the forum so if theres any help or anyone experienced the same issues; Please let me know.

I've installed the 7.4.4 F@H client a while ago with the default options and the client has always had issues getting the next work assignment.
It seemed to have passed and was stable for the past few weeks.

At present, the client is stuck at :

ID - 00
Status - Update_Core
Work Server - 143.89.28.86

Please can anyone advise as it is a chore to keep un-installing and re-installing the client.
It is getting to the point where this can be maintained for much longer.

Any help will be greatly appreciated.

Cheers...

[bruce]

Welcome to foldingforum.org, Veritas360.

We're happy to help, but you need to provide more information. See the documentation suggestions in the signature section of my post (below).

[There was a recent upgrade to the server's code that has been causing unusual problems so it's likely not your fault, but we do need to understand the problem. When you reinstalled the client, did you choose to remove all data or retain it?]

[Veritas360]

Hi Bruce,

Thanks for the prompt reply and the warm welcome!

I've looked at your post and copied the log as requested.

A bit of insight may prove helpful, so the hardware is a new i7 processor with 8GB RAM so this is a machine that I am keen to have running all day, every day as this racks up lots of work units.
Any help would be greatly received and Thanks for the opportunity to help out with a project I (among many) really believe in.

Cheers Bruce!

Code: Select all

*********************** Log Started 2014-09-30T08:34:10Z ***********************
08:34:10:************************* Folding@home Client *************************
08:34:10:      Website: http://folding.stanford.edu/
08:34:10:    Copyright: (c) 2009-2014 Stanford University
08:34:10:       Author: Joseph Coffland <[email protected]>
08:34:10:         Args: --open-web-control
08:34:10:       Config: C:/Users/Admin/AppData/Roaming/FAHClient/config.xml
08:34:10:******************************** Build ********************************
08:34:10:      Version: 7.4.4
08:34:10:         Date: Mar 4 2014
08:34:10:         Time: 20:26:54
08:34:10:      SVN Rev: 4130
08:34:10:       Branch: fah/trunk/client
08:34:10:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
08:34:10:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
08:34:10:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
08:34:10:     Platform: win32 XP
08:34:10:         Bits: 32
08:34:10:         Mode: Release
08:34:10:******************************* System ********************************
08:34:10:          CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
08:34:10:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
08:34:10:         CPUs: 8
08:34:10:       Memory: 7.80GiB
08:34:10:  Free Memory: 5.21GiB
08:34:10:      Threads: WINDOWS_THREADS
08:34:10:   OS Version: 6.1
08:34:10:  Has Battery: false
08:34:10:   On Battery: false
08:34:10:   UTC Offset: 1
08:34:10:          PID: 4176
08:34:10:          CWD: C:/Users/Admin/AppData/Roaming/FAHClient
08:34:10:           OS: Windows 7 Enterprise
08:34:10:      OS Arch: AMD64
08:34:10:         GPUs: 0
08:34:10:         CUDA: Not detected
08:34:10:Win32 Service: false
08:34:10:***********************************************************************
08:34:10:<config>
08:34:10:  <!-- Folding Core -->
08:34:10:  <core-priority v='low'/>
08:34:10:
08:34:10:  <!-- Network -->
08:34:10:  <proxy v='lbsproxy:8080'/>
08:34:10:  <proxy-enable v='true'/>
08:34:10:
08:34:10:  <!-- Remote Command Server -->
08:34:10:  <password v='****'/>
08:34:10:
08:34:10:  <!-- Slot Control -->
08:34:10:  <power v='full'/>
08:34:10:
08:34:10:  <!-- User Information -->
08:34:10:  <passkey v='********************************'/>
08:34:10:  <team v='222711'/>
08:34:10:  <user v='Veritas360'/>
08:34:10:
08:34:10:  <!-- Folding Slots -->
08:34:10:  <slot id='1' type='CPU'/>
08:34:10:</config>
08:34:10:Trying to access database...
08:34:10:Successfully acquired database lock
08:34:10:Enabled folding slot 01: READY cpu:8
08:34:10:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:34:10:WU00:FS01:Connecting to lbsproxy:8080
08:34:11:ERROR:WU00:FS01:Exception: Failed to access core package.
08:35:10:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:35:10:WU00:FS01:Connecting to lbsproxy:8080
08:35:11:ERROR:WU00:FS01:Exception: Failed to access core package.
08:36:47:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:36:47:WU00:FS01:Connecting to lbsproxy:8080
08:36:48:ERROR:WU00:FS01:Exception: Failed to access core package.
08:39:25:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:39:25:WU00:FS01:Connecting to lbsproxy:8080
08:39:25:ERROR:WU00:FS01:Exception: Failed to access core package.
08:43:39:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:43:39:WU00:FS01:Connecting to lbsproxy:8080
08:43:39:ERROR:WU00:FS01:Exception: Failed to access core package.
08:50:30:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
08:50:30:WU00:FS01:Connecting to lbsproxy:8080
08:50:31:ERROR:WU00:FS01:Exception: Failed to access core package.
09:01:36:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
09:01:36:WU00:FS01:Connecting to lbsproxy:8080
09:01:36:ERROR:WU00:FS01:Exception: Failed to access core package.
09:06:42:Removing old file 'configs/config-20140923-100247.xml'
09:06:42:Saving configuration to config.xml
09:06:42:<config>
09:06:42:  <!-- Folding Core -->
09:06:42:  <core-priority v='low'/>
09:06:42:
09:06:42:  <!-- Network -->
09:06:42:  <proxy v='lbsproxy:8080'/>
09:06:42:  <proxy-enable v='true'/>
09:06:42:
09:06:42:  <!-- Remote Command Server -->
09:06:42:  <password v='****'/>
09:06:42:
09:06:42:  <!-- Slot Control -->
09:06:42:  <power v='light'/>
09:06:42:
09:06:42:  <!-- User Information -->
09:06:42:  <passkey v='********************************'/>
09:06:42:  <team v='222711'/>
09:06:42:  <user v='Veritas360'/>
09:06:42:
09:06:42:  <!-- Folding Slots -->
09:06:42:  <slot id='1' type='CPU'/>
09:06:42:</config>
09:12:48:Removing old file 'configs/config-20140924-111054.xml'
09:12:48:Saving configuration to config.xml
09:12:48:<config>
09:12:48:  <!-- Folding Core -->
09:12:48:  <core-priority v='low'/>
09:12:48:
09:12:48:  <!-- Network -->
09:12:48:  <proxy v='lbsproxy:8080'/>
09:12:48:  <proxy-enable v='true'/>
09:12:48:
09:12:48:  <!-- Remote Command Server -->
09:12:48:  <password v='****'/>
09:12:48:
09:12:48:  <!-- User Information -->
09:12:48:  <passkey v='********************************'/>
09:12:48:  <team v='222711'/>
09:12:48:  <user v='Veritas360'/>
09:12:48:
09:12:48:  <!-- Folding Slots -->
09:12:48:  <slot id='1' type='CPU'/>
09:12:48:</config>
09:19:33:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
09:19:33:WU00:FS01:Connecting to lbsproxy:8080
09:19:33:ERROR:WU00:FS01:Exception: Failed to access core package.
09:48:35:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
09:48:35:WU00:FS01:Connecting to lbsproxy:8080
09:48:35:ERROR:WU00:FS01:Exception: Failed to access core package.
10:35:34:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
10:35:34:WU00:FS01:Connecting to lbsproxy:8080
10:35:35:ERROR:WU00:FS01:Exception: Failed to access core package.
10:54:28:Removing old file 'configs/config-20140924-111155.xml'
10:54:28:Saving configuration to config.xml
10:54:28:<config>
10:54:28:  <!-- Folding Core -->
10:54:28:  <core-priority v='low'/>
10:54:28:
10:54:28:  <!-- Network -->
10:54:28:  <proxy v='lbsproxy:8080'/>
10:54:28:  <proxy-enable v='true'/>
10:54:28:
10:54:28:  <!-- Remote Command Server -->
10:54:28:  <password v='****'/>
10:54:28:
10:54:28:  <!-- Slot Control -->
10:54:28:  <power v='full'/>
10:54:28:
10:54:28:  <!-- User Information -->
10:54:28:  <passkey v='********************************'/>
10:54:28:  <team v='222711'/>
10:54:28:  <user v='Veritas360'/>
10:54:28:
10:54:28:  <!-- Folding Slots -->
10:54:28:  <slot id='1' type='CPU'/>
10:54:28:</config>
11:51:35:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
11:51:35:WU00:FS01:Connecting to lbsproxy:8080
11:51:36:ERROR:WU00:FS01:Exception: Failed to access core package.
13:54:34:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
13:54:34:WU00:FS01:Connecting to lbsproxy:8080
13:54:35:ERROR:WU00:FS01:Exception: Failed to access core package.
******************************* Date: 2014-09-30 *******************************
17:13:35:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
17:13:35:WU00:FS01:Connecting to lbsproxy:8080
17:13:35:ERROR:WU00:FS01:Exception: Failed to access core package.
22:35:35:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
22:35:35:WU00:FS01:Connecting to lbsproxy:8080
22:35:35:ERROR:WU00:FS01:Exception: Failed to access core package.
******************************* Date: 2014-10-01 *******************************
04:35:35:WU00:FS01:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_b0.fah
04:35:35:WU00:FS01:Connecting to lbsproxy:8080
04:35:36:ERROR:WU00:FS01:Exception: Failed to access core package.

[davidcoton]

Hi Veritas360

First off, this is not a Core17 issue, so the mods may well move this thread to a more appropriate place...
(Core17 is a GPU core, you are folding CPU only).

The AS (Assignment Server) has wrongly assigned you a CoreB0 WU (Work Unit), so your client requests CoreB0, and not surprisingly can't get it. So you need to remove the Work Unit, and hope the AS gives you a more appropriate WU next time. Probably the best way to do that is to delete and re-create the CPU folding slot using Advanced Control (FAHControl). Shout if you need help with that.

[Veritas360]

Hi David,

Thanks for the reply; That fix seemed to pick up a new work unit! Cheers.

Will this resolve the ongoing issues with the client continually not picking up work units and sat idle for lengths of time or is this something that will be resolved in a future release of the client ?