upload issues and other news (Oct 5, 2007)

Message boards : Technical News : upload issues and other news (Oct 5, 2007)
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile Gary Charpentier Crowdfunding Project Donor*Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 25 Dec 00
Posts: 25391
Credit: 48,644,813
RAC: 25,169
United States
Message 655499 - Posted: 7 Oct 2007, 0:37:35 UTC - in response to Message 655492.  

I used to live about a wavelength from a commercial 10kW AM band radio transmitter. Everything was hot! Of course powerline likes to get into everything too. Sometimes it is easier to shield the powerlines or move them away from the equipment or orient them at right angles to the data cables.

I also remember something recent about the power being redone near the lab building. Check on the timeframe of when the problem started and when that work was done. Perhaps some powerline got moved too close to the data cable maybe even on another floor of the building. New construction might be ENT rather than EMT. Or they could have induced a ground loop in the construction or worse not tied something to ground that should be.

Finally, despite the name Fibre Channel, not all Fibre Channel is carried on fibre optic cables. Copper cable alternatives are available on short runs by some vendors.

I suppose if the 2 interconnected pieces of equipment were not on the same ground bus there could be some differential between them thus inducing some current flow from one to the other.

All too common.
Earth loops can be an nightmare to track down & resolve.


ID: 655499 · Report as offensive
Robert Ribbeck
Avatar

Send message
Joined: 7 Jun 02
Posts: 644
Credit: 5,283,174
RAC: 0
United States
Message 655626 - Posted: 7 Oct 2007, 6:14:51 UTC

Something is still messed up

From the log of one of my machines

