Down for about 5 hours 2nd day in a row, from 23:38 UTC to 04:40 UTC. Negative hours back again and of course lots of missed hours and information for the results of this project thanks to the 1 hour WUs.

---

Down for about 5 hours 2nd day in a row, from 23:38 UTC to 04:40 UTC. Negative hours back again and of course lots of missed hours and information for the results of this project thanks to the 1 hour WUs.

I'm beginning to wonder if it's heat related, no idea where Sebastien lives so it's pure conjecture on my part, but if so maybe a better cpu cooler would help the pc's stay nice and cool.

In last 2 weeks the daily negative hours ebb and flow with no apparent reason or pattern that's obvious, along with the hours long website or database being offline something is not right.

Would be nice to hear from Sebastian or whoever is supposedly helping him as to what is broken. Been going on as far as I can tell for over 6 continuous months now.

---

In last 2 weeks the daily negative hours ebb and flow with no apparent reason or pattern that's obvious, along with the hours long website or database being offline something is not right.

Would be nice to hear from Sebastian or whoever is supposedly helping him as to what is broken. Been going on as far as I can tell for over 6 continuous months now.

I agree knowing means we could possibly help him get the resources he and his Team need to keep this going at it's normal exceptional rate.

Another extended outage and more negative hours overnight.

I was comparing my total hours and task hours here at WuProp versus what Free-DC is showing based on the WuProp database xml exports and there's a substantial difference in total and individual project tasks hours...

Free-DC hours: 1,471,861.70

WuProp hours: 1,468,335

That's a difference of 3526.7 hours!!!
APPARENTLY SOMETHING IS REALLY BROKEN.

Please check your hours across the two websites to see if they match and post a message what you discover.

---

For me FreeDC shows 158,396.37 combined, WUprop 158,391, so just 5 hours difference.

---

Server not reachable every few minutes since 00:40, my Android was out of WUProp work for 14 hours because of it, always got "feeder not running" when asking for work.

---

For me Free-DC shows 6,460,965.72 hours while wuprop shows 6,446,852 a difference of over 14 thousands hours!!!

Free-DC https://stats.free-dc.org/user/wup/1733

Server not reachable every few minutes since 00:40, my Android was out of WUProp work for 14 hours because of it, always got "feeder not running" when asking for work.

Hi

I had the same issue with WU-Prop and the same error messages from:

03/09/2023 02:40:32 | WUProp@Home | Server error: feeder not running

until:

03/09/2023 16:14:05 | WUProp@Home | Started download of data_collect_v4_xxxxxxx_xxxxxx

(Times are in UTC)

And all has been well ever since.

Other websites run by the same admin, also had issues, such as Formula BOINC and the L'AF team website....but all seem to be OK now. :-)

regards
Tim

Server not reachable every few minutes since 00:40, my Android was out of WUProp work for 14 hours because of it, always got "feeder not running" when asking for work.

Hi

I had the same issue with WU-Prop and the same error messages from:

03/09/2023 02:40:32 | WUProp@Home | Server error: feeder not running

until:

03/09/2023 16:14:05 | WUProp@Home | Started download of data_collect_v4_xxxxxxx_xxxxxx

(Times are in UTC)

And all has been well ever since.

Other websites run by the same admin, also had issues, such as Formula BOINC and the L'AF team website....but all seem to be OK now. :-)

regards
Tim

Since it was other websites as well I wonder if it was a power problem for him or a Server problem an ISP problem? I can see one website go down but several usually means something more serious, hopefully it was just upgrades for better reliability stuff!!

Since it was other websites as well I wonder if it was a power problem for him or a Server problem an ISP problem? I can see one website go down but several usually means something more serious, hopefully it was just upgrades for better reliability stuff!!

Hiya

Yes, the fact that all three websites came back online at about the same time, rather implies it was a network issue, either with a server outage, maybe a managed "network switch" that had a lock-up, or maybe some sort of DNS attack?

Unlikely to be a power issue as most ISPs, have standby/back-up generators and/or UPS systems, to take over if there's a total power outage.

But it's not a good thing for the servers to be offline for about 14 hours...even if it is Sunday and most engineers are at home enjoying the weekend.

regards
Tim

Since it was other websites as well I wonder if it was a power problem for him or a Server problem an ISP problem? I can see one website go down but several usually means something more serious, hopefully it was just upgrades for better reliability stuff!!

Hiya

