Dnetc remains offline (it is now mid afternoon in Poland where they are located).

While this is an announced maintenance to upgrade their storage system to RAID 5, it is possible that either the upgrade process is taking longer than they had hoped or that they encountered problems similar to those which they saw when they performed a software upgrade a couple of weeks ago.

The folks at Dnetc are struggling to recover from their latest upgrade efforts.

It seems, just as happened during their software upgrade two weeks ago, some unexpected event occurred in the middle of this weeks hardware upgrade to RAID 5.

Their site has been totally offline for the past 36 hours. Sometime yesterday, they got to a point where their homepage had the simple phrase 'It Works!' - they used that phrase during some of their software upgrade problems as they were trying to recovery. Then their site went dark for another 18 hours. Today, we are presented with a new phrase - which suggests a level of frustration as they try to get things going. The total content of their home page (translated to English):

Theory - is when you know everything, but nothing works.

Practice - is when everything works but nobody knows why.

Here we combine theory and practice - nothing works and nobody knows why!


The original Polish:

Teoria - to kiedy wiecie wszystko, lecz nic nie pracuje.

Praktyka - to kiedy wszystko pracuje, lecz nikt nie wie dlaczego.

W tym miejscu laczymy teorie i praktyke - nic nie pracuje i nikt nie wie dlaczego!


I do hope they are able to recover from this upgrade soon.

The Dnetc folks are getting a bit further with their recovery efforts.

Home page report now:


Warning: mysql_pconnect() [function.mysql-pconnect]: Access denied for user 'dnetc'@'localhost' (using password: NO) in /home/serwer/projects/dnetc/html/inc/db.inc on line 39
Unable to connect to database - please try again later Error: 1045Access denied for user 'dnetc'@'localhost' (using password: NO)

From SETI front page

Our upload (results) storage area is full. The project is down until we resolve this
25 Sep 2010 7:57:24 UTC

---

Posted by Jeff Cob, Seti admin:

Reality got a little ahead of us on this one. We were days, a week tops, away from migrating upload service from bruno to bambi. This will double our upload space and allow us to turn off bruno.

We will now move this up and make it top priority come Monday. We need to reconfigure the raid on bambi and then let the raid sync. At that point we can both turn the projects on and start migrating the results from bruno to bambi. We hope that this will be early in the week. We'll then leave the projects on through next weekend, ie no normal 3 day outage.

Aqua is offline -- 'disk full' -- possibly a result of their newer batch of much smaller work units clogging things up a lot faster than they anticipated.

Enigma seems to be up but all my computers report it as off-line:
9/26/2010 11:37:05 AM Project communication failed: attempting access to reference site
9/26/2010 11:37:10 AM Internet access OK - project servers may be temporarily down.

JHPArizona

I have lots of results ready to report to SETI and SETI Beta but the project is still down. Website is up but with only the header and this message:
Unable to connect to database - please try again later Error: 2003Can't connect to MySQL server on 'mork' (4)

The only good thing is they seem to 'REALLY' extended the due dates as most are due in Nov and even the Oct WU that is done isn't due until 10/26

JHPArizona

Einstein status page shows all is good but I have not been able to communicate with the project since 9/25.

Anybody else having problems with Einstein@Home?

JHPArizona

Anybody else having problems with Einstein@Home?

No problems here:

26/09/2010 12:13:02|Einstein@Home|[sched_op_debug] Starting scheduler request
26/09/2010 12:13:02|Einstein@Home|Sending scheduler request: Requested by user.  Requesting 0 seconds of work, reporting 1 completed tasks
26/09/2010 12:13:08|Einstein@Home|Scheduler request succeeded: got 0 new tasks

Perhaps your problems with Enigma are the same?

Gruß,
Gundolf

Seti update:

Perhaps they started work on their migration to other servers early, as since some hours all you'll get is:

Project is down
The project's database server is down. Please check back in a few hours.

SETI@home
Unable to connect to database - please try again later Error: 2013Lost connection to MySQL server at 'reading initial communication packet', system error: 113

Also

SETI@home/AstroPulse Beta
Unable to connect to database - please try again later Error: 2013Lost connection to MySQL server at 'reading initial communication packet', system error: 113

---

Anybody else having problems with Einstein@Home?


No problems here:
26/09/2010 12:13:02|Einstein@Home|[sched_op_debug] Starting scheduler request
26/09/2010 12:13:02|Einstein@Home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
26/09/2010 12:13:08|Einstein@Home|Scheduler request succeeded: got 0 new tasks

Perhaps your problems with Enigma are the same?
Well.... If it were only one of my computers I would believe it to be a problem on my side. Since it is all of my home computers (3) I find it harder to believe all three of them suddenly developed a problem. Here is the listing from my Linux box:
Sun 26 Sep 2010 11:23:48 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:23:50 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:24:52 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:24:53 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:26:01 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:26:03 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:27:03 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:27:09 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:29:22 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:29:25 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:35:10 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:35:12 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:39:46 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:39:48 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:52:18 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:52:22 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 11:55:29 AM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 11:55:33 AM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 01:10:21 PM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 01:10:23 PM MST Internet access OK - project servers may be temporarily down.
Sun 26 Sep 2010 01:27:54 PM MST Project communication failed: attempting access to reference site
Sun 26 Sep 2010 01:27:56 PM MST Internet access OK - project servers may be temporarily down.

Similar responses from my other 2 boxes (Windows and OS X)

Enigma on the other hand has unclogged and uploaded WUs and downloaded new ones.

JHPArizona

Well things are improving at SETI :^)
The status page is up but Mork is still disabled so the database is not available.

JHPArizona

Well.... If it were only one of my computers I would believe it to be a problem on my side.

But since it doesn't happen to other users, it seems to be at your side anyway. Perhaps your ISP? To get more information, turn on some debug flags in cc_config.xml.

And since this is obviously not about a project outage, please start a new thread if you have any more questions.

Gruß,
Gundolf

Thanks, I did not know that I could set debug flags in cc_config.XML. I have taken a look at http://boinc.berkeley.edu/wiki/Client_configuration and will see what I can find. And yes, this will be the last post on this issue as I did get a bit OT with it. My computers have all made contact with Einstein@home so ..... maybe it was a problem with my ISP..... would not be the first time they blocked something on me without warning.....

JHPArizona

This thread is for reporting project outages only. If you want help on any problem, please start your own thread, or find a thread that's dealing with your problem already and add to it.

As for posting your email address, don't! These forums are read by spy-bots, which just like to gather information like that and send you all kinds of spam. Don't post your account keys for your projects either, nor your telephone number.

These forums are manned by volunteers. We're not going to email you or phone you.

Again, this thread is for reporting project outages, not to ask for help. Please be kind and post your requests for help anywhere else on this forum. Sub-forums enough.

Is there an issue with SETI@home servers? They seem to have been down more then a day.

Anybody else having problems with Einstein@Home?

Yep.

Web site was down before but now back up. According to server status page the scheduler was off and most of the wu generators (29Sep2010 at 12:45 UTC). Checking just now (13:00 UTC) it seems most of it is back on-line apart from ABP wu generators.

Dnetc is offline -- they went totally offline about 11 hours ago -- no home page, no server access. It may be due to a software upgrade they were planning -- hardware and software upgrades for them often keep them offline for 2 to 4 days for some reason.

To the person asking about SETI -- they ran out of disk space earlier than they had anticipated so they are in the process of expanding and rebuilding their RAID array and relocating various resources between their several servers. The last status report they offered (over the weekend) was that they hope to be up early this week -- perhaps that was a tad optimistic.