Getting the 909 error again

[vsemaska]

I just tried to upload results and got the error:

STATUS 909 STRUCTURE WRITE ERROR

Thanks,
Vic

[The_Equivocator]

Yep... I'm getting it, too.

[Halon50]

They're probably working on the "new backend" for the servers right now.

[Halon50]

Looks like it's fixed already.

[The_Equivocator]

Nope. Now I'm getting a NO RESPONSE FROM SERVER message when I try to upload. I'm guessing that that'll be fixed relatively soon...

[stappel]

Can someone please check the server :) I'm expriansing a lot of errors like :


You seem to be experiencing network problems, or may be using an invalid handle. Please correct and try again.


And fellow team members also.

[[DPC]Mobster]

Some problems? That's the understatement of the year.

After every two fileset I get kicked off the server or something. Then I have to restart foldit.bat to flush my other results.

That is going to cost me the rest of the evening....

[Starfish]

I've also noticed that after uploading ~10,000 structures that I only got ~2200 extra in the stats :confused:

10K is 3/4 of my daily production on my only machine :bang:

[markhl]

I too am getting STATUS 909 STRUCTURE WRITE ERROR after the protein update. I'm sure the servers are just real busy, and the client will eventually upload the work.

[Pascal]

I also got the 909 some hours ago. Now everthing's alright again.

Report from Germany :haddock:

[markhl]

My client is OK now.
As Howard notes on the News page on his site, we can expect occasional STATUS 909 STRUCTURE WRITE ERROR messages because server is busy.

[Starfish]

Originally posted by stappel
Can someone please check the server :) I'm expriansing a lot of errors like :




And fellow team members also.

I can't upload either...

Looks like the name of the server cannot be resolved or something like that :confused:

I've added 6 extra nameserver ip's to the config of my FreeBSD machine, but the client refuses to connect for updating and uploading.

SOS! Safe Our Structures!

[struan]

I keep on getting a 907 error: STATUS 907 FOLD LOG PARSE ERROR/UNKNOWN HANDLE... even though the handle hasn't changed and I know it's good, since 3 seconds later it says handle found and continues to fold, buffering the previous set.

Curiously, though, (according to my stats) my machines at work have been able to send data back all night :confused:

[Brian the Fist]

I believe there were some troubles with our ISP last night which may have resulted in slow downs, and as well our server was overloaded (not by you, but by me..) for a few hours. Everything should be OK now though. If you still are getting error messages as of today onwards, let me know.

[Starfish]

I've noticed that my client will only connect when I don't have any old structures waiting to upload. (105 residue)

But when it starts, it doesn't attempt to update :confused:

The client shows no sign at all (not even asking me for permission) regarding the update.

And when I press 'Q' to let the client upload and quit it can't connect again?

Is the server still accepting 105 residue structures that we're cached?

[Brian the Fist]

Check your error.log for clues as to why your uploads are failing. It may just be timing out.

[Starfish]

The strange things is that, when the client tries to upload, it will try to connect to the server and within one second it'll also say "no response from server" and shut down.

It's the lastest FreeBSD client, completely re-installed yesterday.
Reaching the site isn't likely to be the problem because:

The FreeBSD machine is the router/firewall for my home LAN. I've got a few machines running behind it which can connect and upload without any problems :confused:

And both the router and the workstations have a list of about 6 different nameservers to resolve names and I doubt if that is the problem..

Of course this machine is a firewall, but I've had it running for at least 2 months now and without changing the firewall rules.. and as far as I understand the client hasn't changed in this area..

The handle has been checked multiple times and is correct.

The error.log file of the FreeBSD machine reports this:

========================[ Oct 17, 2002 7:23 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 4739} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

========================[ Oct 17, 2002 7:26 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 5672} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER
ERROR: [000.000] {foldtrajlite.c, line 4739} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

========================[ Oct 17, 2002 7:35 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 5672} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER
ERROR: [000.000] {foldtrajlite.c, line 4739} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

========================[ Oct 18, 2002 3:11 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 5672} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER
ERROR: [000.000] {foldtrajlite.c, line 4739} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

========================[ Oct 18, 2002 3:16 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 5672} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

========================[ Oct 18, 2002 3:33 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1162} Unable to check server status
ERROR: [000.000] {foldtrajlite.c, line 5672} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER
ERROR: [000.000] {foldtrajlite.c, line 4739} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER


Could you perhaps share the exact port and IP the client is trying to connect to? Perhaps I can get some more information if I monitor certain aspects more closely. Thank you in advance :)

[Brian the Fist]

If you use a packet sniffer, you can look for packets going to and coming from port 80 (http) on www.distributedfolding.org (206.248.62.8). Then you could see the dialog and what is wrong. (or show me and I will know whats wrong)

[Starfish]

I was just setting up a packet monitor, started the client...and everything was checking and uploading as it was supposed too? :confused:

I don't know why, but everything works again.. :D

Now let's get folding :cheers:
(at the blistering speed of 1 structure per 2 min. or so :))

Thank you for your time anyway Howard!