in the cafe, the moderators contact thread, the status indicates a change to that thread 1 hour ago. however the date of the last post was something like november 25. was there an edit there? I don't see anything missing since I last looked at that thread. virtual beer was the last thing mentioned in there prior to the crash.

That was me moving things around this morning. The contact tread is intended to be work that is in progress. I took items that have been addressed, and remained there for a few weeks, and moved them to the archive mentioned in the first post of the thread. And somehow moving a post to a thread marks it as recently changed, but the date on the post that was moved to it may have been from months ago.

...anyway, that one isn't any problem with the new server website code.

---

Rosetta Moderator: Mod.Sense

I'm having posts modded into obliviion and the only reason given is "Archiving" !

WTF ?????? What new imaginary rule did I violate now????

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

they store old threads in an archive, otherwise if your the first time in a message board, it would take ages to load, especially with an crappy inet connection. so they put posts in a archive so it keeps remained but dousn't gives a tremendous load on the servers and the pc's of the users.

so you didn't violate a rule.

Quick little tip for bypassing the spam filter. If you're posting a link to a specific task, work unit, or computer, to can add a ampersand ( & ) to the end of the URL and not have to edit the post. Examples:

Computer: https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=186636&
Computer results: https://boinc.bakerlab.org/rosetta/results.php?hostid=186636&
Job result: https://boinc.bakerlab.org/rosetta/result.php?resultid=125044738&

Quick little tip for bypassing the spam filter. If you're posting a link to a specific task, work unit, or computer, to can add a ampersand ( & ) to the end of the URL and not have to edit the post.

Hello BitSpit,

Great workaround. It really works!
Homepage: https://boinc.bakerlab.org/rosetta/& has to be changed in: https://boinc.bakerlab.org/rosetta/#.

Thanks,
Path7.

I'm posting the three links without editing or other workarounds. If you see this post then the problem is fixed and no workaround is needed anymore.

https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=186636
https://boinc.bakerlab.org/rosetta/results.php?hostid=186636
https://boinc.bakerlab.org/rosetta/result.php?resultid=125044738

Ya think? So is that why there are threads going back 811 days to the beginning of the project???

No - it's just mods screwing with things again.

they store old threads in an archive, otherwise if your the first time in a message board, it would take ages to load, especially with an crappy inet connection. so they put posts in a archive so it keeps remained but dousn't gives a tremendous load on the servers and the pc's of the users.
so you didn't violate a rule.

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

maybe we should make the forum, non resisable, so if someone posts a long link or something it brakes it up. cause now in the problems with 5.90/5.91 the thread are really big, now i have a quiet high resolution, 1280*1024, but if someone with 800*600 or 1024*768, tries to view this he has to drag forever to read.

maybe we should make the forum, non resisable, so if someone posts a long link or something it brakes it up. cause now in the problems with 5.90/5.91 the thread are really big, now i have a quiet high resolution, 1280*1024, but if someone with 800*600 or 1024*768, tries to view this he has to drag forever to read.

Agreed. I just posted here, good luck, beware of wrist injury!

Tim

---

gogogo

was there a breakdown in the message board server?
I have my settings as most recent post first and it is showing today threads that are ancient in time as being new.

whats up with this?

---

Why is the website so slow, and why cant I attach to the server?

sorry for the double post, didn't think the first one went ;)

Hey, no problem here, the databases are in a bit of ping pong mode. I sure do wish we had some newsflash regarding this sort of thing here, or for that matter a technical news update -- the technical news page hasn't been updated since November.

sorry for the double post, didn't think the first one went ;)

---

Hey, no problem here, the databases are in a bit of ping pong mode. I sure do wish we had some newsflash regarding this sort of thing here, or for that matter a technical news update -- the technical news page hasn't been updated since November.

sorry for the double post, didn't think the first one went ;)

---

Well it's dog slow here in "Blighty" (UK to anyone not familiar with the term !)

BOINC Manager having trouble uploading

