All wu's recent failing quickly.
>>>
<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
error: No such file or directory
problem loading parameter file, stopping
13:27:20 (4804): called boinc_finish
</stderr_txt>
]]>
<<<
All wu's failing.
Moderator: moderators
Re: All wu's failing.
I'm seeing the same thing. Reseting the project doesn't help, nor does disconnecting and reconnecting.
Re: All wu's failing.
It was our fault. The client binary has been updated and should now work.
Re: All wu's failing.
Practically all Wu's fail on all my Box's:
Stderr output
<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified.
(0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
</stderr_txt>
]]>
Stderr output
<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified.
(0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
</stderr_txt>
]]>
Re: All wu's failing.
Steve,
>std::bad_alloc
Eon seems to have a huge memory inflation bug, making them eat all your ram and swap.
(I'm having a similar thing. See my thread).
>std::bad_alloc
Eon seems to have a huge memory inflation bug, making them eat all your ram and swap.
(I'm having a similar thing. See my thread).
-
- Posts: 20
- Joined: Wed Oct 27, 2010 2:07 pm
Re: All wu's failing.
Its happening again. I am getting 100% WU failures. Everything since 17:00UTC as far as I can tell. Maybe earlier.
Re: All wu's failing.
API-MS-WIN-CORE-COM-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
missing.
http://www.microsoft.com/en-us/download ... aspx?id=29
You need to install the correct MS redistributables when you deploy your application. This should fix some of the dependency errors.
http://qt-project.org/doc/qt-4.8/deploy ... l-installs
http://qt-project.org/doc/qt-4.8/deploy ... pendencies
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
DCOMP.DLL
missing.
http://www.microsoft.com/en-us/download ... aspx?id=29
You need to install the correct MS redistributables when you deploy your application. This should fix some of the dependency errors.
http://qt-project.org/doc/qt-4.8/deploy ... l-installs
http://qt-project.org/doc/qt-4.8/deploy ... pendencies
-
- Posts: 20
- Joined: Wed Oct 27, 2010 2:07 pm
Re: All wu's failing.
OK, looks like a fix came in about 22 Jun 2013 7:30:01 UTC. Normal running has resumed.
-
- Posts: 5
- Joined: Wed Oct 13, 2010 9:11 pm
Re: All wu's failing.
Looks like its back again, I got some of these WU with error more than 20 on that machine since 25 June
Stderr output
<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
Das System kann den angegebenen Pfad nicht finden. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
http://eon.ices.utexas.edu/eon2/result. ... =232510405
Name 871948887_0_4812
Edit: all WU with 871948887_0_* are crashing with the error above.
WU like 1768547535_38298 are running fine on the same machine.
Stderr output
<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
Das System kann den angegebenen Pfad nicht finden. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
http://eon.ices.utexas.edu/eon2/result. ... =232510405
Name 871948887_0_4812
Edit: all WU with 871948887_0_* are crashing with the error above.
WU like 1768547535_38298 are running fine on the same machine.