Posts by Questor

11) Message boards : Number crunching : OpenCL MB v8.12 issues thread attempt 2 (Message 1790089)
Posted 24 May 2016 by Profile Questor Special Project $75 donor
Post:
Thanks for report. AP binary needs rebuild to include that option.

P.S. Also, could you run tool like ProcessExplorer and list named MutExes that created both for AP and MB processes in your case?


Hope this is what you're after :-
SOG1, SOG2 and AP

For SOG1
Mutant \BaseNamedObjects\SETI_GPU_App_Slot8_Mutex
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(005692)
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(005692)
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot0_Mutex
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot1_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot1_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot0_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot2_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot3_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot4_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot5_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot6_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot7_Mutex
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot2_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot9_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot10_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot11_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot12_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot13_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot14_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot15_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot16_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot17_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot18_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot19_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot20_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot21_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot22_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot23_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot24_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot25_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot26_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot27_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot28_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot29_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot30_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot31_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot32_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot33_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot34_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot35_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot36_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot37_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot38_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot39_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot40_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot41_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot42_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot43_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot44_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot45_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot46_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot47_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot48_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot49_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot50_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot51_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot52_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot53_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot54_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot55_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot56_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot57_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot58_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot59_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot60_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot61_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot62_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot63_Mutex



For SOG2
Mutant \BaseNamedObjects\SETI_GPU_App_Slot0_Mutex
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(003624)
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(003624)
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot0_Mutex
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot1_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot8_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot1_Mutex
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot2_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot2_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot3_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot4_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot5_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot6_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot7_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot9_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot10_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot11_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot12_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot13_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot14_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot15_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot16_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot17_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot18_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot19_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot20_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot21_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot22_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot23_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot24_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot25_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot26_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot27_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot28_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot29_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot30_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot31_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot32_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot33_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot34_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot35_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot36_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot37_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot38_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot39_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot40_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot41_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot42_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot43_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot44_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot45_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot46_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot47_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot48_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot49_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot50_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot51_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot52_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot53_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot54_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot55_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot56_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot57_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot58_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot59_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot60_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot61_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot62_Mutex
Mutant \BaseNamedObjects\SETI_GPU_App_Slot63_Mutex


For AP
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot0_Mutex
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(011408)
Mutant \Sessions\3\BaseNamedObjects\LoggerMutex(011408)
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot2_Mutex
Mutant \BaseNamedObjects\SETI_NV_GPU_App_Slot1_Mutex
12) Message boards : Number crunching : OpenCL MB v8.12 issues thread attempt 2 (Message 1790039)
Posted 24 May 2016 by Profile Questor Special Project $75 donor
Post:

However, AP and MB apps are setting affinity independantly of each other.

MB tasks were on CPU0 and CPU1
and AP task was on CPU0 instead of CPU2

I hadn't previously had the commandline parameters set so do not know if this is correct behaviour or not?


If after adding -total_GPU_instances_num 3 AP and MB will still share same CPU (both having -cpu_lock and -instances_per_device 3 ) please report again.


I have that set in both AP and MB command line files now (although I could not see that AP README referred to it)

It is still :

MB tasks are on CPU0 and CPU1
and AP task is on CPU0 instead of CPU2


Edit : also tried with just in MB file and without -hp : no difference.

I only have one GPU running three tasks.
http://setiathome.berkeley.edu/show_host_detail.php?hostid=7973566
13) Message boards : Number crunching : OpenCL MB v8.12 issues thread attempt 2 (Message 1789991)
Posted 24 May 2016 by Profile Questor Special Project $75 donor
Post:
I have been setting -instances_per_device 3 -cpu_lock -hp in the MB command line.

