| *** rajm has joined #cip | 07:01 | |
| *** toscalix has joined #cip | 07:39 | |
| *** toscalix has quit IRC | 07:40 | |
| *** toscalix has joined #cip | 07:40 | |
| *** toscalix has joined #cip | 07:41 | |
| *** toscalix has quit IRC | 07:41 | |
| *** toscalix has joined #cip | 07:41 | |
| * rajm runs a successful healthcheck on BBB with an email to the list | 07:53 | |
| *** patersonc has joined #cip | 08:03 | |
| *** mungaip has joined #cip | 08:16 | |
| patersonc | Hello rajm, meet mungaip (Patryk) | 08:27 |
|---|---|---|
| rajm | hi mungaip - I've just replied to your email (thanks patersonc ) | 08:30 |
| *** dl9pf has quit IRC | 08:35 | |
| *** dl9pf has joined #cip | 08:37 | |
| *** dl9pf has joined #cip | 08:37 | |
| mungaip | Hi rajm, I have just read your email. I have just done step 6 again on the website, but when I run the 'vagrant provision' command, it comes up with an error that there was "no matching distribution found for cffi" | 08:49 |
| rajm | so you had done that step the prev time - hmmm! can you try creating that marker file on the VM and then rerunning provision? | 08:54 |
| rajm | I'm just trying a fresh provision from an empty vm - just to check here | 08:56 |
| mungaip | I have just added that marker file in the specified directory. Now when running the provision, it cannot find the install_backend.sh script | 09:03 |
| rajm | what's in /vagrant/integration-scripts on the VM - there's nothing in the provision that removes it, puzzling! | 09:05 |
| mungaip | All the installation scripts by the looks of it. Unless I typed something wrong when creating the directories or the marker file | 09:08 |
| mungaip | I will try once more | 09:08 |
| mungaip | No I have the same problem as before. As soon as I create the marker file, the provisioning cannot find the install scripts by the looks of it. Very strange | 09:12 |
| *** darknighte_ has joined #cip | 09:16 | |
| rajm | very odd, does ~/.buildpy.cfg exist in the vm? i'd do a vagrant destroy and then vagrant up to start that one from scratch | 09:17 |
| *** darknighte has quit IRC | 09:18 | |
| *** darknighte_ is now known as darknighte | 09:18 | |
| rajm | my fresh provision is working for me - just got to that step 6 - but looks ok so far, I have a more recent version of vagrant & virtualbox but your versions look ok | 09:18 |
| mungaip | No it doesn't. I'll do that, and get back to you on how it goes | 09:18 |
| rajm | ok ta! so looks as if install_backend never was found one the manual provision stage | 09:20 |
| rajm | mungaip: yes my fresh provision completes (at least as far as the end of configure_lava.sh) | 09:29 |
| mungaip | rajm, I have got to step 5 in building another vagrant VM after destroying the previous one, but running vagrant up stops again when looking for a distribution for cffi. So I never get the output at the start of stage 6 | 09:37 |
| rajm | ta can you put the output up to the failure on pastebin (or similar). that cffi message rings a bell, checking up | 09:40 |
| mungaip | rajm here's the full output from the vagrant up command to the failure: https://pastebin.com/yHWe6eqA | 09:55 |
| rajm | thanks! | 09:58 |
| mungaip | Hi rajm, I think I've got to the bottom of the issue. It seems that the pip command has been disabled, so running "pip install <package>" will always come up with that error that I saw with cffi, no matter what package I'm trying to install | 11:18 |
| mungaip | I tried manually doing the same thing using the command "sudo apt-get install python-cffi" within the vagrant VM and the package sure enough installed | 11:20 |
| mungaip | I'll try running vagrant provision with a modified install_dependencies script to see if that works | 11:21 |
| rajm | let me look shortly - i've just run install-dependenies and was going to compare your and my output | 11:22 |
| mungaip | okay thank | 11:25 |
| rajm | just taking lunch back in 30mins | 11:29 |
| mungaip | Okay same here | 11:31 |
| mungaip | It worked for me for all the packages other than ansible | 11:31 |
| *** ironfoot has quit IRC | 12:15 | |
| rajm | hmm too many differences for diff (or emacs diff) to cope with easily, pip for me is in /usr/local/bin and --version gives pip 18.0 from /usr/local/lib/python2.7/dist-packages/pip (python 2.7) | 12:16 |
| *** ironfoot has joined #cip | 12:19 | |
| *** toscalix has quit IRC | 12:29 | |
| *** toscalix has joined #cip | 12:29 | |
| *** toscalix has quit IRC | 12:29 | |
| *** toscalix has joined #cip | 12:29 | |
| mungaip | rajm I have pip 9.0.1 from /usr/lib/python2.7/dist-packages (python 2.7) | 12:30 |
| mungaip | I have tried upgrading pip, but that's the latest version available to me | 12:32 |
| mungaip | rajm what operating system are you using? | 12:33 |
| rajm | on the host I have debian 9.5 but I assume the issue is with the version in the VM | 12:36 |
| mungaip | Yes I agree. I can try to install a newer version of the VM to see if I continue to get the same problems? | 12:42 |
| mungaip | These are the steps I took, which made me think it's an issue with the way pip works on the VM... https://pastebin.com/sQvDMgpV | 12:44 |
| rajm | you mean a newer debian version, I'll look at what the scripts do before that point | 12:54 |
| rajm | s/version,/version?/ | 12:56 |
| mungaip | sorry, I meant a newer version of vagrant | 13:20 |
| rajm | though I think I was using 1.9.1 until recently, I will check | 13:23 |
| rajm | no I think I had 2.0.4 from april and 1.9.1 before april, though you're getting the error very early on which is concerning | 13:54 |
| rajm | but I'm intending to install 1.9.1 to rule that out (I hope!) | 13:57 |
| rajm | 'dpkg: warning: ignoring request to remove virtualbox, only the config files of which are on the system' however running virtualbox from command line works (I wonder how I installed it!?) | 14:25 |
| rajm | arrgh - installed 1.9.1 of vagrant but installing virtualbox installs version 5.2 which vagrant whinges about saying it's not supported | 14:34 |
| mungaip | I think I had that problem originally which is why I resorted to installing virtualbox 5.1 | 14:37 |
| rajm | well at least it has brought up issues that need addressing in the install instructions! | 14:46 |
| toscalix | bwh just told me about this problem https://www.intel.com/content/www/us/en/architecture-and-technology/l1tf.html | 14:49 |
| toscalix | it seems there is a mitigation he will incorporate in CIP 4.4 kernel | 14:49 |
| toscalix | another link https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/ | 14:50 |
| toscalix | patersonc: szlin fyi | 14:50 |
| patersonc | Thanks toscalix | 14:51 |
| bwh | I think this is low severity for CIP applications, like the other speculation issues, but since it's high profile I expect you'll have people in your organisations asking anywy | 15:08 |
| szlin | toscalix: thanks! | 15:18 |
| toscalix | thanks bwh :-) | 15:23 |
| *** mungaip has quit IRC | 15:51 | |
| *** rajm has quit IRC | 16:01 | |
| *** toscalix has quit IRC | 16:33 | |
| *** CTtpollard has quit IRC | 16:55 | |
| *** patersonc has quit IRC | 18:55 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!