10/7/2007 1:07:03 AM|SETI@home|Scheduler RPC succeeded [server version 511]
10/7/2007 1:07:03 AM|SETI@home|Message from server: No work sent
10/7/2007 1:07:03 AM|SETI@home|Message from server: (won't finish in time) Computer on 85.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that

Say What ?? the machine is on 24/7 and only runs seti@home

The closest deadline is 0ct 30 for 6 less than 5.5hr chunks everything else is
not due till Nov. Unless the scheduler is messed up and is ignoring deadlines
the oct deadlines should be completed early monday.

So WHY the won't finish in time and computer on errors ???


ID: 655626 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 11478
Credit: 167,325,260
RAC: 100,895
Australia
Message 655636 - Posted: 7 Oct 2007, 7:37:38 UTC - in response to Message 655626.  

So WHY the won't finish in time and computer on errors ???

Try the Help forums, or the Number Crunching forum.

Grant
Darwin NT
ID: 655636 · Report as offensive
Profile arr25b

Send message
Joined: 19 Nov 05
Posts: 16
Credit: 14,839,632
RAC: 0
United Kingdom
Message 656218 - Posted: 8 Oct 2007, 12:50:59 UTC - in response to Message 655636.  

08/10/2007 13:49:01||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:04|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:04|SETI@home|Sending scheduler request: To fetch work
08/10/2007 13:49:04|SETI@home|Requesting 34560 seconds of new work
08/10/2007 13:49:05||Project communication failed: attempting access to reference site
08/10/2007 13:49:06||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:09|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:09|SETI@home|Deferring communication for 1 min 0 sec
08/10/2007 13:49:09|SETI@home|Reason: scheduler request failed


having trouble getting any wu's and when I do I only receive about 6, I have my settings set to receive upto 10 days worth
ID: 656218 · Report as offensive
Idefix
Volunteer tester

Send message
Joined: 7 Sep 99
Posts: 154
Credit: 482,193
RAC: 0
Germany
Message 656252 - Posted: 8 Oct 2007, 13:43:56 UTC - in response to Message 655626.  

Hi,
Something is still messed up

From the log of one of my machines

10/7/2007 1:07:03 AM|SETI@home|Scheduler RPC succeeded [server version 511]
10/7/2007 1:07:03 AM|SETI@home|Message from server: No work sent
10/7/2007 1:07:03 AM|SETI@home|Message from server: (won't finish in time) Computer on 85.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that

Say What ?? the machine is on 24/7 and only runs seti@home

The closest deadline is 0ct 30 for 6 less than 5.5hr chunks everything else is
not due till Nov. Unless the scheduler is messed up and is ignoring deadlines
the oct deadlines should be completed early monday.

So WHY the won't finish in time and computer on errors ???

Your WUs will finish in time. But Berkeley thinks that the new WUs Berkeley wants to send to you won't be reported in time. At the moment, VHAR workunits with a deadline of about 8 days are sent out. Some of your machines have average turnaround times of 8 to 10 days, which are too long to report the WUs in time. That's the reason why Boinc blocks you from getting new work.

Regards,
Carsten
ID: 656252 · Report as offensive
Profile KWSN THE Holy Hand Grenade!
Volunteer tester
Avatar

Send message
Joined: 20 Dec 05
Posts: 3187
Credit: 56,831,319
RAC: 17,395
United States
Message 656264 - Posted: 8 Oct 2007, 14:12:39 UTC

I agree here, something is messed up...

10/8/2007 6:59:57 AM|SETI@home|Sending scheduler request: Requested by user
10/8/2007 6:59:57 AM|SETI@home|Requesting 700834 seconds of new work, and reporting 16 completed tasks
10/8/2007 7:00:13 AM||Project communication failed: attempting access to reference site
10/8/2007 7:00:16 AM||Access to reference site succeeded - project servers may be temporarily down.
10/8/2007 7:00:18 AM|SETI@home|Scheduler request failed: server returned nothing (no headers, no data)
10/8/2007 7:00:18 AM|SETI@home|Deferring communication for 1 min 0 sec
10/8/2007 7:00:18 AM|SETI@home|Reason: scheduler request failed
10/8/2007 7:01:18 AM|SETI@home|Sending scheduler request: Requested by user
10/8/2007 7:01:18 AM|SETI@home|Requesting 700832 seconds of new work, and reporting 16 completed tasks
10/8/2007 7:02:53 AM|SETI@home|Scheduler request failed: HTTP service unavailable
10/8/2007 7:02:53 AM|SETI@home|Deferring communication for 1 min 0 sec
10/8/2007 7:02:53 AM|SETI@home|Reason: scheduler request failed

at this point, I set "no new tasks"...

10/8/2007 7:03:13 AM|SETI@home|Sending scheduler request: Requested by user
10/8/2007 7:03:13 AM|SETI@home|Reporting 16 tasks
10/8/2007 7:04:33 AM|SETI@home|Scheduler request failed: HTTP service unavailable
10/8/2007 7:04:33 AM|SETI@home|Deferring communication for 1 min 0 sec
10/8/2007 7:04:33 AM|SETI@home|Reason: scheduler request failed
10/8/2007 7:05:33 AM|SETI@home|Sending scheduler request: Requested by user


This behavior is with 5.10.20 (x64)... I'm NOT getting the same with 5.8.16 or 15 (x86) (on different computers in the "farm".) I finally got through on the next try...
.

Hello, from Albany, CA!...
ID: 656264 · Report as offensive
Profile KWSN THE Holy Hand Grenade!
Volunteer tester
Avatar

Send message
Joined: 20 Dec 05
Posts: 3187
Credit: 56,831,319
RAC: 17,395
United States
Message 656267 - Posted: 8 Oct 2007, 14:18:31 UTC - in response to Message 655626.  

Something is still messed up

From the log of one of my machines

10/7/2007 1:07:03 AM|SETI@home|Scheduler RPC succeeded [server version 511]
10/7/2007 1:07:03 AM|SETI@home|Message from server: No work sent
10/7/2007 1:07:03 AM|SETI@home|Message from server: (won't finish in time) Computer on 85.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that

Say What ?? the machine is on 24/7 and only runs seti@home

The closest deadline is 0ct 30 for 6 less than 5.5hr chunks everything else is
not due till Nov. Unless the scheduler is messed up and is ignoring deadlines
the Oct deadlines should be completed early Monday.

So WHY the won't finish in time and computer on errors ???



Have you recently (within the last 2 months) shut that machine down for any reason? (maintenance, a reboot, anything?) That would cause the "Computer on" stat to fall below 100%...

.

Hello, from Albany, CA!...
ID: 656267 · Report as offensive
Profile Martin P.

Send message
Joined: 19 May 99
Posts: 294
Credit: 26,784,191
RAC: 2,641
Austria
Message 656318 - Posted: 8 Oct 2007, 16:10:04 UTC - in response to Message 656218.  

08/10/2007 13:49:01||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:04|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:04|SETI@home|Sending scheduler request: To fetch work
08/10/2007 13:49:04|SETI@home|Requesting 34560 seconds of new work
08/10/2007 13:49:05||Project communication failed: attempting access to reference site
08/10/2007 13:49:06||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:09|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:09|SETI@home|Deferring communication for 1 min 0 sec
08/10/2007 13:49:09|SETI@home|Reason: scheduler request failed


having trouble getting any wu's and when I do I only receive about 6, I have my settings set to receive upto 10 days worth


arr25b,

does the estimated time to finish a WU match with the real time? It can happen that the client_state.xml file gets corrupted. SETI@Home calculates the need for new WUs on basis of the estimated time to finish your backlog.

You can repair this by editing the client_state.xml file. Open it in any Text Editor and search for "duration_correction_factor" This will give results like this:
<duration_correction_factor>0.368199</duration_correction_factor>
Make sure it is the one for SETI!
If estimated times are longer than real crunch time then reduce the correction factor. Make sure you use the exact same number of decimal places!!!
Safe it and restart BOINC.

ID: 656318 · Report as offensive
Profile arr25b

Send message
Joined: 19 Nov 05
Posts: 16
Credit: 14,839,632
RAC: 0
United Kingdom
Message 656322 - Posted: 8 Oct 2007, 16:14:11 UTC - in response to Message 656318.  

08/10/2007 13:49:01||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:04|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:04|SETI@home|Sending scheduler request: To fetch work
08/10/2007 13:49:04|SETI@home|Requesting 34560 seconds of new work
08/10/2007 13:49:05||Project communication failed: attempting access to reference site
08/10/2007 13:49:06||Access to reference site succeeded - project servers may be temporarily down.
08/10/2007 13:49:09|SETI@home|Scheduler request failed: failed sending data to the peer
08/10/2007 13:49:09|SETI@home|Deferring communication for 1 min 0 sec
08/10/2007 13:49:09|SETI@home|Reason: scheduler request failed


having trouble getting any wu's and when I do I only receive about 6, I have my settings set to receive upto 10 days worth


arr25b,

does the estimated time to finish a WU match with the real time? It can happen that the client_state.xml file gets corrupted. SETI@Home calculates the need for new WUs on basis of the estimated time to finish your backlog.

You can repair this by editing the client_state.xml file. Open it in any Text Editor and search for "duration_correction_factor" This will give results like this:
<duration_correction_factor>0.368199</duration_correction_factor>
Make sure it is the one for SETI!
If estimated times are longer than real crunch time then reduce the correction factor. Make sure you use the exact same number of decimal places!!!
Safe it and restart BOINC.


I'll give that a try,I have also altered my days buffering from 10 to 7,still can't d/l any wu's even on a fresh install

ID: 656322 · Report as offensive
1mp0£173
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 656327 - Posted: 8 Oct 2007, 16:37:04 UTC - in response to Message 655489.  



Sorry, but you are confusing electrical signal cables with fiber optic cables. The grounding advice you gave is well applied to electrical cables, but fiber optics are immune to RFI and other electical interference, and do not require shielding which is earthed (grounded).


:) I know that fibre cables normally have no shielding, but sometimes the rodent protection of the cables is connected to the sending and the receiving modul, or to the server rack. This can cause such problems, not because of electrical interference in the cable itself, but in the sending or receiving modul.


I just wanted to mention it, cause i had such problems twice (with fibre optic) and it took me 2 months to locate the problem.

I suppose if the 2 interconnected pieces of equipment were not on the same ground bus there could be some differential between them thus inducing some current flow from one to the other. Fair enough. When you don't have an obvious solution to a problem, you must look for other obscure causes.

No. We're talking about converting electrical signals to light, running them through the fiber optics, and then converting from light back to electrical signals.

The signal is referenced to local ground at the converter at each end. That's one of the best things about fiber optics, all of the yucky "what is ground" questions go away. The light is light at each end of the cable.
ID: 656327 · Report as offensive
1mp0£173
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 656331 - Posted: 8 Oct 2007, 16:40:10 UTC - in response to Message 655492.  

I suppose if the 2 interconnected pieces of equipment were not on the same ground bus there could be some differential between them thus inducing some current flow from one to the other.

All too common.
Earth loops can be an nightmare to track down & resolve.

... and this is the other reason you use optical fiber -- it's a great way to break up ground loops (earth loops) caused by the cable ground lines.
ID: 656331 · Report as offensive
Robert Ribbeck
Avatar

Send message
Joined: 7 Jun 02
Posts: 644
Credit: 5,283,174
RAC: 0
United States
Message 656502 - Posted: 8 Oct 2007, 23:05:08 UTC - in response to Message 656267.  

Something is still messed up

From the log of one of my machines

10/7/2007 1:07:03 AM|SETI@home|Scheduler RPC succeeded [server version 511]
10/7/2007 1:07:03 AM|SETI@home|Message from server: No work sent
10/7/2007 1:07:03 AM|SETI@home|Message from server: (won't finish in time) Computer on 85.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that

Say What ?? the machine is on 24/7 and only runs seti@home

The closest deadline is 0ct 30 for 6 less than 5.5hr chunks everything else is
not due till Nov. Unless the scheduler is messed up and is ignoring deadlines
the Oct deadlines should be completed early Monday.

So WHY the won't finish in time and computer on errors ???



Have you recently (within the last 2 months) shut that machine down for any reason? (maintenance, a reboot, anything?) That would cause the "Computer on" stat to fall below 100%...



It's been on 24/27
ID: 656502 · Report as offensive
Robert Ribbeck
Avatar

Send message
Joined: 7 Jun 02
Posts: 644
Credit: 5,283,174
RAC: 0
United States
Message 656507 - Posted: 8 Oct 2007, 23:11:46 UTC - in response to Message 656252.  

Hi,
Something is still messed up

From the log of one of my machines

10/7/2007 1:07:03 AM|SETI@home|Scheduler RPC succeeded [server version 511]
10/7/2007 1:07:03 AM|SETI@home|Message from server: No work sent
10/7/2007 1:07:03 AM|SETI@home|Message from server: (won't finish in time) Computer on 85.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that

Say What ?? the machine is on 24/7 and only runs seti@home

The closest deadline is 0ct 30 for 6 less than 5.5hr chunks everything else is
not due till Nov. Unless the scheduler is messed up and is ignoring deadlines
the oct deadlines should be completed early monday.

So WHY the won't finish in time and computer on errors ???

Your WUs will finish in time. But Berkeley thinks that the new WUs Berkeley wants to send to you won't be reported in time. At the moment, VHAR workunits with a deadline of about 8 days are sent out. Some of your machines have average turnaround times of 8 to 10 days, which are too long to report the WUs in time. That's the reason why Boinc blocks you from getting new work.

Regards,
Carsten


That was from a machine that returns a result in about 8 hours The whole queue
would be returned in 8-10 days

ID: 656507 · Report as offensive
Profile The Grinch
Volunteer tester

Send message
Joined: 21 Jul 99
Posts: 6
Credit: 7,201,132
RAC: 0
Germany
Message 656634 - Posted: 9 Oct 2007, 6:55:27 UTC

The seti@home - Server actual very unstable!
What the Matter?
ID: 656634 · Report as offensive
1mp0£173
Volunteer tester

Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 656831 - Posted: 9 Oct 2007, 20:04:42 UTC - in response to Message 656634.  

The seti@home - Server actual very unstable!
What the Matter?

SETI@Home runs on old, hand-me-down hardware. That's why BOINC is designed to tolerate outages.

You can:

    *Set BOINC to cache more work
    *Connect to more than one BOINC project so you'll always have work from someone
    *Donate some cash so SETI can get better servers.



It is amazing how well things work given the size of the project and the project funding.


ID: 656831 · Report as offensive
Previous · 1 · 2

Message boards : Technical News : upload issues and other news (Oct 5, 2007)


 
©2019 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.