When I received some AP tasks yesterday I noticed one running task was stalled with zero CPU activity. (Pausing all other GPU tasks allowed the AP to start processing again)

The AP command line also has -instances_per_device 3 -cpu_lock -hp

The AP readme file says [quote]-instances_per_device N :Sets allowed number of simultaneously executed GPU app instances per GPU device (shared with MultiBeam app instances).

However, AP and MB apps are setting affinity independantly of each other.

MB tasks were on CPU0 and CPU1
and AP task was on CPU0 instead of CPU2

I hadn't previously had the commandline parameters set so do not know if this is correct behaviour or not?
14) Message boards : Number crunching : Waiting for shared memory, Linux 64-bit, (Message 1463878)
Posted 13 Jan 2014 by Profile Questor Special Project $75 donor
Post:
I don't know how it shows in Linux as I only run Windows at present but if you set the BOINC preference for memory usage too low you will get tasks waiting for memory to become free. Might you have accidentally changed that setting(or perhaps all your memory is not being recognised)?


John.
15) Message boards : Number crunching : Need cc_config.xml help! (Message 1161109)
Posted 11 Oct 2011 by Profile Questor Special Project $75 donor
Post:
You have a couple of missing lines in your file.

The structure is :-

<cc_config>
<log_flags>
[ ... ]
</log_flags>
<options>
[ ... ]
</options>
</cc_config>

So you should have :-

<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>


John.
16) Message boards : Number crunching : Asking for efficiency advice (Message 1144764)
Posted 25 Aug 2011 by Profile Questor Special Project $75 donor
Post:
I realize that there is a creditnew effect working its way through RAC figures these days, but my rigs are off about 40% from where they were about six months ago. While I have reduced WU per gpu down to one on several cards/machines,(because of heat) I can't imagine that it would make that much difference. I've even upgraded two machines recently. All machines have been running fairly steady (when WU availability allows) for several months. I run a stable 266.58, a stable Lunatics x0.37, and a stable BOINC 6.12.33, 24/7 on all machines. I was having a lot of invalids and errors months ago with newer drivers. I since rolled back, and that seems to have calmed down. As I look at my results, they seem to be OK time wise. I'm just concerned that I don't get near the RAC that I used to with better hardware. What am I missing? Where can I look to find any bottlenecks? Thanks for any advice.

Russ


280.26 has made a big difference to one of my machines and seems stable. The GTX570s were downclocking so that I was seeing GPU usage in the 80% range instead of 99% now - only seen on Vista64. XP 32 and 64 machines always show 99% with both drivers. (all cases with lunatics 38g)

That was starting to make a difference to RAC but at the moment it seems to be generally on the rise on all my machines for some other resaon.


John.
17) Message boards : Number crunching : I Was Getting Strange Errors (Message 1109455)
Posted 25 May 2011 by Profile Questor Special Project $75 donor
Post:
I have a similar machine http://setiathome.berkeley.edu/show_host_detail.php?hostid=5798463

Phenom X6 1100T running SETI@HOME on 6 cores without errors. This has only 4GB RAM running Vista 64. I am running 6.10.58 not 6.12.26.


John.
18) Message boards : Number crunching : nVIDIA driver 266.58 (Message 1103742)
Posted 6 May 2011 by Profile Questor Special Project $75 donor
Post:
Hi Sutaru

I have the tray icon and am using XP with 266.58 drivers.

If you do not have it, run the Nvidia Control Panel and go to the Desktop menu. Under there is an option to tick for 'Show notification tray icon'.

Hope that gives you what you are looking for.

Regards,


John.
19) Message boards : Number crunching : computer crashes when usb device plugged in (Message 1047024)
Posted 8 Nov 2010 by Profile Questor Special Project $75 donor
Post:
When you insert the USB device and the machine does not reboot - does the USB device actually work?

What I'm wondering is ususally the front panel sockets go to a header which plugs into the motherboard. If the header plug is misaligned on the motherboard connector it may be shorting something out / causing a reset when you insert your device.

