I am working on a Laravel project and was trying to referencing another project on GitHub. In the process of trying to open that project, my computer stalled and I restarted. Now this pops up every time I use vagrant up.
C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/psych.rb:370:in `parse': (<unknown>): found a tab character that violate intendation while scanning a plain scalar at line 22 column 11 (Psych::SyntaxError)
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/psych.rb:370:in `parse_stream'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/psych.rb:318:in `parse'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/psych.rb:245:in `load'
from C:/Users/ericc/Homestead/Vagrantfile:20:in `block in <top (required)>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/v2/loader.rb:37:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/v2/loader.rb:37:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:113:in `block (2 levels) in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:107:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:107:in `block in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:104:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/config/loader.rb:104:in `load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/vagrantfile.rb:28:in `initialize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:740:in `new'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:740:in `vagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:486:in `host'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:208:in `block in action_runner'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:33:in `call'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.rb:33:in `run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:473:in `hook'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb:722:in `unload'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:177:in `ensure in <main>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/bin/vagrant:177:in `<main>'
How can I solve this?
when you see this error, you should look the homestead.yaml file. there is space or enter extra.
Sometimes it's very hard to find the character that is messing with yml file.
Copy entire content of the following file and paste that in your ~/.homestead/Homestead.yaml
https://raw.githubusercontent.com/laravel/homestead/master/src/stubs/Homestead.yaml
Related
I try to migrate diaspora from a damaged debian 8 to another gentoo. I want to be able to can run diaspora before I deploy the web server. I crashes because of Ruby Errors, maybe kind of PATH errors.
When I run diaspora with script/server in production mode it crashes because the thing behind web.pid crashes. In the log eye_processes_stderr.log is:
bin/bundle:3:in `load': cannot load such file -- /usr/lib/ruby/bin/bundle (LoadError)
from bin/bundle:3:in `<main>'
In development mode I can not execute correctly (I tried it to get better error message reporting):
RAILS_ENV=development bin/rake db:migrate RAILS_ENV=development
bin/rake assets:precompile
because of the stdout and stderr of script/server I run: bin/bundle exec unicorn -c config/unicorn.rb
In production mode it returns:
that I shall look into stderr
and in the log there is nothing helpful, in:
tail log/eye_processes_stderr.log:
bin/bundle:3:in `load': cannot load such file -- /usr/lib/ruby/bin/bundle (LoadError)
from bin/bundle:3:in `<main>' bin/bundle:3:in `load': cannot load such file -- /usr/lib/ruby/bin/bundle (LoadError)
from bin/bundle:3:in `<main>'
But in development mode it returns:
I, [2019-10-07T11:14:20.840060 #20262] INFO -- : Refreshing Gem list
/home/diaspora/diaspora-2017-07-07-newest/config/environments/development.rb:64:in `block in <top (required)>': uninitialized constant TurboDevAssets (NameError)
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/railtie.rb:211:in `instance_eval'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/railtie.rb:211:in `configure'
from /home/diaspora/diaspora-2017-07-07-newest/config/environments/development.rb:3:in `<top (required)>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/engine.rb:600:in `block (2 levels) in <class:Engine>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/engine.rb:599:in `each'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/engine.rb:599:in `block in <class:Engine>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:30:in `instance_exec'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:30:in `run'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:59:in `block in run_initializers'
from /usr/lib/ruby/2.4.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/2.4.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
from /usr/lib/ruby/2.4.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
from /usr/lib/ruby/2.4.0/tsort.rb:431:in `each_strongly_connected_component_from'
from /usr/lib/ruby/2.4.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:48:in `each'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:48:in `tsort_each_child'
from /usr/lib/ruby/2.4.0/tsort.rb:415:in `call'
from /usr/lib/ruby/2.4.0/tsort.rb:415:in `each_strongly_connected_component_from'
from /usr/lib/ruby/2.4.0/tsort.rb:349:in `block in each_strongly_connected_component'
from /usr/lib/ruby/2.4.0/tsort.rb:347:in `each'
from /usr/lib/ruby/2.4.0/tsort.rb:347:in `call'
from /usr/lib/ruby/2.4.0/tsort.rb:347:in `each_strongly_connected_component'
from /usr/lib/ruby/2.4.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/2.4.0/tsort.rb:205:in `tsort_each'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/initializable.rb:58:in `run_initializers'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/railties-5.1.6.2/lib/rails/application.rb:353:in `initialize!'
from /home/diaspora/diaspora-2017-07-07-newest/config/environment.rb:7:in `<top (required)>'
from config.ru:10:in `require'
from config.ru:10:in `block in <main>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/rack-2.0.6/lib/rack/builder.rb:55:in `instance_eval'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/rack-2.0.6/lib/rack/builder.rb:55:in `initialize'
from config.ru:1:in `new'
from config.ru:1:in `<main>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/unicorn-5.5.0/lib/unicorn.rb:54:in `eval'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/unicorn-5.5.0/lib/unicorn.rb:54:in `block in builder'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/unicorn-5.5.0/lib/unicorn/http_server.rb:794:in `build_app!'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/unicorn-5.5.0/lib/unicorn/http_server.rb:141:in `start'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/gems/unicorn-5.5.0/bin/unicorn:128:in `<top (required)>'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `load'
from /home/diaspora/diaspora-2017-07-07-newest/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `<main>'
and now it returns that also in production mode, after I executed it in development mode.
line 64 in
/home/diaspora/diaspora-2017-07-07-newest/config/environments/development.rb
is:
# Speed up asset serving
config.middleware.insert 0, TurboDevAssets
It shall run as it did with every working diaspora as it has worked on debian 8 when I used rvm in the home directory. (as I also tried that on the Gentoo machine)
I'm trying to install Homestead on my terminal. I was in my home directory and ran the code "vagrant up" but I get an error. This was what I typed in:
MACs-MBP:Homestead MAC$ vagrant up
And this was the error:
/Users/MAC/web/Homestead/scripts/homestead.rb:118:in `read': No such file or directory # rb_sysopen - /Users/MAC/.ssh/id_rsa (Errno::ENOENT)
from /Users/MAC/web/Homestead/scripts/homestead.rb:118:in `block (2 levels) in configure'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/kernel_v2/config/vm_provisioner.rb:72:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/kernel_v2/config/vm_provisioner.rb:72:in `add_config'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/kernel_v2/config/vm.rb:338:in `provision'
from /Users/MAC/web/Homestead/scripts/homestead.rb:115:in `block in configure'
from /Users/MAC/web/Homestead/scripts/homestead.rb:114:in `each'
from /Users/MAC/web/Homestead/scripts/homestead.rb:114:in `configure'
from /Users/MAC/web/Homestead/Vagrantfile:35:in `block in <top (required)>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/v2/loader.rb:37:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/v2/loader.rb:37:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/loader.rb:113:in `block (2 levels) in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/loader.rb:107:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/loader.rb:107:in `block in load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/loader.rb:104:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/config/loader.rb:104:in `load'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/vagrantfile.rb:28:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:746:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:746:in `vagrantfile'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:492:in `host'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:214:in `block in action_runner'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/runner.rb:33:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/runner.rb:33:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:479:in `hook'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:728:in `unload'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/bin/vagrant:130:in `ensure in <main>'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/bin/vagrant:130:in `<main>'
How would I fix this? I am really confused. Thank you for all the help
The first line in your error message indicates that you need to generate an SSH key first.
In your terminal (but outside Homestead interface), type:
ssh-keygen -t rsa
When it asks for the directory to save your key, press Enter for default directory, which is where your Homestead is searching. When it asks for a passphrase, it's good to have one.
Then try vagrant up again.
The problem is that the server will not start.
I have set up the following:
Windows 10 build 1607 (Anniversary edition)
Windows subsystem for Linux
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Ubuntu 14.04.5 LTS \n \l
Rails ver 5.0.0.1
Ruby ver 2.3.1 (using - rbenv)
MySQL 5.5.53
I am very new to Linux and Ruby / Rails so please forgive me if I use incorrect terminology.
After a few days of installing, configuring and debugging, I was able to get everything working (Linux shell, rails, ruby mysql etc.).
I began a tutorial at Lynda called "Ruby on Rails 5 Essential Training" and was able to do the following:
Create a new rails project called Simple CMS
Create MySQL databases for development and test
Create users in MySQL
** When it came time to start the web server (Puma via the 'rails server' command) I received pages of errors as shown. I've searched every stackoverflow, google, Microsoft and GitHub result that had anything to do with "Failed to watch" and the above noted configuration. There were no solutions and the latest result stated that it was not possible to run the server because of the way Windows works.
Before scrapping my installation I wanted to ask here if anyone had run across this and/or had a solution.
Thank you very much in advance for any help and for taking the time to read this.
Mike
Here is the error including the command I used to initiate it:(Sorry its huge)
mike#MIKES-PC:~/sites/simple_cms$ rails server
=> Booting Puma
=> Rails 5.0.0.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Exiting
/home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rb-inotify-0.9.7/lib/rb-inotify/watcher.rb:74:in `initialize': Invalid argument - Failed to watch "/home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/locale": the given event mask contains no legal events; or fd is not an inotify file descriptor. (Errno::EINVAL)
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rb-inotify-0.9.7/lib/rb-inotify/notifier.rb:190:in `new'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rb-inotify-0.9.7/lib/rb-inotify/notifier.rb:190:in `watch'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rb-inotify-0.9.7/lib/rb-inotify/notifier.rb:204:in `watch'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/adapter/linux.rb:32:in `_configure'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/adapter/base.rb:45:in `block in configure'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/adapter/base.rb:40:in `each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/adapter/base.rb:40:in `configure'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/adapter/base.rb:63:in `start'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/backend.rb:28:in `start'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/listener.rb:67:in `block in <class:Listener>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/fsm.rb:120:in `instance_eval'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/fsm.rb:120:in `call'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/fsm.rb:91:in `transition_with_callbacks!'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/fsm.rb:57:in `transition' from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/listen-3.0.8/lib/listen/listener.rb:90:in `start' from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/evented_file_update_checker.rb:90:in `boot!'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/evented_file_update_checker.rb:61:in `initialize'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/i18n_railtie.rb:59:in `new'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/i18n_railtie.rb:59:in `initialize_i18n'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/i18n_railtie.rb:15:in `block in <class:Railtie>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/lazy_load_hooks.rb:45:in `block in run_load_hooks'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/lazy_load_hooks.rb:44:in `each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activesupport-5.0.0.1/lib/active_support/lazy_load_hooks.rb:44:in `run_load_hooks'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/application/finisher.rb:65:in `block in <module:Finisher>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/initializable.rb:30:in `instance_exec'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/initializable.rb:30:in `run'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/initializable.rb:55:in `block in run_initializers'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:347:in `each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:347:in `call'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/initializable.rb:54:in `run_initializers'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/application.rb:352:in `initialize!'
from /home/mike/sites/simple_cms/config/environment.rb:5:in `<top (required)>'
from /home/mike/sites/simple_cms/config.ru:3:in `require_relative'
from /home/mike/sites/simple_cms/config.ru:3:in `block in <main>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/builder.rb:55:in `instance_eval'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/builder.rb:55:in `initialize' from /home/mike/sites/simple_cms/config.ru:in `new'
from /home/mike/sites/simple_cms/config.ru:in `<main>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/builder.rb:49:in `eval'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/builder.rb:49:in `new_from_string'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/builder.rb:40:in `parse_file' from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/server.rb:318:in `build_app_and_options_from_config'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/server.rb:218:in `app'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/server.rb:59:in `app'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/rack-2.0.1/lib/rack/server.rb:353:in `wrapped_app'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/server.rb:124:in `log_to_stdout'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/server.rb:77:in `start'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/commands_tasks.rb:90:in `block in server'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/commands_tasks.rb:85:in `tap'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/commands_tasks.rb:85:in `server'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/railties-5.0.0.1/lib/rails/commands.rb:18:in `<top (required)>'
from /home/mike/sites/simple_cms/bin/rails:9:in `require'
from /home/mike/sites/simple_cms/bin/rails:9:in `<top (required)>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/client/rails.rb:28:in `load'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/client/rails.rb:28:in `call'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/client/command.rb:7:in `call'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/client.rb:30:in `run'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/bin/spring:49:in `<top (required)>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/binstub.rb:31:in `load'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/spring-2.0.0/lib/spring/binstub.rb:31:in `<top (required)>'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
from /home/mike/.rbenv/versions/2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
from /home/mike/sites/simple_cms/bin/spring:14:in `<top (required)>'
from bin/rails:3:in `load'
from bin/rails:3:in `<main>'
Found a solution in #jwsloan's comment on this Github issue:
When creating a new rails app, use --skip-listen to avoid problems with inotify, like so:
rails new myproject --skip-listen
That should allow the server to start - worked for me! :)
Note, I'm running this on a Windows Environment.
I'm working behind a corporate proxy, and trying to get the vagrant-proxyconf plug-in working so the vagrant machines can be set up to work through a proxy. However, on executing vagrant plugin install vagrant-proxyconf I got the following error:
Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is:
Could not fetch specs from http://gems.hashicorp.com/
Retrying source fetch due to error (2/3): Bundler::HTTPError Could not fetch specs from http://gems.hashicorp.com/Retrying source fetch due to error (3/3): Bundler::HTTPError Could not fetch specs from http://gems.hashicorp.com/
Figuring it was probably a proxy issue, I tried setting my environment variable:
set HTTP_PROXY="http://username:password#proxy:port"
After re-executing the plug-in install command, I got a different error:
C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in `split': bad URI(is not
URI?): http://"http://username:password#proxy:port" (URI::InvalidURIError)
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:211:in `parse'
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:747:in `parse'
from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:996:in `URI'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:908:in `proxy_from_env'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:858:in `proxy='
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/vendor/net/
http/persistent.rb:528:in `initialize'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
113:in `new'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
113:in `connection'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/fetcher.rb:
103:in `initialize'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `new'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `block in remote_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `map'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:262:in `remote_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:202:in `fetch_specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/source/ruby
gems.rb:66:in `specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:216:in `block (2 levels) in index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:213:in `each'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:213:in `block in index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/index.rb:9:
in `build'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:209:in `index'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:203:in `resolve'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:133:in `specs'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/definition.
rb:122:in `resolve_remotely!'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/installer.r
b:76:in `run'
from C:/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/installer.r
b:15:in `install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
226:in `block in internal_install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
284:in `block in with_isolated_gem'
from C:/Vagrant/embedded/lib/ruby/2.0.0/rubygems/user_interaction.rb:40:
in `use_ui'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
283:in `with_isolated_gem'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
225:in `internal_install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/bundler.rb:
92:in `install'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:62:in `block in install_plugin'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:72:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/plugin/mana
ger.rb:72:in `install_plugin'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/action/install_gem.rb:37:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/ward
en.rb:34:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/buil
der.rb:116:in `call'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runn
er.rb:66:in `block in run'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/util/busy.r
b:19:in `busy'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runn
er.rb:66:in `run'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/base.rb:14:in `action'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:32:in `block in execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:31:in `each'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/install.rb:31:in `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/plugins/commands/plugin
/command/root.rb:56:in `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/cli.rb:42:i
n `execute'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment
.rb:292:in `cli'
from C:/Vagrant/embedded/gems/gems/vagrant-1.6.5/bin/vagrant:174:in `<ma
in>'
Note the error:
C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:176:in 'split': bad URI(is not URI?): http://"http://username:password#proxy:port" (URI::InvalidURIError) from C:/Vagrant/embedded/lib/ruby/2.0.0/uri/common.rb:211:in parse'
Seems it's interpreting the environment variable incorrectly and having issues interpreting it? Anyone know how to address this issue?
You don't probably even need the quotes (unless the password includes some funny characters). So you could just try:
set HTTP_PROXY=http://username:password#proxy:port
If you need the quotes, the correct form is:
set "HTTP_PROXY=http://username:password#proxy:port"
I tried to install this dashing widget and I get the following error when I run dashing start
/var/lib/gems/1.9.1/gems/dashing-1.3.1/lib/dashing.rb:26:in `block (2 levels) in <top (required)>': undefined method `history' for Sinatra::Application:Class (NoMethodError)
So then I removed all aspects of this new widget (its folder in the /widgets directory, its job .rb file and the code in the .erb file). However this error persists and I am no longer able to even start my dashboard. This is a big problem for me. Can someone help me out?
EDIT:
The full error is
/var/lib/gems/1.9.1/gems/dashing-1.3.1/lib/dashing.rb:26:in `block (2 levels) in <top (required)>': undefined method `history' for Sinatra::Application:Class (NoMethodError)
from /var/lib/gems/1.9.1/gems/dashing-1.3.1/lib/dashing.rb:25:in `open'
from /var/lib/gems/1.9.1/gems/dashing-1.3.1/lib/dashing.rb:25:in `block in <top (required)>'
/usr/lib/ruby/1.9.1/psych.rb:203:in `parse': (history.yml): control characters are not allowed at line 1 column 1 (Psych::SyntaxError)
from /usr/lib/ruby/1.9.1/psych.rb:203:in `parse_stream'
from /usr/lib/ruby/1.9.1/psych.rb:151:in `parse'
from /usr/lib/ruby/1.9.1/psych.rb:127:in `load'
from /usr/lib/ruby/1.9.1/psych.rb:297:in `block in load_file'
from /usr/lib/ruby/1.9.1/psych.rb:297:in `open'
from /usr/lib/ruby/1.9.1/psych.rb:297:in `load_file'
from /var/lib/gems/1.9.1/gems/dashing-1.3.1/lib/dashing.rb:31:in `<top (required)>'
from config.ru:2:in `require'
from config.ru:2:in `block in <main>'
from /var/lib/gems/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
from /var/lib/gems/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
from config.ru:1:in `new'
from config.ru:1:in `<main>'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/rack/adapter/loader.rb:33:in `eval'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/rack/adapter/loader.rb:33:in `load'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/thin/controllers/controller.rb:182:in `load_rackup_config'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/thin/controllers/controller.rb:72:in `start'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/thin/runner.rb:200:in `run_command'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/lib/thin/runner.rb:156:in `run!'
from /var/lib/gems/1.9.1/gems/thin-1.6.1/bin/thin:6:in `<top (required)>'
from /usr/local/bin/thin:23:in `load'
from /usr/local/bin/thin:23:in `<main>'
I fixed this problem by renaming the old history file
mv history.yml history
and then restarting the server. In my case thats
rackup -p 3030 -s puma
The history.yml file didn't reappear until after I stopped the server. I checked it with nano and it was full of data.
Sorry I can't shed any light as to why it may have happened.
Server details. Ubuntu 13.10 32bit Desktop