Yes, the fact that all three websites came back online at about the same time, rather implies it was a network issue, either with a server outage, maybe a managed "network switch" that had a lock-up, or maybe some sort of DNS attack?

Unlikely to be a power issue as most ISPs, have standby/back-up generators and/or UPS systems, to take over if there's a total power outage.

But it's not a good thing for the servers to be offline for about 14 hours...even if it is Sunday and most engineers are at home enjoying the weekend.

regards
Tim

Actually I was thinking of a business or more likely home power outage or even neighborhood outage due to the storms that are on the News everywhere right now.

In fact my wife finally relented and in about 2 weeks I will finally get a whole house generator for my new home here at the beach in North Carolina, USA. We had one at my old home around the corner but here at the new one we didn't until she sat thru a 3 hour power outage in the middle of the day and decided that if it happened at night time we would be in trouble as we both use CPAP machines. She thought we would just pack up and drive to someplace that has power but when she called a couple places she realized the costs were sky high due to the demand from the short outage that we did have.

Anyway I'm glad the sites are back up and I hope they stay that way for a good long time!!

Keep on crunching
mikey

28/11/2023 17:01:25 | WUProp@Home | Server can't open database
28/11/2023 20:01:55 | WUProp@Home | Server error: feeder not running
28/11/2023 21:02:03 | WUProp@Home | Server error: feeder not running
28/11/2023 22:02:07 | WUProp@Home | Server error: feeder not running
28/11/2023 23:02:12 | WUProp@Home | Server error: feeder not running
29/11/2023 00:02:18 | WUProp@Home | Server error: feeder not running
29/11/2023 02:02:28 | WUProp@Home | Server error: feeder not running
29/11/2023 04:02:37 | WUProp@Home | Server error: feeder not running
29/11/2023 05:02:42 | WUProp@Home | Server error: feeder not running
29/11/2023 06:02:46 | WUProp@Home | Server error: feeder not running
29/11/2023 08:02:55 | WUProp@Home | Server error: feeder not running
29/11/2023 09:03:00 | WUProp@Home | Server error: feeder not running
29/11/2023 10:03:05 | WUProp@Home | Server error: feeder not running
29/11/2023 11:03:10 | WUProp@Home | Server error: feeder not running
29/11/2023 12:03:14 | WUProp@Home | Server error: feeder not running
29/11/2023 13:03:18 | WUProp@Home | No tasks sent
29/11/2023 14:03:38 | WUProp@Home | Server error: feeder not running
29/11/2023 15:03:42 | WUProp@Home | Server error: feeder not running
29/11/2023 16:03:47 | WUProp@Home | Server error: feeder not running
29/11/2023 17:03:52 | WUProp@Home | Server error: feeder not running
29/11/2023 18:03:56 | WUProp@Home | Server error: feeder not running
29/11/2023 20:04:05 | WUProp@Home | Server error: feeder not running
29/11/2023 21:04:10 | WUProp@Home | Server error: feeder not running
29/11/2023 22:04:16 | WUProp@Home | Server error: feeder not running
29/11/2023 23:04:21 | WUProp@Home | Server error: feeder not running
30/11/2023 00:04:26 | WUProp@Home | Server error: feeder not running
30/11/2023 02:04:35 | WUProp@Home | Server error: feeder not running
30/11/2023 03:04:40 | WUProp@Home | Server error: feeder not running
30/11/2023 04:04:44 | WUProp@Home | Server error: feeder not running
30/11/2023 05:04:49 | WUProp@Home | Server error: feeder not running
30/11/2023 06:04:55 | WUProp@Home | Server error: feeder not running
30/11/2023 08:05:06 | WUProp@Home | Server error: feeder not running

Lots of server issues again.

---

I have found that when I have a WU that tries to report when these server errors are present then it wont try to report the WU again.

The WU will sit there for hours (longest was 6 hours) before I have to manually update the project to make it report.

It is a annoying but I appreciate the fact the project is still going.

Conan

---

I have found that when I have a WU that tries to report when these server errors are present then it wont try to report the WU again.

The WU will sit there for hours (longest was 6 hours) before I have to manually update the project to make it report.

It is a annoying but I appreciate the fact the project is still going.

Conan

Mine also get stuck in the 'trying to download or 'trying to upload' phase and I have to click multiple times to get it to go thru. I realize that 3 or the old 6 hours tasks have alot more data to process but would it make things easier on the Server if we went back to longer tasks? I also realize the answer could be 'yes but' as in the more data means more processing time which could mean the Server itself is busier so less time for those longer downloads.