LHC@home

The current sixtracktests: have all the same Result:

Maximum elapsed time exceeded

after 11 000 - 15000 sec.

Regardes

wsuper_nuebb7__1__s__64.31_59.32__6.5_7__e4__64.5_boinc102_2



Arbeitspaket

11641148



Erstellt

17 Jan 2014, 3:41:24 UTC



Gesendet

17 Jan 2014, 3:41:35 UTC



Empfangen

17 Jan 2014, 14:36:32 UTC



Serverstatus

Abgeschlossen



Resultat

Berechnungsfehler



Clientstatus

Berechnungsfehler



Endstatus

197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED



Computer ID

10310510



Ablaufdatum

24 Jan 2014, 19:13:49 UTC



Laufzeit

7,068.76



CPU Zeit

6,550.36



Prüfungsstatus

Ungültig



Punkte

0.00



Anwendungsversion

sixtracktest v450.03 (pni)


Stderr Ausgabe
<core_client_version>7.0.42</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x753D491E

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 7.1.0


Dump Timestamp : 01/17/14 15:31:05
Install Directory : C:\Program Files\BOINC\
Data Directory : C:\ProgramData\BOINC
Project Symstore :
Loaded Library : C:\Program Files\BOINC\\dbghelp.dll
Loaded Library : C:\Program Files\BOINC\\symsrv.dll
Loaded Library : C:\Program Files\BOINC\\srcsrv.dll
LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\ProgramData\BOINC\slots\0;C:\ProgramData\BOINC\projects\lhcathomeclassic.cern.ch_sixtrack


ModLoad: 0000000001320000 0000000004df4000 C:\ProgramData\BOINC\projects\lhcathomeclassic.cern.ch_sixtrack\sixtracktest_win32_4503_pni.exe (-nosymbols- Symbols Loaded)
Linked PDB Filename :

ModLoad: 0000000077190000 000000000013c000 C:\Windows\SYSTEM32\ntdll.dll (6.1.7601.18205) (-exported- Symbols Loaded)
Linked PDB Filename : ntdll.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7600.16385

ModLoad: 0000000076960000 00000000000d4000 C:\Windows\system32\kernel32.dll (6.1.7601.18229) (-exported- Symbols Loaded)
Linked PDB Filename : kernel32.pdb
File Version : 6.1.7601.17965 (win7sp1_gdr.121004-0333)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7601.17965

ModLoad: 00000000753a0000 000000000004b000 C:\Windows\system32\KERNELBASE.dll (6.1.7601.18229) (-exported- Symbols Loaded)
Linked PDB Filename : kernelbase.pdb
File Version : 6.1.7601.17965 (win7sp1_gdr.121004-0333)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7601.17965

