I also have a work unit hanging like this. I don't see any activity except for the clock.

---

I've got a slew of units that just don't seem to be processing on all three of my machines. One was showing that it had been running for over 50 hours and still had 60 some hours to go. I stopped it and chose another one, but it seems to be in that same loop. I did this on all three computers and still nothing looks normal. When I ask for the graphic, it doesn't show anything happening.

Can you give me the name of this workunit, or better yet a link to its page on the server?

Thanks,

Eric

---

@SETIEric@qoto.org (Mastodon)

Here it is, 27mr99aa.29951.15681.579834.3.238_4
Thanks for your help..

---

Quick question:

Are there some workunits that have simply been wiped out entirely in correcting this problem? I crunched, uploaded, and reported a workunit yesterday that was completed successfully in 6.5 hours but now does not appear in my account information at all. It appears to have simply vanished off the face of the earth. It is in my BoincView log as downloaded and crunched but does not appear in my results list. I'm quite confused so if someone might enlighten me I would be much obliged :)

Thanks,

Dig

I've got a slew of units that just don't seem to be processing on all three of my machines. One was showing that it had been running for over 50 hours and still had 60 some hours to go. I stopped it and chose another one, but it seems to be in that same loop. I did this on all three computers and still nothing looks normal. When I ask for the graphic, it doesn't show anything happening.

Can you give me the name of this workunit, or better yet a link to its page on the server?

Thanks,

Eric

I take it this means that the issue(s) with the splitters have not been corrected?

---

I take it this means that the issue(s) with the splitters have not been corrected?

The wu in question here wuid-8030467 was split in May, so doesn't say anything about splitter-fix working or not...

I take it this means that the issue(s) with the splitters have not been corrected?

The wu in question here wuid-8030467 was split in May, so doesn't say anything about splitter-fix working or not...

Yep, that's one of the bad ones. Note that it has been cancelled. Unfortunately, not until it had been send out four times.

---

@SETIEric@qoto.org (Mastodon)

I've got a slew of units that just don't seem to be processing on all three of my machines. One was showing that it had been running for over 50 hours and still had 60 some hours to go. I stopped it and chose another one, but it seems to be in that same loop. I did this on all three computers and still nothing looks normal. When I ask for the graphic, it doesn't show anything happening.

Can you give me the name of this workunit, or better yet a link to its page on the server?

Thanks,

Eric

Hi Eric,

I'm not sure exactly what you want, but here is what appears in the Work area of Boinc Manager.

27mr99aa.29951.15681.579834.3.67_0

However, there are several more that when started, seemed that they too were going backwards and not producing any graphics. Some of which start with the same numbers as the unit above, but some differ as well. What should I do with these units? I don't seem to be able to delete them from the Boinc Mgr program. Do I need to find their home on my drive and kill them off there or will Seti somehow rid me of them?

Thanks, Allen

---

Eric the link to Result ID of Wayne Millers' wu is 27mr99aa.29951.15681.579834.3.238_4

http://setiathome.berkeley.edu/workunit.php?wuid=80304676

errors => Cancelled

:)

---

SETI@Home Informational message -9 result_overflow
with a general handicap of 80% and it makes much d' efforts for the community and s' expimer, thank you d' to be understanding.

I take it this means that the issue(s) with the splitters have not been corrected?

The wu in question here wuid-8030467 was split in May, so doesn't say anything about splitter-fix working or not...

Yep, that's one of the bad ones. Note that it has been cancelled. Unfortunately, not until it had been send out four times.

Eric,

Here are a couple more....

27mr99aa.29951.15681.579834.3.82_3
27mr99aa.29951.15681.579834.3.88_0

I'm not sure how many more I have. Without trying them, is there anything one can do to get rid of them?

---

I'm not sure how many more I have. Without trying them, is there anything one can do to get rid of them?

If the beginnings of their names appear in this list then you should probably delete or abort them.

Eric

---

@SETIEric@qoto.org (Mastodon)

Thank you Eric...

---

I'm not sure how many more I have. Without trying them, is there anything one can do to get rid of them?

If the beginnings of their names appear in this list then you should probably delete or abort them.

Eric

Thanks for the list, Eric.

---

I have encountered a few that continue to use proc without updating the state.sah file.

28fe99aa.18483.22561.934666.3 does not appear to be on the list of known problems.

---

The following unit hung up at 8+ hours work time and had to be restarted at that point claimed credit for only 4 hours of cpu time:20mr99aa.22885.24002.379824.3.94_2

---

Ok, here's a list of units (not on Eric's 'bad' list) which I found busily using cpu, but neither updating percentage complete nor updating the state.sah file for more than 24 hours.

Note these were scattered across a half-dozen servers, and other work units (on those running more than one unit) appeared to be proceeding normally.

28fe99aa.18483.22561.934666.3.112
03mr99ab.9678.28129.1047142.3.0
20mr99aa.15250.20145.984656.3.71
30au99ab.18587.29250.573572.3.172
24mr99ab.175.2848.697140.3.2
22mr99aa.23950.25105.54842.3.101
23mr99aa.23594.22768.565904.3.154
14ja99aa.26346.5648.947164.3.60

Is there anything else I should look at when I find more of them?

---

I'll check out whether they should be in the list or not. It could be that I missed a few...

Eric

Ok, here's a list of units (not on Eric's 'bad' list) which I found busily using cpu, but neither updating percentage complete nor updating the state.sah file for more than 24 hours.

Note these were scattered across a half-dozen servers, and other work units (on those running more than one unit) appeared to be proceeding normally.

28fe99aa.18483.22561.934666.3.112
03mr99ab.9678.28129.1047142.3.0
20mr99aa.15250.20145.984656.3.71
30au99ab.18587.29250.573572.3.172
24mr99ab.175.2848.697140.3.2
22mr99aa.23950.25105.54842.3.101
23mr99aa.23594.22768.565904.3.154
14ja99aa.26346.5648.947164.3.60

Is there anything else I should look at when I find more of them?

---

@SETIEric@qoto.org (Mastodon)

If you've still got any of these, could you send me the workunit file and the contents of stderr? (email to my last name at ssl.berkeley.edu) Which core client version are you using?

Ok, here's a list of units (not on Eric's 'bad' list) which I found busily using cpu, but neither updating percentage complete nor updating the state.sah file for more than 24 hours.

Note these were scattered across a half-dozen servers, and other work units (on those running more than one unit) appeared to be proceeding normally.

28fe99aa.18483.22561.934666.3.112
03mr99ab.9678.28129.1047142.3.0
20mr99aa.15250.20145.984656.3.71
30au99ab.18587.29250.573572.3.172
24mr99ab.175.2848.697140.3.2
22mr99aa.23950.25105.54842.3.101
23mr99aa.23594.22768.565904.3.154
14ja99aa.26346.5648.947164.3.60

Is there anything else I should look at when I find more of them?

---

@SETIEric@qoto.org (Mastodon)

T2600 CPU
WinXP SP2 w/ latest patches.

BOINC client 5.4.9 for windows_intelx86
setiathome_5.15_windows_intelx86.exe

WU 22mr99ab.5386.10081.736064.3.0_0
at this post,
8 hours of CPU time 23% progress 9 hours to completion

My average is ~02:20:00 per WU

---