1) Message boards : ATLAS application : credits for runtime, not for cputime ? (Message 46053)
Posted 16 days ago by keputnam
Post:
So if I run one core on a 3.5 Ghz machine, I get the same credit as someone who runs 8 cores or 10 cores on a 3.5 GHz machine?

That is totally non-comprehensible, as I'm doing MUCH less work and returning MANY fewer results

If this is indeed correct, I can allocate more cores to other projects and get the same credit in Atlas
2) Message boards : ATLAS application : Repeated computation errors (Message 45799)
Posted 6 Dec 2021 by keputnam
Post:
Thanks, guys

The uninstall/re-install seems to have cured the problem

I'm about 10 minutes from completing a WU


Thinking back, I did upgrade VBox to 6.1.30 Apparently it didn't clean up the previously installed version very well
3) Message boards : ATLAS application : Repeated computation errors (Message 45798)
Posted 6 Dec 2021 by keputnam
Post:
Thanks for the responses

No, I have not done any tweaking of VBox

I have uninstalled VBox, used ADAware uninstall cleanup, booted reinstalled VBox and the extension pack and rebooted again

Now waiting for the job queue to clear out to where the Scheduler requests another ATLAS job
4) Message boards : ATLAS application : Repeated computation errors (Message 45789)
Posted 6 Dec 2021 by keputnam
Post:
I have used E: as my BOINC Data Drive for over 8 years Started when my system HD was a little undersized No problems at all

BOINC and VBOX executables and VBOX VMs are all on C:
5) Message boards : ATLAS application : Repeated computation errors (Message 45787)
Posted 6 Dec 2021 by keputnam
Post:
Got a new computer recently, and for a few days, things were great

Then I started getting Computation Errors on every job I run

Last time this happened the consensus was that I had lousy internet (failure to connect to the LHC servers)



I have since upgraded my connection from 25MB to 150MB
(I can post results from several speed test sites if it will help)

Running BOINC 7.16.11
VBox 6.1.26 (+ Extension Pack)



Any assistance gratefully accepted
6) Message boards : ATLAS application : Bad WUs? (Message 45176)
Posted 3 Aug 2021 by keputnam
Post:
Already aborted the second Doesn't surprise me that there is no log file, the WUs never got any CPU time

But a third, previously downloaded and queued has started and is responding normally
7) Message boards : ATLAS application : Bad WUs? (Message 45174)
Posted 3 Aug 2021 by keputnam
Post:
The last two ATLAS WUs that I have downloaded appear to be faulty

One ran for 3 days before I noticed that while I could access the VM, ALT-F2 had no effect at all I aborted that one

The latest one has now been running for about an hour and exhibits the same behavior

Also, while BOINC reports the WU as running Resource Monitor show VBox using no CPU at all

I have re-booted and upgraded to the latest VBox version with no change


TIA for any ideas or suggestions
8) Message boards : ATLAS application : Checkpointing? (Message 43393)
Posted 22 Sep 2020 by keputnam
Post:
Can anybody tell me why a program, would take regular checkpoints, and then ignore them on restart and start from scratch? For ATLAS, BOINC manager/properties shows "time since last checkpoint," which resets every two minutes

I shut down BOINC to apply some Windows service

On restart as soon as VBox manager initialized and BOINC monitoring starts, it correctly shows a certain member of events completed

Then at some later point, it resets to zero and starts at event 1 again


???
9) Message boards : ATLAS application : Confused (Message 43309)
Posted 4 Sep 2020 by keputnam
Post:
Oh, i realize the purpose, but this has only ever happened on ATLAS as far as I can remember

And this is the third go round on the circus for me
10) Message boards : ATLAS application : Confused (Message 43308)
Posted 4 Sep 2020 by keputnam
Post:
Already have an app_config with max_concurrent set to 1

We took three power hits over about 19 hours, so that would account for three restarts

I think I did one for Windows maintenance, too




As for the aborted tasks, and ridiculous number of new tasks sent

I haven't changed relative resource share in over 6 months, nor added any new projects and the scheduler SHOULD be smart enough to not send me work I will never complete on time
11) Message boards : ATLAS application : Confused (Message 43305)
Posted 4 Sep 2020 by keputnam
Post:
Can anyone explain this to me


