[p2pu-dev] Problems with Vagrant

Chris Ewald chris at p2pu.org
Fri Jul 13 14:44:14 UTC 2012


cd into the top project directory.

On Fri, Jul 13, 2012 at 4:41 PM, Stian Håklev <shaklev at gmail.com> wrote:

> Thanks a lot for your support.
>
> More fun error messages:
>
> stian at Monkey ~/s/l/l/l/l/z/LC_MESSAGES> vagrant ssh
> /Users/Stian/src/lernanta-dev-env/Vagrantfile:85:in `read': No such file
> or directory - ./node.json (Errno::ENOENT)
>  from /Users/Stian/src/lernanta-dev-env/Vagrantfile:85:in `block (2
> levels) in <top (required)>'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:32:in
> `call'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:32:in
> `configure'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm/provisioner.rb:21:in
> `initialize'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm.rb:71:in
> `new'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/vm.rb:71:in
> `provision'
>  from /Users/Stian/src/lernanta-dev-env/Vagrantfile:78:in `block in <top
> (required)>'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:83:in
> `call'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:83:in
> `block (2 levels) in load'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:79:in
> `each'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:79:in
> `block in load'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:76:in
> `each'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/config/loader.rb:76:in
> `load'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:387:in
> `block in load_config!'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:392:in
> `call'
> from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:392:in
> `load_config!'
>  from
> /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/lib/vagrant/environment.rb:327:in
> `load!'
> from /usr/local/lib/ruby/gems/1.9.1/gems/vagrant-1.0.3/bin/vagrant:40:in
> `<top (required)>'
>  from /usr/local/bin/vagrant:23:in `load'
> from /usr/local/bin/vagrant:23:in `<main>'
>
> On Fri, Jul 13, 2012 at 10:38 AM, Chris Ewald <chris at p2pu.org> wrote:
>
>> Thanks for going through this Stian. We probably will have some things to
>> iron out as developers start actively using this.
>>
>> Re the git issue:
>> switch to master branch to fix this for you: git checkout -b master
>> I have added this to the setup script so a plain `git pull should work in
>> the future
>>
>> Not sure about the compile messages issue. You may want to try:
>> vagrant ssh
>> cd /opt/lernanta/lernata
>> Then whatever command you tried.
>>
>> If general if you ever use the command line, you need to use it from
>> inside the vm so it uses its' environment.
>>
>> Hope this helps and thanks!
>>
>> On Fri, Jul 13, 2012 at 4:21 PM, Stian Håklev <shaklev at gmail.com> wrote:
>>
>>> Thanks, I sent a pull request for two small updates to the README.md,
>>> not sure if this is where I ought to be adding info.
>>>
>>> PS: I wanted to play around with the Chinese localization, which is a
>>> bit half-assed at the moment (much easier when you can actually see the
>>> updates). I am curious about why the front page shows Browse groups &
>>> courses in English, yet when I look into django.po in zh_CN/LC_MESSAGES, I
>>> see
>>>
>>> #: templates/dashboard/splash.html:19
>>> #, fuzzy
>>> msgid "Browse Groups & Courses"
>>> msgstr "浏览小组 &课程"
>>>
>>> (I wondered if it was because the fuzzy tag was applied, so I tried
>>> removing it, and running
>>> django-admin.py compilemessages
>>>
>>> then I got
>>>
>>> stian at Monkey ~/s/l/l/l/l/z/LC_MESSAGES> django-admin.py compilemessages
>>> Error: This script should be run from the Django SVN tree or your
>>> project or app tree, or with the settings module specified.)
>>>
>>> Stian
>>>
>>> On Fri, Jul 13, 2012 at 10:08 AM, Jessy Kate Schingler <
>>> jessy at jessykate.com> wrote:
>>>
>>>> ditto on both counts!
>>>>
>>>> stian as you go through and realize clarifications, i would personally
>>>> think they'd be welcome additions/elaborations on the existing docs, if you
>>>> were so inclined. (no rest for the wicked :)).
>>>>
>>>>
>>>> On Fri, Jul 13, 2012 at 4:03 PM, Dirk Uys <dirk at p2pu.org> wrote:
>>>>
>>>>> Hi Stian
>>>>>
>>>>> Django should reload when code changes. It is still running using the
>>>>> built in web server, so it should be the same as running 'python manage.py
>>>>> runserver' on your local machine.
>>>>>
>>>>> If you have any suggestions on how we can further improve things,
>>>>> please let us know!
>>>>>
>>>>> Big hand for Chris' work and our brave explored Stian!
>>>>>
>>>>> Cheers
>>>>> d
>>>>>
>>>>>
>>>>> On Fri, Jul 13, 2012 at 3:58 PM, Jessy Kate Schingler <
>>>>> jessy at jessykate.com> wrote:
>>>>>
>>>>>> stian i think you should just be able to issue the more verbose "git
>>>>>> pull origin master" and the pull should work.
>>>>>>
>>>>>>
>>>>>> On Fri, Jul 13, 2012 at 3:52 PM, Stian Håklev <shaklev at gmail.com>wrote:
>>>>>>
>>>>>>> Brilliant, it works. Amazing, to think of the hours I spent trying
>>>>>>> to get this to work earlier!
>>>>>>>
>>>>>>> A few questions: is the lernanta source directory pulled in from the
>>>>>>> lernanta github repository, so that it stays in sync with the most
>>>>>>> up-to-date development? I tried git pull in that directory but got
>>>>>>>
>>>>>>> stian at Monkey ~/s/l/l/lernanta> git pull
>>>>>>> You asked me to pull without telling me which branch you
>>>>>>> want to merge with, and 'branch.deploy.merge' in
>>>>>>> your configuration file does not tell me, either. Please
>>>>>>> specify which branch you want to use on the command line and
>>>>>>> try again (e.g. 'git pull <repository> <refspec>').
>>>>>>> See git-pull(1) for details.
>>>>>>>
>>>>>>> If you often merge with the same branch, you may want to
>>>>>>> use something like the following in your configuration file:
>>>>>>>
>>>>>>>     [branch "deploy"]
>>>>>>>     remote = <nickname>
>>>>>>>     merge = <remote-ref>
>>>>>>>
>>>>>>>     [remote "<nickname>"]
>>>>>>>     url = <url>
>>>>>>>     fetch = <refspec>
>>>>>>>
>>>>>>> See git-config(1) for details.
>>>>>>> ----
>>>>>>>
>>>>>>> Also, does Django automatically refresh on new code, or do I need to
>>>>>>> restart the server when I modify the code? (Ie. vagrant down, and then
>>>>>>> vagrant up again, or is there a better way?).
>>>>>>>
>>>>>>> Thanks again, this will make it way easier for people to play with
>>>>>>> Lernanta on their own computers, contribute small patches, translate the
>>>>>>> interface, etc.
>>>>>>>
>>>>>>> Stian
>>>>>>>
>>>>>>> On Fri, Jul 13, 2012 at 8:37 AM, Chris Ewald <chris at p2pu.org> wrote:
>>>>>>>
>>>>>>>> You may need to update your virtual box as well:
>>>>>>>> https://www.virtualbox.org/wiki/Downloads
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Jul 13, 2012 at 2:36 PM, Chris Ewald <chris at p2pu.org>wrote:
>>>>>>>>
>>>>>>>>> Hi Stian,
>>>>>>>>>
>>>>>>>>> Delete the directory and clone it again. It's all fixed now.
>>>>>>>>>
>>>>>>>>> On Fri, Jul 13, 2012 at 2:33 PM, Stian Håklev <shaklev at gmail.com>wrote:
>>>>>>>>>
>>>>>>>>>> I tried the new Vagrant procedures, I got the following error
>>>>>>>>>> messages:
>>>>>>>>>>
>>>>>>>>>> [default] The guest additions on this VM do not match the install
>>>>>>>>>> version of
>>>>>>>>>> VirtualBox! This may cause things such as forwarded ports, shared
>>>>>>>>>> folders, and more to not work properly. If any of those things
>>>>>>>>>> fail on
>>>>>>>>>> this machine, please update the guest additions and repackage the
>>>>>>>>>> box.
>>>>>>>>>>
>>>>>>>>>> Guest Additions Version: 4.1.16
>>>>>>>>>> VirtualBox Version: 4.1.18
>>>>>>>>>>
>>>>>>>>>> then later
>>>>>>>>>>
>>>>>>>>>> [default] Running chef-solo...
>>>>>>>>>> stdin: is not a tty
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: *** Chef 0.10.10 ***
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Setting the run_list to
>>>>>>>>>> ["main::default", "mysql::server", "main::python", "main::lernanta"] from
>>>>>>>>>> JSON
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Run List is
>>>>>>>>>> [recipe[main::default], recipe[mysql::server], recipe[main::python],
>>>>>>>>>> recipe[main::lernanta]]
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Run List expands to
>>>>>>>>>> [main::default, mysql::server, main::python, main::lernanta]
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Starting Chef Run for
>>>>>>>>>> precise32
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Running start handlers
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] INFO: Start handlers complete.
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] WARN: found a directory mysql
>>>>>>>>>> in the cookbook path, but it contains no cookbook files. skipping.
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] WARN: found a directory openssl
>>>>>>>>>> in the cookbook path, but it contains no cookbook files. skipping.
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] ERROR: Running exception
>>>>>>>>>> handlers
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] ERROR: Exception handlers
>>>>>>>>>> complete
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] FATAL: Stacktrace dumped to
>>>>>>>>>> /tmp/vagrant-chef-1/chef-stacktrace.out
>>>>>>>>>> [Fri, 13 Jul 2012 12:31:52 +0000] FATAL:
>>>>>>>>>> Chef::Exceptions::CookbookNotFound: Cookbook mysql not found. If you're
>>>>>>>>>> loading mysql from another cookbook, make sure you configure the dependency
>>>>>>>>>> in your metadata
>>>>>>>>>> Chef never successfully completed! Any errors should be visible
>>>>>>>>>> in the
>>>>>>>>>> output above. Please fix your recipes so that they properly
>>>>>>>>>> complete.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> http://reganmian.net/blog -- Random Stuff that Matters
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> p2pu-dev mailing list
>>>>>>>>>> p2pu-dev at lists.p2pu.org
>>>>>>>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> p2pu-dev mailing list
>>>>>>>> p2pu-dev at lists.p2pu.org
>>>>>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> http://reganmian.net/blog -- Random Stuff that Matters
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> p2pu-dev mailing list
>>>>>>> p2pu-dev at lists.p2pu.org
>>>>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jessy Kate Schingler
>>>>>> http://jessykate.com
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> p2pu-dev mailing list
>>>>>> p2pu-dev at lists.p2pu.org
>>>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> p2pu-dev mailing list
>>>>> p2pu-dev at lists.p2pu.org
>>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jessy Kate Schingler
>>>> http://jessykate.com
>>>>
>>>>
>>>> _______________________________________________
>>>> p2pu-dev mailing list
>>>> p2pu-dev at lists.p2pu.org
>>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> http://reganmian.net/blog -- Random Stuff that Matters
>>>
>>>
>>> _______________________________________________
>>> p2pu-dev mailing list
>>> p2pu-dev at lists.p2pu.org
>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>>
>>
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
>>
>
>
> --
> http://reganmian.net/blog -- Random Stuff that Matters
>
>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120713/a478bc3d/attachment-0001.html>


More information about the p2pu-dev mailing list