Waiting game indeed, moved my machines to wcg for the time being. I got a laptop, game pc, highend server, rasp pi and two phones ready to crunch... for now wcg's childhood cancer is the objective. Nicely small wu's

---

out of curiosity what platforms are u guys not receiving work???

I'm on latest ubuntu linux.

Mac and Windows here. It doesn't matter as the server status page the number in progress continues to fall and it shows there are no work units available. The only work available at times are resends.

I tried to contact TJM at B@P forum, but no luck. So evebody have to wait...

I looked up the contact e-mail for the domain, and e-mailed as well. As of yet, no response. I hope all is well in his world.

Maybe on vacation? Normally he notices after a day or so, but not this time.

If anyone has a plan that allows texting/calling Poland, there is a phone number in the WHOIS info for this domain. That is the only other thing I could think of.

ah ok i was asking because someone on a arm device was still getting units probably the resends then.

I get a few every now and then but that is it. The stats show the same thing, no new work, just completing what was already generated before whatever happened happened.

If you check here:
http://www.enigmaathome.net/server_status

You will see not much changes but the in progress goes down, the remaining will stay the same.

P1030680 (dictionary set: naval)
# of workunits: 91104000
done 55106674
remaining 35973094
in progress 24232
Restarts: target/avg/min 2000/1209/1166

Here is where it only shows 2 WU's available but there is really none:
Server state
Results ready to send6 2
High priority results7 0
Results sent last hour 455
Results in progress 24,250
Workunits waiting for validation 0
Workunits waiting for assimilation 20
Workunits waiting for deletion 0
Results waiting for deletion 0
Transitioner backlog (hours) 0

When the WU's drop below 1,000 the work generator is suppose to wakeup, it doesn't appear to be waking up. I believe that he has somethings hosted and other things running at his home. So the issue could be at either place.

I have seen work generation in paused state because of high load once for small time while this problem has existed.

Also I saw someone deleting spam post from forum about two or three weeks ago.

Also not getting work, but with a strange reason:

30.03.2017 21:18:39 | Enigma@Home | update requested by user
30.03.2017 21:18:41 | Enigma@Home | Sending scheduler request: Requested by user.
30.03.2017 21:18:41 | Enigma@Home | Not requesting tasks: don't need (CPU: job cache full; Intel GPU: )
30.03.2017 21:18:44 | Enigma@Home | Scheduler request completed

This isn't quite true. I have no tasks at all.

Also not getting work, but with a strange reason:

30.03.2017 21:18:39 | Enigma@Home | update requested by user
30.03.2017 21:18:41 | Enigma@Home | Sending scheduler request: Requested by user.
30.03.2017 21:18:41 | Enigma@Home | Not requesting tasks: don't need (CPU: job cache full; Intel GPU: )
30.03.2017 21:18:44 | Enigma@Home | Scheduler request completed

This isn't quite true. I have no tasks at all.

Are you running other projects on this machine?

If decide status page more attentive, you can see that "in progress" is decreasing and "With no results in progress" is increasing. But remark 5 says that "This should stay low, as it indicates work distribution problems". Something is wrong.

Yes, the work distributor is broken.

Are you running other projects on this machine?

Only WCG, since even before I signed up with E@H. Worked perefctly all the time. WCG keeps getting work.

The last time the workflow halted, how long was the downtime before the project leader fixed the issue?

I'm curious if this is about the expected length of time, or if we should be worried he was hit by a bus.

Thanks.

---

The past several times, only a few days. I might have died on a Friday evening and it was resolved by Monday. So this is truly an extended outage from the ones in the past. That is why I was wondering if he went on vacation or something.

The past several times, only a few days. I might have died on a Friday evening and it was resolved by Monday. So this is truly an extended outage from the ones in the past. That is why I was wondering if he went on vacation or something.

Thank you for that info. I will hold out hope.

Did notice a change when this showed up in notices:

Enigma@Home: Notice from server
Enigma 0.76b needs 3633355906759967822163392472118519509897936333762380538799349237146650150447872889552536326477638749902077901780791787612123406287017170888293484786718292115578013593460801536.00 MB RAM but only 22116.19 MB is available for use.

... first time to see that one. Apparently enigma now wants more RAM than exists in the entire galaxy.

---

Maybe it's trying to do a space/time trade off. ;)

Available workunits: m4_vroln72_1 P1030680 (dictionary set: naval)
# of workunits: 91,104,000
done 55,129,565
remaining 35,974,206
in progress 229
Restarts: target/avg/min 2000/1210/1179
Server stats
Workunits validated last hour 1
CPU hours/hour 1 8.1
Error rate 2 5.4%
Result average turnaround time (hours) 3 20.99
Workunit state
Active blocks: 4 45,299
With no results in progress 5 45,200
Server state
Results ready to send 6 2
High priority results 7 0
Results sent last hour 0
Results in progress 240
Workunits waiting for validation 0
Workunits waiting for assimilation 10
Workunits waiting for deletion 0
Results waiting for deletion 0
Transitioner backlog (hours) 0

1) - That means the current Enigma@Home speed is equal to 8.1 Athlon Thunderbirds 1.4GHz. It's average from last 6 hours.
2) - percentage number of results which failed on the client side (server_state = 5, outcome = 3 -> client error)
3) - average time between sending result and receiving it back.
4) - number of active workunits (keyrange blocks) in the master database.
5) - number of active workunits with 0 results in progress.This should stay low, as it indicates work distribution problems
6) - currently workunit generator wakes up when the result ready to send goes below 1k
7) - number of workunits marked for processing on hosts with average turnaround time lower than 3 days.