18/01/2008 14:47:30|rosetta@home|Temporarily failed upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0: system connect
18/01/2008 14:47:30|rosetta@home|Backing off 6 min 6 sec on upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 14:47:31||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 14:53:36|rosetta@home|Started upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 14:58:48||Project communication failed: attempting access to reference site
18/01/2008 14:58:48|rosetta@home|Temporarily failed upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0: http error
18/01/2008 14:58:48|rosetta@home|Backing off 17 min 43 sec on upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 14:58:50||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 15:16:32|rosetta@home|Started upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 15:16:54||Project communication failed: attempting access to reference site
18/01/2008 15:16:54|rosetta@home|Temporarily failed upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0: system connect
18/01/2008 15:16:54|rosetta@home|Backing off 1 hr 56 min 55 sec on upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 15:16:56||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:05:11|rosetta@home|Sending scheduler request: To fetch work. Requesting 24 seconds of work, reporting 0 completed tasks
18/01/2008 16:10:16||Project communication failed: attempting access to reference site
18/01/2008 16:10:16|rosetta@home|Scheduler request failed: Timeout was reached
18/01/2008 16:10:18||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:11:16|rosetta@home|Sending scheduler request: To fetch work. Requesting 384 seconds of work, reporting 0 completed tasks
18/01/2008 16:11:38||Project communication failed: attempting access to reference site
18/01/2008 16:11:40||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:11:41|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 16:12:41|rosetta@home|Sending scheduler request: To fetch work. Requesting 466 seconds of work, reporting 0 completed tasks
18/01/2008 16:13:03||Project communication failed: attempting access to reference site
18/01/2008 16:13:04||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:13:06|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 16:14:06|rosetta@home|Sending scheduler request: To fetch work. Requesting 549 seconds of work, reporting 0 completed tasks
18/01/2008 16:19:19||Project communication failed: attempting access to reference site
18/01/2008 16:19:20||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:19:22|rosetta@home|Scheduler request failed: Timeout was reached
18/01/2008 16:20:22|rosetta@home|Sending scheduler request: To fetch work. Requesting 916 seconds of work, reporting 0 completed tasks
18/01/2008 16:20:44||Project communication failed: attempting access to reference site
18/01/2008 16:20:45||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:20:47|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 16:22:47|rosetta@home|Sending scheduler request: To fetch work. Requesting 1058 seconds of work, reporting 0 completed tasks
18/01/2008 16:23:09||Project communication failed: attempting access to reference site
18/01/2008 16:23:10||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:23:12|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 16:29:22|rosetta@home|Sending scheduler request: To fetch work. Requesting 1445 seconds of work, reporting 0 completed tasks
18/01/2008 16:29:44||Project communication failed: attempting access to reference site
18/01/2008 16:29:45||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 16:29:47|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 16:47:03|rosetta@home|Sending scheduler request: To fetch work. Requesting 2488 seconds of work, reporting 0 completed tasks
18/01/2008 16:47:23|rosetta@home|Scheduler request succeeded: got 1 new tasks
18/01/2008 16:47:25|rosetta@home|Started download of native_1zpy_.fasta.gz
18/01/2008 16:47:25|rosetta@home|Started download of native_1zpy_.psipred_ss2.gz
18/01/2008 16:47:26|rosetta@home|Finished download of native_1zpy_.fasta.gz
18/01/2008 16:47:26|rosetta@home|Finished download of native_1zpy_.psipred_ss2.gz
18/01/2008 16:47:26|rosetta@home|Started download of boinc_native_aa1zpy_03_05.200_v1_3.gz
18/01/2008 16:47:26|rosetta@home|Started download of boinc_native_aa1zpy_09_05.200_v1_3.gz
18/01/2008 16:47:34|rosetta@home|Finished download of boinc_native_aa1zpy_09_05.200_v1_3.gz
18/01/2008 16:47:34|rosetta@home|Started download of native_1zpy.pdb.gz
18/01/2008 16:47:36|rosetta@home|Finished download of native_1zpy.pdb.gz
18/01/2008 16:47:39|rosetta@home|Finished download of boinc_native_aa1zpy_03_05.200_v1_3.gz
18/01/2008 17:13:51|rosetta@home|Started upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 17:14:34|rosetta@home|Finished upload of 1g2z__BOINC_TWIST_RINGS_TWIST_ANGLE_SYMM_FOLD_AND_DOCK_RELAX-1g2z_-crystal_foldanddock__2599_37539_0_0
18/01/2008 17:39:06|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
18/01/2008 17:39:28||Project communication failed: attempting access to reference site
18/01/2008 17:39:30||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 17:39:31|rosetta@home|Scheduler request failed: Couldn't connect to server
18/01/2008 17:40:31|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
18/01/2008 17:40:51|rosetta@home|Scheduler request succeeded: got 0 new tasks
18/01/2008 18:14:11|rosetta@home|Computation for task 1scjB_BOINC_ABRELAX_VF_IGNORE_THE_REST-S25-7-S3-9--1scjB-vf__2602_31_0 finished
18/01/2008 18:14:11|rosetta@home|Starting 1tig__BOINC_ABRELAX_VF_IGNORE_THE_REST-S25-16-S3-10--1tig_-vf__2601_194_0
18/01/2008 18:14:11|rosetta@home|Starting task 1tig__BOINC_ABRELAX_VF_IGNORE_THE_REST-S25-16-S3-10--1tig_-vf__2601_194_0 using rosetta_beta version 593
18/01/2008 18:14:13|rosetta@home|Started upload of 1scjB_BOINC_ABRELAX_VF_IGNORE_THE_REST-S25-7-S3-9--1scjB-vf__2602_31_0_0
18/01/2008 18:14:36|rosetta@home|Finished upload of 1scjB_BOINC_ABRELAX_VF_IGNORE_THE_REST-S25-7-S3-9--1scjB-vf__2602_31_0_0
18/01/2008 19:20:20|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
18/01/2008 19:25:31||Project communication failed: attempting access to reference site
18/01/2008 19:25:33||Access to reference site succeeded - project servers may be temporarily down.
18/01/2008 19:25:35|rosetta@home|Scheduler request failed: Timeout was reached
18/01/2008 19:26:35|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
18/01/2008 19:26:45|rosetta@home|Scheduler request succeeded: got 0 new tasks

So maybe the webserver need "bouncing" as ping to IP is "fine"

Pinging boinc.bakerlab.org [140.142.20.103] with 32 bytes of data:

Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=178ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=178ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=178ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=176ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=178ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48
Reply from 140.142.20.103: bytes=32 time=177ms TTL=48

Ping statistics for 140.142.20.103:
Packets: Sent = 36, Received = 36, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 178ms, Average = 176ms

---

Right -- would be nice to get some sort of feedback from the admins here. I'd guess they know there is something amiss, but can't be sure as there has been a rather long bout of silence regarding technical matters.

Well it's dog slow here in "Blighty" (UK to anyone not familiar with the term !)

---

any news is like pulling teeth with this project

Right -- would be nice to get some sort of feedback from the admins here. I'd guess they know there is something amiss, but can't be sure as there has been a rather long bout of silence regarding technical matters.

Well it's dog slow here in "Blighty" (UK to anyone not familiar with the term !)

---

connection has been a bit intermittent from here too - was able to connect more than not though... and seems fine now...

---

Indeed, whatever problem that was going on (recognizing that all we have is speculation here) has, at least for the moment, been resolved (or alternatively, temporarily fixed itself).

connection has been a bit intermittent from here too - was able to connect more than not though... and seems fine now...

---