LHC@home

Work unit 18368005 has completed on my PC and BOINC Manager says "Uploading" but it does not appear on the Transfers tab and "Update" does not make it budge. It shows as "In progress" on the web site.

Other packets completed since that one are uploading OK.

Any suggestions?

---

As an addition to that no new statistics in here http://stats.free-dc.org/stats.php?page=proj&proj=lhc appeared for anyone, so seems something stuck or broken.
Meantime we have some progress on this exact http://lhcathomeclassic.cern.ch/sixtrack site.
Please take a look

I have another work unit stuck at my end as "Uploading" but marked as "In progress" by the LHC@home server.
Work unit: 18509433
Task: 39413334
Both are SixTrack v451.07 (pni)
I am running Xubuntu 13.10 and BOINC Manager v7.2.7 (x64)

---

I have another work unit stuck at my end as "Uploading" but marked as "In progress" by the LHC@home server.
Work unit: 18509433
Task: 39413334
Both are SixTrack v451.07 (pni)
I am running Xubuntu 13.10 and BOINC Manager v7.2.7 (x64)

Assuming you're running the BOINC v7.2.7 client, as well as managing it with the v7.2.7 Manager, that's a really old version, and early in the development cycle for v7.2 - I wouldn't be surprised if it still had a load of bugs left in. You would perhaps be better off upgrading both components to v7.2.42 - the current 'recommended' - but I know some Linux distros were slow to update their repositories.

You would perhaps be better off upgrading both components to v7.2.42 - the current 'recommended' - but I know some Linux distros were slow to update their repositories.

Over the years I've twice tried to upgrade BOINC Manager to a version newer than that provided by the repositories, and on both occasions ended up with a cocked-up PC. I'd also lose the two complete work packets plus other work that's under way.

There's nothing in the change logs about any of the versions between v7.2.7 and v7.2.42 altering how uploads work and I'm not having this trouble with any of my other projects.

Also, every upgrade to BOINC just introduces new bugs anyway, so I won't bother upgrading. Thanks for the suggestion anyway.

Incidentally, someone else reported the same problem last October - link - on an Intel processor running BOINC v7.0.64 on Windows 8.

---

Oh well, upgrading looks like my best bet after all, now I have 4 of these stuck packets:

Sat 19 Jul 2014 17:58:05 BST | LHC@home 1.0 | update requested by user
Sat 19 Jul 2014 17:58:06 BST | LHC@home 1.0 | Sending scheduler request: Requested by user.
Sat 19 Jul 2014 17:58:06 BST | LHC@home 1.0 | Not requesting tasks: too many uploads in progress
Sat 19 Jul 2014 17:58:08 BST | LHC@home 1.0 | Scheduler request completed

Sat 19 Jul 2014 18:01:10 BST | LHC@home 1.0 | update requested by user
Sat 19 Jul 2014 18:01:13 BST | LHC@home 1.0 | Sending scheduler request: Requested by user.
Sat 19 Jul 2014 18:01:13 BST | LHC@home 1.0 | Not requesting tasks: too many uploads in progress
Sat 19 Jul 2014 18:01:15 BST | LHC@home 1.0 | Scheduler request completed

---

So I upgraded a couple of weeks ago to v7.2.42 and it made no difference. Now I just have:

Sat 26 Jul 2014 16:48:57 BST | LHC@home 1.0 | Result w14_job_tracking_bb_np_nt_fset_240214_1k_x10_2__20__s__62.31_60.32__6_8__6__30_1_sixvf_boinc6864_0 is no longer usable
Sat 26 Jul 2014 16:48:57 BST | LHC@home 1.0 | Result w1_job_corr_bb_np_nt_fset_240214_1k_2__3__s__62.31_60.32__4_6__6__79.5_1_sixvf_boinc820_0 is no longer usable

through to

Thu 31 Jul 2014 21:22:30 BST | LHC@home 1.0 | Result w14_job_tracking_bb_np_nt_fset_240214_1k_x10_2__20__s__62.31_60.32__6_8__6__30_1_sixvf_boinc6864_0 is no longer usable
Thu 31 Jul 2014 21:22:30 BST | LHC@home 1.0 | Result w1_job_corr_bb_np_nt_fset_240214_1k_2__3__s__62.31_60.32__4_6__6__79.5_1_sixvf_boinc820_0 is no longer usable
Thu 31 Jul 2014 21:22:30 BST | LHC@home 1.0 | Result w-0.5_job.B1injection__15__s__64.281_59.3137__2_4__5__15.8824_1_sixvf_boinc7541_0 is no longer usable
Thu 31 Jul 2014 21:22:30 BST | LHC@home 1.0 | Result w-1.5_job.B1injection__22__s__64.281_59.3137__6_8__5__56.4707_1_sixvf_boinc11327_1 is no longer usable

so I've just done a 'Reset Project' and dealt with them that way. Hey ho.

---

Got another one ( work unit 25587189 )that has been stuck on 'Uploading' for days.

SixTrack v451.07 (pni)
Xubuntu 14.04
BOINC Manager v7.2.42 (x64)

---

I don't suppose this is of any interest to anyone, but I'm wondering why this completed packet has a different .zip file to the two others that are complete and ready to be uploaded, and whether that is related.

# pwd
/var/lib/boinc-client/projects/lhcathomeclassic.cern.ch_sixtrack
# ls -la
total 18520
drwxrwx--x  2 simon boinc   12288 Jan 26 20:41 .
drwxrwx--x 19 boinc boinc    4096 Jan 11 22:18 ..
-rwxr-xr-x  1 boinc boinc 5858789 Aug  4 17:31 sixtrack_lin32_4517_pni.linux
-rwxr-xr-x  1 boinc boinc 5858789 Aug  3 01:48 sixtrack_lin64_4517_pni.linux
-rwxr-xr-x  1 boinc boinc 5871077 Aug  5 06:00 sixtrack_lin64_4517_sse2.linux
-rw-r--r--  1 boinc boinc       0 Jan 26 14:03 w16_job_inj_nobb__26__s__62.28_60.31__10_12__6__61.5_1_sixvf_boinc16503_1_0
-rw-r--r--  1 boinc boinc  346161 Jan 26 13:58 w16_job_inj_nobb__26__s__62.28_60.31__10_12__6__61.5_1_sixvf_boinc16503.zip
-rw-r--r--  1 boinc boinc  296995 Jan 15 14:43 w200_HLLHC_RFcav_scana2_150.BOINC__33__s__62.31_60.32__4_6__5__16.5_1_sixvf_boinc18564.zip
-rw-r--r--  1 boinc boinc  344519 Jan 26 20:25 w2_job_tracking_nobb_np_nt_dq-4_50Hz_2_om1__30__s__62.31_60.32__22_24__6__69_1_sixvf_boinc22133.zip
-rw-r--r--  1 boinc boinc  344522 Jan 26 20:25 w2_job_tracking_nobb_np_nt_dq-4_50Hz_2_om1__30__s__62.31_60.32__22_24__6__84_1_sixvf_boinc22143.zip

---