1) Questions and Answers : Unix/Linux : Boinc waits 1 hour before starting the next WU (Message 7572)
Posted 10 May 2005 by Hermes
Post:
> Are your preferences the same for all projects?

The preferences were distributed by the client to all attached projects.

> Sounds to me like maybe Boincmanager is getting a 1 hour 'time to swtich
> between projects' from one place, and maybe boinc is getting a different time
> to switch between projects from another place.
>
> I tried boincmanager, but didn't like it, and downgraded to the boinc command
> line client.

I am starting the command line client manually and control ist with BoincView from a Windows Computer in my local Network.
2) Questions and Answers : Unix/Linux : Boinc not suspending projects properly and mixing them up (Message 7473)
Posted 6 May 2005 by Hermes
Post:
Boinc v4.32 running under Knoppix 3.4
Attached to Einstein (suspended), LHC and Predictor.
2005-05-06 14:22:02 [---] May run out of work in 0.01 days; requesting more
2005-05-06 14:22:02 [LHC@home] Requesting 16.86 seconds of work
2005-05-06 14:22:02 [LHC@home] Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
2005-05-06 14:22:33 [LHC@home] Computation for result v64diponlyinjnoskew-58s14_16519.0385_1_sixvf_41990_1 finished
2005-05-06 14:22:33 [ProteinPredictorAtHome] Starting result h0006A_1_13335_1 using mfoldB125 version 4.27
2005-05-06 14:22:34 [LHC@home] Started upload of v64diponlyinjnoskew-58s14_16519.0385_1_sixvf_41990_1_0
2005-05-06 14:22:38 [LHC@home] Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
2005-05-06 14:22:39 [LHC@home] Started download of v64diponlyinjnoskew-58s16_18565.7693_1_sixvf_42068.zip
2005-05-06 14:22:40 [LHC@home] Finished upload of v64diponlyinjnoskew-58s14_16519.0385_1_sixvf_41990_1_0
2005-05-06 14:22:40 [LHC@home] Throughput 46843 bytes/sec
2005-05-06 14:22:43 [LHC@home] Finished download of v64diponlyinjnoskew-58s16_18565.7693_1_sixvf_42068.zip
2005-05-06 14:22:43 [LHC@home] Throughput 90236 bytes/sec
2005-05-06 14:22:43 [ProteinPredictorAtHome] Pausing result h0006A_1_13335_1 (left in memory)
2005-05-06 14:22:43 [LHC@home] Starting result v64diponlyinjnoskew-58s16_18565.7693_1_sixvf_42068_3 using sixtrack version 4.66
2005-05-06 15:22:43 [ProteinPredictorAtHome] Resuming result h0006A_1_13335_1 using mfoldB125 version 4.27

At this point both the mfold (Predictor) and the sixtrack (LHC) Program are running and increasing their CPU-time. But in the worktab only the CPU-time of the Predictor WU increases, the LHC WU stays at zero CPU-time.

After the next switch:
2005-05-06 15:22:43 [ProteinPredictorAtHome] Resuming result h0006A_1_13335_1 using mfoldB125 version 4.27
2005-05-06 15:22:43 [LHC@home] Pausing result v64diponlyinjnoskew-58s16_18565.7693_1_sixvf_42068_3 (left in memory)

The mfold program is now suspended, and sixtrack continues running. The CPU-time and percentage complete of the mfold-WU continue to rise, the sixtrack-WU stays at 0 for both values.
3) Questions and Answers : Unix/Linux : Boinc waits 1 hour before starting the next WU (Message 7472)
Posted 6 May 2005 by Hermes
Post:
This happened 3 times the last few hours. From 6:20 to 7:20, from 8:26 to 9:26 and from 10:51 to 11:51.

