Message boards :
Number crunching :
LHC@Home Theory Native ???
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
Installed full version of Linux Ubuntu v18.04.2 LTS so I can run some of the Linux only Applications.Having a problem running the LHC Theory Native Wu's so far. They error out in just a few seconds running time. Are they a VBox Wu, they show MT so I'm assuming their a CPU Wu ??? Checked and as far as I know VirtualBox is installed. Don't know about the Lib files though if that is causing the error. I can't find the proper commands to install the lib files if that's what missing for the Wu's to run properly. If anybody knows the proper commands or a link that shows them for installing the Lib Files could you post them ... Thanks |
Send message Joined: 2 Oct 16 Posts: 85 Credit: 847,739 RAC: 0 |
This is not enough. Please follow instruction here to install extra software required to run them: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4971. |
Send message Joined: 22 Aug 16 Posts: 447 Credit: 2,090,661 RAC: 704 |
Not having a VBox setup puts the burden on the user to have all the requirements. Theory credits are stupidly low. Atlas is ok though and requires singularity setup but don't follow their guide as it will have you compiling everything instead of installing from repos. To add onto the link Daniel posted here is my setup for CVFMS and Singularity https://www.overclock.net/forum/365-overclock-net-boinc-team/1721752-projects-month-march-2019-a.html#post27876964 Atlas is still same app while Theory has separate apps selectable on LHC site and for WUProp. I'd also recommend an app_config as they don't use all the CPU threads requested. <app_config> |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
This is not enough. Please follow instruction here to install extra software required to run them: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4971. Not working for whatever reason ... steve@pboyztoy99:~$ sudo dpkg -i cvmfs-release-latest_all.deb dpkg: error: dpkg frontend is locked by another process steve@pboyztoy99:~$ rm -f cvmfs-release-latest_all.deb steve@pboyztoy99:~$ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:2 http://ca.archive.ubuntu.com/ubuntu bionic InRelease Get:3 http://ca.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Fetched 252 kB in 1s (296 kB/s) Reading package lists... Done steve@pboyztoy99:~$ sudo apt-get install cvmfs E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? steve@pboyztoy99:~$ |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
Crap now BOINC won't even connect, have network connected & can use Firefox but BOINC just spins it wheels without connecting ... Options to connect look okay ... Weird: If I reboot BOINC will connect again but as soon as I shut BOINC off it won't reconnect again unless I reboot again ... |
Send message Joined: 22 Aug 16 Posts: 447 Credit: 2,090,661 RAC: 704 |
dpkg: error: dpkg frontend is locked by another process Is there another install going? I'm guessing if so it would be cleared if you've reboot the PC since then. I've used the instructions on several 18.04 systems. |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
dpkg: error: dpkg frontend is locked by another process Yeah already thought of that but been debating whether to just uninstall BOINC reinstall it again. There's no reason to have to reboot each time I exit BOINC in order to get it to start again. Check the process manager but nothing shows up there that another instance it running so something must be messed up. May have to just wipe the Linux install out reinstall that, not a big deal since it's on the hard drive by itself ... |
Send message Joined: 21 Jun 13 Posts: 26 Credit: 842,542 RAC: 173 |
dpkg: error: dpkg frontend is locked by another process Obviously, there is another process locking dpkg database. And reinstalling the whole system will not help you. Did you install desktop Ubuntu? There is usually process like "apt-daemon" or whatever (i dont remember exactly) which locks dpkg database and don't allow you to use apt-get or even dpkg. This daemon is supposed to be helper for desktop "Software Center" or whatever it is called now or some kind of autoupdater. Just one of the desktop Ubuntu stupidities. Find it, kill it and try again, and do not ignore errors. PS: Last time I used Ubuntu as a desktop, the first thing I did after installation is to uninstall all that "user-friendly" bloatware daemons, auto-updaters and so on, lol. Good old aptitude (pseudo-graphical version of apt-get) ftw. PPS: I installed everyting for Theory Native on my home Ubuntu Server 18.04 some days ago and everything is working fine. |
Send message Joined: 3 Nov 10 Posts: 114 Credit: 3,170,681 RAC: 811 |
dpkg: error: dpkg frontend is locked by another process If you see the error “dpkg frontend is locked by another process†you’ll have to do the following: First, find out the id of the process that is holding the lock file. lsof /var/lib/dpkg/lock-frontend The above command will give you the PID of the processes using the lock files. Use this PID to kill the process. sudo kill -9 PID Now you can remove the lock and reconfigure dpkg: sudo rm /var/lib/dpkg/lock-frontend sudo dpkg --configure -a |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
lsof /var/lib/dpkg/lock-frontend... doesn't show or do anything when entered in the terminal steve@pboyztoy99:~$ sudo wget https://lhcathome.cern.ch/lhcathome/download/default.local -O /etc/cvmfs/default.local [sudo] password for steve: --2019-04-20 14:11:25-- https://lhcathome.cern.ch/lhcathome/download/default.local Resolving lhcathome.cern.ch (lhcathome.cern.ch)... 137.138.156.174 Connecting to lhcathome.cern.ch (lhcathome.cern.ch)|137.138.156.174|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 191 Saving to: ‘/etc/cvmfs/default.local’ /etc/cvmfs/default. 100%[===================>] 191 --.-KB/s in 0s 2019-04-20 14:11:26 (6.42 MB/s) - ‘/etc/cvmfs/default.local’ saved [191/191] steve@pboyztoy99:~$ sudo cvmfs_config reload steve@pboyztoy99:~$ cvmfs_config probe Probing /cvmfs/atlas.cern.ch... Failed! Probing /cvmfs/atlas-condb.cern.ch... Failed! Probing /cvmfs/grid.cern.ch... Failed! Probing /cvmfs/cernvm-prod.cern.ch... Failed! Probing /cvmfs/sft.cern.ch... Failed! Probing /cvmfs/alice.cern.ch... Failed! steve@pboyztoy99:~$ |
Send message Joined: 21 Jun 13 Posts: 26 Credit: 842,542 RAC: 173 |
Looks like you didn't start autofs service. Did you do cvmfs_config setup? |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
Looks like you didn't start autofs service. Did you do cvmfs_config setup? I have no idea what I started or didn't start. I really don't know anything about Linux or the commands needed to run certain things. I'm not worried if I run Theory Native or not, way to many commands & hoop jumping for me to worry about it, I thought there might be a simple solution but apparently not ... |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
Well whatever I did it possibly seems to have worked. For the heck of it I tried to get some work & the project gave me 2 WU's & they are running now past the 30 second mark anyway. Their up to 10% done so I assume their going to stay running ... Thanks for the help even if I didn't know what I was doing something worked |
Send message Joined: 21 Jun 13 Posts: 26 Credit: 842,542 RAC: 173 |
I asked a simple question: did you run "cvmfs_config setup" as described in the guide here https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html? Some people (including me) miss this step at first time. The guide also says "reload the autofs service in order to apply an updated configuration" without specifying how to do this, it should be "systemctl restart autofs". And finally you can check status with "systemctl status autofs" |
Send message Joined: 28 Mar 10 Posts: 671 Credit: 3,988,291 RAC: 683 |
Simple answer is I DON'T KNOW but whatever I did it worked as I'm running the Wu's so it doesn't matter if i know or not does it ... |
©2024 Sébastien