Run Time CPU Time Credit
120,886.49 140,595.50 590.26
107,254.38 36,754.30 2,149.71



Also I have another another complaint about the Scheduler. I had five WUs cancelled by the server because I would have returned them late Fair enough

But it sent me another 15 with an 8 day return date !

There is no way in hell I'll get through them all on time

What gives?
12) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43263)
Posted 24 Aug 2020 by keputnam
Post:
Well, running copper seems to have reduced latency considerably

Your Internet speed is
29Mbps

Latency
Unloaded
23 ms

Loaded
35 ms

Upload
Speed
4.6 Mbps



Finished one WU after installing the CAT6, and the next is now an hour and a half into execution, crunching along quite nicely



Thanks for all the assistance, guys
13) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43257)
Posted 23 Aug 2020 by keputnam
Post:
So when the task "locks up" and gets no more CPU time, as verified by Windows Resource Manager, what am I looking for?


Current WU is at 13:48:24 and crunching happily along
14) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43255)
Posted 22 Aug 2020 by keputnam
Post:
Thanks for the response

I'll get some CAT6 today or tomorrow

I only run 1 LHC task at time, but have BOINC set to use 10 of my 12 "processors" (Hex core/MT)


The last two ATLAS tasks ran to completion, waiting for another at this point

Curiously, one of them kind of lugged along getting 1-2 sec of CPU time per 20 seconds of Elapsed, then at about 8:30 took off and ran to completion!
15) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43244)
Posted 21 Aug 2020 by keputnam
Post:
copper to the house, WiFi throughout Contract is 24Mb Modem/Router is a Two Wire
Speed from desktop to the router from 56 to over 120 Mbps, currently 72, which is about average My to-do list for the day includes making a few phone calls to other ISPs

The supervisor I talked to suggested trying copper from router to the desktop to see if if made any difference was going to get some the next-time I was out and about If it helps, I've then got to figure out how to permanently run it frim the Kitchen (middle of the house) to my den

C:\WINDOWS\system32>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
Reply from 8.8.8.8: bytes=32 time=31ms TTL=117
Reply from 8.8.8.8: bytes=32 time=25ms TTL=117
Reply from 8.8.8.8: bytes=32 time=24ms TTL=117







from fast.com
Your Internet speed is
16
Mbps


Latency
Unloaded
25 ms

Loaded
125 ms


Upload
Speed
4.2 Mbps
16) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43241)
Posted 20 Aug 2020 by keputnam
Post:
Well got the replacement modem, got it installed and worked with a Supervisor to get it back to a measures speed of the old one. When it was first installed, it was about half! (the first guy was an absolute idiot who didn't listen to a thing I told him - Yeah, Indian sub-continent))

First WU completed

The next two I had to abort
of note, BOTH of those two were aborted by other users, as well

I'm currently at max bandwidth, for my ISP this area (small neighborhood separated from the rest of the city by a river) so may have to shop for another carrier

(Yeah I was told "we are upgrading our service throughout the country and surveys are underway even now HaHaHa)


Guess I need to shop around and see if anyone else has better bandwidth, here



Looks like for the meantime, I either don't run Atlas, or do and accept a success rate around 1 in 5 or 1 in 8 though that's not really fair to the project or other crunchers



<sigh>
17) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43227)
Posted 17 Aug 2020 by keputnam
Post:
Double checked Yeti's check list - all good

Called my ISP and asked if there was anything they could do to reduce latency

They couldn't access the modem control panel from their end, and I couldn't access it from within my home network

They also said it was over 7 years old and offered to send me a new one, which should be here WED afternoon sometime

Let me get it hooked up and set "accept new tasks" here and lets see what happens



Thanks for all the responses so far

Really appreciated
18) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43225)
Posted 17 Aug 2020 by keputnam
Post:
Thanks, Guys


Guest Edition?

Not familiar with that term

Already at VBox 6.0.14 with Extension Pack 6.0.14


I'll review Yeti's checklist one more time
19) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43199)
Posted 8 Aug 2020 by keputnam
Post:
Sorry for the delayed response I was out of town most of the week



I'm not seeing what you describe, but here are the few lines of the VBox.log