2005-05-06 05:56:14 [ProteinPredictorAtHome] Restarting result h0006A_1_4278_2 using mfoldB125 version 4.27
2005-05-06 05:56:14 [LHC@home] Pausing result v64D1D2MQonlyinjnoskew1b5offcomp-49s8_10583.077_1_sixvf_35077_2 (removed from memory)
2005-05-06 06:20:42 [ProteinPredictorAtHome] Computation for result h0006A_1_4278_2 finished
2005-05-06 06:20:44 [ProteinPredictorAtHome] Started upload of h0006A_1_4278_2_0
2005-05-06 06:20:44 [ProteinPredictorAtHome] Started upload of h0006A_1_4278_2_1
2005-05-06 06:20:46 [ProteinPredictorAtHome] Finished upload of h0006A_1_4278_2_0
2005-05-06 06:20:46 [ProteinPredictorAtHome] Throughput 4740 bytes/sec
2005-05-06 06:20:46 [ProteinPredictorAtHome] Started upload of h0006A_1_4278_2_2
2005-05-06 06:20:48 [ProteinPredictorAtHome] Finished upload of h0006A_1_4278_2_1
2005-05-06 06:20:48 [ProteinPredictorAtHome] Throughput 24301 bytes/sec
2005-05-06 06:20:49 [ProteinPredictorAtHome] Finished upload of h0006A_1_4278_2_2
2005-05-06 06:20:49 [ProteinPredictorAtHome] Throughput 32489 bytes/sec
2005-05-06 07:20:41 [ProteinPredictorAtHome] Starting result h0006A_1_5173_2 using mfoldB125 version 4.27
2005-05-06 07:20:44 [---] May run out of work in 0.01 days; requesting more
2005-05-06 07:20:44 [ProteinPredictorAtHome] Requesting 459.41 seconds of work
2005-05-06 07:20:44 [ProteinPredictorAtHome] Sending request to scheduler: http://predictor.scripps.edu/predictor_cgi/cgi
2005-05-06 07:20:46 [ProteinPredictorAtHome] Scheduler RPC to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
2005-05-06 07:20:48 [ProteinPredictorAtHome] Started download of h0006A_1_6608.ini
2005-05-06 07:20:48 [ProteinPredictorAtHome] Started download of h0006A_1_6608.inp
2005-05-06 07:20:49 [ProteinPredictorAtHome] Finished download of h0006A_1_6608.ini
2005-05-06 07:20:49 [ProteinPredictorAtHome] Throughput 2134 bytes/sec
2005-05-06 07:20:49 [ProteinPredictorAtHome] Finished download of h0006A_1_6608.inp
2005-05-06 07:20:49 [ProteinPredictorAtHome] Throughput 323 bytes/sec
2005-05-06 07:20:49 [ProteinPredictorAtHome] Started download of h0006A_1_6608.seq
2005-05-06 07:20:49 [ProteinPredictorAtHome] Started download of h0006A_1_6608.res
2005-05-06 07:20:50 [ProteinPredictorAtHome] Finished download of h0006A_1_6608.seq
2005-05-06 07:20:50 [ProteinPredictorAtHome] Throughput 2577 bytes/sec
2005-05-06 07:20:50 [ProteinPredictorAtHome] Finished download of h0006A_1_6608.res
2005-05-06 07:20:50 [ProteinPredictorAtHome] Throughput 6 bytes/sec
2005-05-06 08:20:50 [LHC@home] Restarting result v64D1D2MQonlyinjnoskew1b5offcomp-49s8_10583.077_1_sixvf_35077_2 using sixtrack version 4.66
2005-05-06 08:20:50 [ProteinPredictorAtHome] Pausing result h0006A_1_5173_2 (removed from memory)
2005-05-06 08:25:26 [---] May run out of work in 0.01 days; requesting more
2005-05-06 08:25:26 [LHC@home] Requesting 8.61 seconds of work
2005-05-06 08:25:26 [LHC@home] Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
2005-05-06 08:25:27 [LHC@home] Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
2005-05-06 08:25:29 [LHC@home] Started download of v64diponlyinjnoskew-57s8_10564.0385_1_sixvf_41506.zip
2005-05-06 08:25:33 [LHC@home] Finished download of v64diponlyinjnoskew-57s8_10564.0385_1_sixvf_41506.zip
2005-05-06 08:25:33 [LHC@home] Throughput 91077 bytes/sec
2005-05-06 08:26:51 [LHC@home] Computation for result v64D1D2MQonlyinjnoskew1b5offcomp-49s8_10583.077_1_sixvf_35077_2 finished
2005-05-06 08:26:52 [LHC@home] Started upload of v64D1D2MQonlyinjnoskew1b5offcomp-49s8_10583.077_1_sixvf_35077_2_0
2005-05-06 08:26:58 [LHC@home] Finished upload of v64D1D2MQonlyinjnoskew1b5offcomp-49s8_10583.077_1_sixvf_35077_2_0
2005-05-06 08:26:58 [LHC@home] Throughput 47775 bytes/sec
2005-05-06 09:26:51 [LHC@home] Starting result v64diponlyinjnoskew-57s8_10564.0385_1_sixvf_41506_0 using sixtrack version 4.66
2005-05-06 10:26:51 [ProteinPredictorAtHome] Restarting result h0006A_1_5173_2 using mfoldB125 version 4.27
2005-05-06 10:26:51 [LHC@home] Pausing result v64diponlyinjnoskew-57s8_10564.0385_1_sixvf_41506_0 (removed from memory)
2005-05-06 10:51:53 [ProteinPredictorAtHome] Computation for result h0006A_1_5173_2 finished
2005-05-06 10:51:54 [ProteinPredictorAtHome] Started upload of h0006A_1_5173_2_0
2005-05-06 10:51:54 [ProteinPredictorAtHome] Started upload of h0006A_1_5173_2_1
2005-05-06 10:51:56 [ProteinPredictorAtHome] Finished upload of h0006A_1_5173_2_0
2005-05-06 10:51:56 [ProteinPredictorAtHome] Throughput 4850 bytes/sec
2005-05-06 10:51:56 [ProteinPredictorAtHome] Started upload of h0006A_1_5173_2_2
2005-05-06 10:51:58 [ProteinPredictorAtHome] Finished upload of h0006A_1_5173_2_1
2005-05-06 10:51:58 [ProteinPredictorAtHome] Throughput 24699 bytes/sec
2005-05-06 10:51:59 [ProteinPredictorAtHome] Finished upload of h0006A_1_5173_2_2
2005-05-06 10:51:59 [ProteinPredictorAtHome] Throughput 27972 bytes/sec
2005-05-06 11:51:52 [ProteinPredictorAtHome] Starting result h0006A_1_6608_4 using mfoldB125 version 4.27