The header sockets arent usually keyed in any way and it is possible to insert incorrectly when they are in an awkward position - I've done it myself.

Another thought - check for any small conducting foreign objects that might have found their way into the USB socket which may cause intermittent shorts when a device is inserted.


John.

20) Message boards : Number crunching : Corrupt database? (Message 1044021)
Posted 23 Oct 2010 by Profile Questor Special Project $75 donor
Post:
My computer with ID 5455034 shouldn’t be at Rank 21, as I have RAC 47,504.20 .
It should be at Rank 16.
I think something is going on with the database.


I have noticed this before. I think those pages are based on some sort of static data which gets refreshed periodically (you can only view the first 10000 hosts). If the process doesnt get as far as updating everything some pages show old data. Page 1 had values less than yours a while back but it has now changed and you actually appear in pos 20 and 21 at the moment!.


John.
21) Message boards : Number crunching : Still Getting New Ghosts (Message 1040909)
Posted 11 Oct 2010 by Profile Questor Special Project $75 donor
Post:
Apparently it doesnt work on XP. http://support.microsoft.com/kb/262265

The work around is to change the IP address to a non working one for your router and then back to dhcp (or a working static address).

Disable
=======

netsh interface ip set address <interface name> static <ip address> <mask> <default gateway> <gateway interface metric>

e.g.
netsh interface ip set address "Local Area Connection" static 1.1.1.1 255.0.0.0 1.0.0.1 1

Enable
======

netsh interface ip set address "Local Area Connection" dhcp

Tried on XP and works OK.


John.
22) Message boards : Number crunching : Oh no - my PC has gone! (Message 1039563)
Posted 8 Oct 2010 by Profile Questor Special Project $75 donor
Post:
Seems a shame to lose the 250. Could you just put that in one of your home machines?

I'm sure you'd sneak that past the missus .....


John.
23) Message boards : Number crunching : Panic Mode On (39) Server problems (Message 1038679)
Posted 3 Oct 2010 by Profile Questor Special Project $75 donor
Post:
Hmm..............

Last contacted SETI on 10 Sep 2010 22:17:04 UTC.

I would perform a project reset. More important to get the machine back online with SETI since the completed work is probably lost anyway.

Be advised that you will probably lose the optimized apps installation also so be prepared to reinstall the optimized apps again.

This is what I would do but it's your machine...............


That machine is a ghost machine created when a machine accidentally booted from the wrong disk which had an earlier copy of a SETI install on it. I can't merge the two machines. ID: 4650366 and ID: 5488329.

The machine which wouldnt report finally has with 211 tasks (ID: 5516356 ).


John
24) Message boards : Number crunching : Panic Mode On (39) Server problems (Message 1038558)
Posted 3 Oct 2010 by Profile Questor Special Project $75 donor
Post:
Is anyone else having problem reporting?

Most of my machines are reporting one or two tasks at a time OK.

However I have one which hasnt reported for a time and now has over 100 tasks to report.

When it reports I get

03/10/2010 04:14:38 SETI@home update requested by user
03/10/2010 04:14:41 SETI@home Sending scheduler request: Requested by user.
03/10/2010 04:14:41 SETI@home Reporting 109 completed tasks, requesting new tasks for CPU and GPU
03/10/2010 04:16:13 SETI@home Scheduler request failed: HTTP internal server error


Have rebooted machine.
25) Message boards : Number crunching : Help! I've lost all my settings! (Message 1038550)
Posted 3 Oct 2010 by Profile Questor Special Project $75 donor
Post:
Hi Tim,

No, it's the same size as the normal client_state file. The other one there is client_state_old, but it is exactly that - 6 months old.

Looks like I'm gonna have to get a new machine id, and try to get some more work.

The machine hasn't changed, so I should be able to merge it with the old one, but I will lose about 800 tasks.

Damn! This was just starting to rip through a good few wu's too. Now it's sitting on 800 tasks it can't work on, and I can't seem to get any new ones either.

regards, Giz.