00:00:10.586190 IEM: rdmsr(0x4e) -> #GP(0)
00:00:10.720435 APIC0: Switched mode to x2APIC
00:00:10.828486 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:10.863375 APIC1: Switched mode to x2APIC
00:00:10.863391 GIM: KVM: VCPU 1: Enabled system-time struct. at 0x000000014bf84040 - u32TscScale=0x9b26c76a i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x4d5156a93 uVirtNanoTS=0x176e06bcd
00:00:10.864397 IEM: rdmsr(0x4e) -> #GP(0)
00:00:12.276698 IEM: wrmsr(0xc90,0x0`000fffff) -> #GP(0)
00:00:13.344427 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:13.344508 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:13.344924 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa1 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:13.344994 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:15.339531 NAT: Link up
00:00:17.175622 VMMDev: Guest Additions information report: Version 5.2.32 r132073 '5.2.32'
00:00:17.175672 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)
00:00:17.175813 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:17.176096 VMMDev: Guest reported fixed hypervisor window at 00001800000 LB 0x2400000 (rc=VINF_SUCCESS)
00:00:17.176121 VMMDev: vmmDevReqHandler_HeartbeatConfigure: No change (fHeartbeatActive=false)
00:00:17.176141 VMMDev: Heartbeat flatline timer set to trigger after 4 000 000 000 ns
00:00:17.176199 VMMDev: Guest Log: vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
00:00:17.176806 VMMDev: Guest Log: vboxguest: misc device minor 58, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
00:00:17.576133 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000ac60000 w=800 h=600 bpp=32 cbLine=0xC80 flags=0x1 origin=0,0
00:00:21.852605 NAT: IPv6 not supported
00:00:22.141405 NAT: DHCP offered IP address 10.0.2.15
00:00:22.141752 NAT: DHCP offered IP address 10.0.2.15
00:00:24.308484 VMMDev: Guest Log: Checking CVMFS...
00:00:35.698186 VMMDev: Guest Log: VBoxService 5.2.32 r132073 (verbosity: 0) linux.amd64 (Jul 12 2019 10:32:28) release log
00:00:35.698208 VMMDev: Guest Log: 00:00:00.000211 main Log opened 2020-08-08T12:40:50.916026000Z
00:00:35.698272 VMMDev: Guest Log: 00:00:00.000313 main OS Product: Linux
00:00:35.698310 VMMDev: Guest Log: 00:00:00.000354 main OS Release: 3.10.0-957.27.2.el7.x86_64
00:00:35.698344 VMMDev: Guest Log: 00:00:00.000389 main OS Version: #1 SMP Mon Jul 29 17:46:05 UTC 2019
00:00:35.698383 VMMDev: Guest Log: 00:00:00.000424 main Executable: /opt/VBoxGuestAdditions-5.2.32/sbin/VBoxService
00:00:35.698391 VMMDev: Guest Log: 00:00:00.000426 main Process ID: 1490
00:00:35.698396 VMMDev: Guest Log: 00:00:00.000427 main Package type: LINUX_64BITS_GENERIC
00:00:35.703679 VMMDev: Guest Log: 00:00:00.005729 main 5.2.32 r132073 started. Verbose level = 0
00:00:35.704600 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x1, 0x8000000000000000
00:00:45.706543 VMMDev: Guest Log: 00:00:10.008554 timesync vgsvcTimeSyncWorker: Radical guest time change: 25 211 221 087 000ns (GuestNow=1 596 915 662 144 209 000 ns GuestLast=1 596 890 450 923 122 000 ns fSetTimeLastLoop=true )
00:10:11.861076 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000ac60000 w=800 h=600 bpp=0 cbLine=0xC80 flags=0x5 origin=0,0
20) Message boards : ATLAS application : Processor Time Locks Up Elapsed Time Continues to Climb (Message 43179)
Posted 3 Aug 2020 by keputnam
Post:
??

Is that file structure on LINUX, because it doesn't exist on my Win10 machine


I have a Boinc Data Folder

Under that I have Projects and Slots directories among others

Current Theory job is running at CPU 00:00:52 Elapsed 00:34:07 in slot 8

Neither the “cernvm\shared” folder or the runRivet.log file exists anywhere in the DATA directory


Next 20


©2022 CERN