Boinc v4.32 running under Knoppix 3.4
Attached to Einstein (suspended), LHC and Predictor.
4) Questions and Answers : Unix/Linux : LHC and Predictor don't get along (Message 6957)
Posted 11 Apr 2005 by Hermes
Post:
> Try to reset the lhc@home project.
> Make sure you get version 4.66 of sixtrack.

I got sixtrack 4.66 now, but it also got mixed up with mfold. It went even so far as to Boinc claiming to have P@H running and counting up the CPU-time, but in the process list the running process was sixtrack. and now my mfold WUs end with "process got signal 6".
5) Questions and Answers : Unix/Linux : LHC and Predictor don't get along (Message 6887)
Posted 8 Apr 2005 by Hermes
Post:
I have encountered an unknown number of problems this night. On my first Linux computers was a Predictor@home workunit running, when Boinc started sixtrack. Even though Boinc claimed to pause P@H the mfold-client continued to run. The CPU-Time of the Predictor WU was reset to zero, the progress continued at the same percentage.
My second Linux machine had a paused Predictor WU with about an hour CPU-Time, when Boinc paused Einstein to start a LHC WU. Again the CPU-Time of the Predictor WU was reset to zero. And now the CPU-time used by the sixtrack-program ist added to the Predictor WU.

Software Versions:
Boinc: 4.27
Sixtrack: 4.63
mfoldB125: 4.27

1. Computer: Knoppix 3.4, Kernel 2.4.26
2. Computer: Fedora Core 3, Kernel: 2.6.10-1.770_FC3



©2024 CERN