So annoying when that happens. Assuming your 6 month old file has the same host cpid value as you were currently using you could use this to start Boinc and detach/reattach which will release those orphaned 800 tasks.


John.
26) Message boards : Number crunching : BOINC not downloading GPU WUs (Message 1033501)
Posted 17 Sep 2010 by Profile Questor Special Project $75 donor
Post:
There was a server side change made a while ago which means that VLAR tasks that dont run as well on a GPU are only allocated to CPU. You may be experiencing that. Otherwise the MB tasks run on CPU or GPU.

Do your CPU tasks have a name something like xxxxxxxxxxx.vlar_y - those a VLARs which wont get assigned to your GPU.

With a lot of users currently requesting new work you may just have been unlucky and got 0 allocated on that request.

If you have surplus of CPU tasks you could look at Freds Reschedule app which allows you to move tasks from CPU<_> GPU.

Note: The other scheduler app on Lunatics does not work well with Fermi cards.


John.
27) Message boards : Number crunching : Computation Errors (Message 1032911)
Posted 11 Sep 2010 by Profile Questor Special Project $75 donor
Post:
Hi all, one of my hosts seems to be getting a lot of errors in the last few hours since the servers came back online Host ID: 879910 I have another three WU's that are yet to report and I noticed the run time is identical when they exit at 01:51:44 I am running AK's optimised app and they are non Cuda WU's, anyone having similar problems?
One of them link below

EXIT STATUS -177 (0xffffffffffffff4f)

http://setiathome.berkeley.edu/result.php?resultid=1698440392


There are a few threads with explanations as to the cause of these errors but as a quick fix you can download the new Reschedule tool by Fred which has an option to fix the problem. (The -177 happens when a task exits because it has reached a maximum timeout value)

New Reschedule tool

John.
28) Message boards : Number crunching : Panic Mode On (38) Server problems (Message 1032589)
Posted 10 Sep 2010 by Profile Questor Special Project $75 donor
Post:
Oops
11/09/2010 03:23:07 SETI@home Temporarily failed upload of 02ap10ag.32558.13336.14.10.117_0_0: transient upload error
11/09/2010 03:23:07 SETI@home [error] Error reported by file upload server: Server is out of disk space


Getting this on all machines, and the cricket graphs are dying.

T.A.


Getting it on all my machines as well. At first fails to upload because of space but then succeeds.

It is hard to believe the SETI folks wouldnt have spotted the disks were full (unless nothing could be done about it) - I wonder if it is a deliberate mechanism to control the upload storm by limiting the amount of disk space available? However, I did wonder if the increasing pendings and ghosts were eventually going to cause a problem.


John.
29) Message boards : Number crunching : And we're live. Outage over, upload server online (Message 1032581)
Posted 10 Sep 2010 by Profile Questor Special Project $75 donor
Post:
Keeping NNT on on main machine. Letting my most urgent machine upload & possibly download first as it's likely to go dry first.

Remember all: a fresh attempt to get those _2+s priority by selecting all _0s + _1s + suspending them for a sec or 2 to kick into action the higher-quorums. Let's get that pending down.



Do we have a problem?