ModLoad: 0000000075900000 00000000000c9000 C:\Windows\system32\USER32.dll (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : user32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7601.17514

ModLoad: 0000000077370000 000000000004e000 C:\Windows\system32\GDI32.dll (6.1.7601.18275) (-exported- Symbols Loaded)
Linked PDB Filename : gdi32.pdb
File Version : 6.1.7601.18275 (win7sp1_gdr.131002-1533)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7601.18275

ModLoad: 0000000077340000 000000000000a000 C:\Windows\system32\LPK.dll (6.1.7601.18177) (-exported- Symbols Loaded)
Linked PDB Filename : lpk.pdb
File Version : 6.1.7601.18177 (win7sp1_gdr.130605-1534)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7601.18177

ModLoad: 00000000759d0000 000000000009d000 C:\Windows\system32\USP10.dll (1.626.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : usp10.pdb
File Version : 1.0626.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft(R) Uniscribe Unicode script processor
Product Version : 1.0626.7601.17514

ModLoad: 0000000075c30000 00000000000ac000 C:\Windows\system32\msvcrt.dll (7.0.7601.17744) (-exported- Symbols Loaded)
Linked PDB Filename : msvcrt.pdb
File Version : 7.0.7601.17744 (win7sp1_gdr.111215-1535)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 7.0.7601.17744

ModLoad: 0000000076d20000 00000000000a0000 C:\Windows\system32\ADVAPI32.dll (6.1.7601.22137) (-exported- Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7600.16385

ModLoad: 00000000772d0000 0000000000019000 C:\Windows\SYSTEM32\sechost.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : sechost.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075620000 00000000000a2000 C:\Windows\system32\RPCRT4.dll (6.1.7601.18205) (-exported- Symbols Loaded)
Linked PDB Filename : rpcrt4.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7600.16385

ModLoad: 0000000075ce0000 000000000002b000 C:\Windows\system32\imagehlp.dll (6.1.7601.18288) (-exported- Symbols Loaded)
Linked PDB Filename : imagehlp.pdb
File Version : 6.1.7601.18288 (win7sp1_gdr.131018-1533)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7601.18288

ModLoad: 0000000077350000 0000000000005000 C:\Windows\system32\PSAPI.DLL (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : psapi.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000076a40000 000000000001f000 C:\Windows\system32\IMM32.DLL (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : imm32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7601.17514

ModLoad: 0000000076bc0000 00000000000cc000 C:\Windows\system32\MSCTF.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : msctf.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft&#174; Windows&#174;
Product Version : 6.1.7600.16385

ModLoad: 000000005fad0000 0000000000115000 C:\Program Files\BOINC\dbghelp.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : dbghelp.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 000000006c440000 0000000000048000 C:\Program Files\BOINC\symsrv.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : symsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 000000006ba40000 000000000003b000 C:\Program Files\BOINC\srcsrv.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : srcsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 0000000075050000 0000000000009000 C:\Windows\system32\version.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : version.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft&#174; Windows&#174; Operating System
Product Version : 6.1.7600.16385



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 0, Write: 0, Other 0

- I/O Transfers Counters -
Read: 0, Write: 0, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 0, QuotaPeakPagedPoolUsage: 0
QuotaNonPagedPoolUsage: 0, QuotaPeakNonPagedPoolUsage: 0

- Virtual Memory Usage -
VirtualSize: 0, PeakVirtualSize: 0

- Pagefile Usage -
PagefileUsage: 0, PeakPagefileUsage: 0

- Working Set Size -
WorkingSetSize: 0, PeakWorkingSetSize: 0, PageFaultCount: 0

*** Dump of thread ID 11480 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x753D491E

- Registers -
eax=00000000 ebx=0000000a ecx=0164340c edx=0624f850 esi=769ac266 edi=769ad790
eip=753d491e esp=0624f844 ebp=0624fc4c
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
0624fc4c 015ea210 00000000 00000000 00000000 70c05c7c KERNELBASE!DebugBreak+0x0
0624fe6c 769aed5c 00000000 0624feb8 771f37eb 00000000 sixtracktest_win32_4503_pni!+0x0
0624fe78 771f37eb 00000000 7703f2a4 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
0624feb8 771f37be 015ea190 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
0624fed0 00000000 015ea190 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0

*** Dump of thread ID 10428 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000

- Registers -
eax=02378c78 ebx=02378c78 ecx=02379478 edx=02378a78 esi=02378a78 edi=02379478
eip=0145d80f esp=00179fc8 ebp=0017a018
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000203

- Callstack -
ChildEBP RetAddr Args to Child
0017a018 014cd6fe 02378c78 02378a78 02379478 02379278 sixtracktest_win32_4503_pni!+0x0
0017c088 01498be7 771d6a64 753a179c 00000088 00000000 sixtracktest_win32_4503_pni!+0x0
0017c374 01382c3d 0017cba4 02ab3fe0 00000000 00000000 sixtracktest_win32_4503_pni!+0x0
0017fd78 015f21a2 0017fe7c 00000000 00000000 00000000 sixtracktest_win32_4503_pni!+0x0
0017fdf8 015c7782 00000004 00000000 015fe2f4 00000000 sixtracktest_win32_4503_pni!+0x0
0017fec4 769aed5c 7ffd3000 0017ff10 771f37eb 7ffd3000 sixtracktest_win32_4503_pni!+0x0
0017fed0 771f37eb 7ffd3000 7130f30c 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
0017ff10 771f37be 015c77ff 7ffd3000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
0017ff28 00000000 015c77ff 7ffd3000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0

Exiting...

</stderr_txt>
]]>

Batch of 7 last night all had the same time-limit error with all wingmen having the same problem (random example) all with longer run times than normal for test WUs.

New batch just in (and out). Couple of minutes run time and all completed OK. Whatever today's tweak was seems to have fixed the problem.

Thanks for the feedback. I messed up (as usual).
Fixed and running more tests. Eric.

---

Hi,

I just errored out on a task: http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=11658885

From the specs of others users, I was wondering: Windows 7 only task?

Hi,

I just errored out on a task: http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=11658885

From the specs of others users, I was wondering: Windows 7 only task?

ERIC!! Maybe this is a hint:

Windows-XP and Windos 2003 Server leads to 100% loss
Error:

Stderr Ausgabe
<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
couldn't start CreateProcess() failed - : -148
</message>
]]>

Win7 and Microsoft Windows Server 2008 "R2" are 100% successful

Look a my Machines:

http://lhcathomeclassic.cern.ch/sixtrack/hosts_user.php?userid=241360


regardes

Franz

OT to the thread title but relevant to testing of the same version v450.03.

Not sure exactly what these latest batch of 450.03 are testing but I did spot a couple with 9e5 in the wu name where all the others were just e5. Those with the e5 start at 0% and finish at 1%. Those with the 9e5 start at 8% and finish at 9%. And, just in, others with 3e5 and 8e5, starting at 2% and 7% running to 3% and 8% respectively. Is this perhaps preparation for future mega WUs were we get the follow on of a WU from a previous contributor? Personally, I have no objection to running longer WUs than are normal here, having done CPDN WUs that can run for a couple of weeks to a couple of months depending on the flavour. If such WUs were to be run by a single user, they could, perhaps, be called a separate application, user selectable, so one could choose to run only the short ones or only the long ones, or a mixture.

All those with the extra digit have been finishing successfully but in the stderr there is the line:

<stderr_txt>
error: cannot delete old stderr.txt eg. this one.
so perhaps some more tweaking reqd.

All those with the extra digit have been finishing successfully but in the stderr there is the line:

<stderr_txt>
error: cannot delete old stderr.txt eg. this one.
so perhaps some more tweaking reqd.

That's a odd one. In general, BOINC will start each new task in a pristine (clean) slot directory - there will be no files at all (except the files needed to start the new task). stderr.txt will be created (from scratch) by the application running the new task: that application is not expected to delete any previous file, and any attempt to delete a file will fail because the file isn't there after BOINC has performed housekeeping.

It does sound like an artefact of the attempt to create a chain of tasks, each picking up where the previous one finished. Maybe the file deletion is needed for stand-alone tests without a BOINC housekeeper? In which case, the 'delete stray files' action may be useful, but the failure under BOINC isn't an error. Maybe change the message class to [info]?

96 marked as validation inconclusive
for both

SixTrack v446.03 (pni)
sixtracktest v450.03 (pni)

like
http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=25202863
(SixTrack v446.03 (pni))
and
http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=25295372 (sixtracktest v450.03 (pni))


15 marked as invalid
sixtracktest v450.03 (pni)

like this http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=25257359

170 marked as error while computing
sixtracktest v450.03

like this http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=25265447

Outcome Computation error
Client state Compute error
Exit status -185 (0xffffffffffffff47) ERR_RESULT_START

<core_client_version>7.2.28</core_client_version>
<![CDATA[
<message>
couldn't start app: CreateProcess() failed - (unknown error)
</message>
]]>

Hi,

Windows-XP and Windos 2003 Server leads to 100% loss
Error:

[quote]Stderr Ausgabe
<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
couldn't start CreateProcess() failed - : -148
</message>
]]>

Win7 and Microsoft Windows Server 2008 "R2" are 100% successful

mine the only Win7 have other error meanwhile are also failing

Is this perhaps preparation for future mega WUs were we get the follow on of a WU from a previous contributor?

Yep, the madness has begun. Why does this project attract the nuttiest of the nutbar admins. Pathetic. A one idea man with a one track mind on a mission to solve problems that are already solved. Hopefully somebody at CERN gets wind of this and tells him he isn't allowed to waste their bandwidth that way let alone the bandwidth of their volunteers.

---

6 bangers are for wussies.