10/09/2010 18:52:31 | SETI@home | [error] Error reported by file upload server: can't write file /home/boincadm/projects/sah/upload/250/29mr10ae.3263.11704.16.10.120.vlar_0_0: No space left on server
10/09/2010 18:52:31 | SETI@home | [error] Error reported by file upload server: Server is out of disk space
10/09/2010 18:52:31 | SETI@home | Temporarily failed upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0: transient upload error
10/09/2010 18:52:31 | SETI@home | Backing off 11 min 50 sec on upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0
10/09/2010 18:52:31 | SETI@home | Temporarily failed upload of 05my10ac.19824.23962.13.10.24_1_0: transient upload error
10/09/2010 18:52:31 | SETI@home | Backing off 19 min 30 sec on upload of 05my10ac.19824.23962.13.10.24_1_0
10/09/2010 18:52:31 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.17_1_0
10/09/2010 18:52:31 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:52:41 | SETI@home | Finished upload of 05my10ac.19824.23962.13.10.17_1_0
10/09/2010 18:52:43 | SETI@home | [error] Error reported by file upload server: can't write file /home/boincadm/projects/sah/upload/260/05my10ac.19824.23962.13.10.14_0_0: No space left on server
10/09/2010 18:52:43 | SETI@home | Temporarily failed upload of 05my10ac.19824.23962.13.10.14_0_0: transient upload error
10/09/2010 18:52:43 | SETI@home | Backing off 16 min 56 sec on upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:52:54 | SETI@home | Started upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0
10/09/2010 18:52:54 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.24_1_0
10/09/2010 18:52:55 | SETI@home | [error] Error reported by file upload server: Server is out of disk space
10/09/2010 18:52:55 | SETI@home | [error] Error reported by file upload server: Server is out of disk space
10/09/2010 18:52:55 | SETI@home | Temporarily failed upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0: transient upload error
10/09/2010 18:52:55 | SETI@home | Backing off 28 min 21 sec on upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0
10/09/2010 18:52:55 | SETI@home | Temporarily failed upload of 05my10ac.19824.23962.13.10.24_1_0: transient upload error
10/09/2010 18:52:55 | SETI@home | Backing off 32 min 21 sec on upload of 05my10ac.19824.23962.13.10.24_1_0
10/09/2010 18:52:55 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:52:57 | SETI@home | [error] Error reported by file upload server: Server is out of disk space
10/09/2010 18:52:57 | SETI@home | Temporarily failed upload of 05my10ac.19824.23962.13.10.14_0_0: transient upload error
10/09/2010 18:52:57 | SETI@home | Backing off 29 min 3 sec on upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:52:58 | SETI@home | Started upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0
10/09/2010 18:52:58 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.24_1_0
10/09/2010 18:53:08 | SETI@home | Finished upload of 29mr10ae.3263.11704.16.10.120.vlar_0_0
10/09/2010 18:53:08 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:53:10 | SETI@home | Finished upload of 05my10ac.19824.23962.13.10.24_1_0
10/09/2010 18:53:16 | SETI@home | [error] Error reported by file upload server: can't write file /home/boincadm/projects/sah/upload/260/05my10ac.19824.23962.13.10.14_0_0: No space left on server
10/09/2010 18:53:16 | SETI@home | Temporarily failed upload of 05my10ac.19824.23962.13.10.14_0_0: transient upload error
10/09/2010 18:53:16 | SETI@home | Backing off 56 min 8 sec on upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:53:19 | SETI@home | Started upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:53:27 | SETI@home | Finished upload of 05my10ac.19824.23962.13.10.14_0_0
10/09/2010 18:53:30 | SETI@home | update requested by user
10/09/2010 18:53:31 | SETI@home | Sending scheduler request: Requested by user.
10/09/2010 18:53:31 | SETI@home | Reporting 100 completed tasks, not requesting new tasks
10/09/2010 18:54:31 | SETI@home | Scheduler request completed

Odd that it says no space and then manages to upload. I'm disabling network for a while.


John
30) Message boards : Number crunching : michael has a question (Message 1032057)
Posted 9 Sep 2010 by Profile Questor Special Project $75 donor
Post:
that would involve w*rk on my part!!!

Sorry, says I dont have enough credits to write in the forum.

Does the IP address of your computer affect Boinc from connecting? I travel for work, so the ip address is never the same, and online it says my ip is the same as when I am at home, not the new one on the road. My laptop continually says Retrieving Current Status. My Server continually says Processing Suspended: User Active.

The website wont even update the computer info on any of my computers running Boinc.

Thanks for a reply (if you want to).
Peranha


Sounds like two problems on 2 machines? The server has "Do work when computer is in use" set to No (unticked) and on the laptop boincmgr cannot connect to boinc.exe perhaps because of firewall blocking app connection via port 31416?
I have two routers at home (work and home) which give PCs different IP addresses and I connect via both at different times without problems.

John.


Previous 20 · Next 20


 
©2018 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.