This was driving me crazy but even after solving it, I fell fairly stupid.
I am running
bundle install inside a new app – while studying RoR – and I am getting this error:
computer:timetracker user$ bundle install
Fetching gem metadata from https://rubygems.org/………
Fetching additional metadata from https://rubygems.org/..
Using rake 10.1.0
Using i18n 0.6.9
Using minitest 4.7.5
Using multi_json 1.8.2
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
/Users/user/.rvm/rubies/ruby-2.1.2/bin/ruby: invalid option -7 (-h will show valid options) (RuntimeError)
extconf failed, exit code 1
Gem files will remain installed in /Users/user/workspace/safari-ruby-course/safari-ror-course-all-files/Chapter 7/timetracker/vendor/bundle/gems/atomic-1.1.14 for inspection.
Results logged to /Users/user/workspace/safari-ruby-course/safari-ror-course-all-files/Chapter 7/timetracker/vendor/bundle/extensions/x86_64-darwin-13/2.1.0-static/atomic-1.1.14/gem_make.out
An error occurred while installing atomic (1.1.14), and Bundler cannot continue.
Make sure that `gem install atomic -v ’1.1.14′` succeeds before bundling.
The problem is – and I bet everybody but me knew – is the space in the name of one of the directory (“Chapter 7″).
The only consolation – if any – is that I would have never created a directory with a space – it’s part of the tutorial I am studying.
The following was executed on xubuntu running in a VirtualBox VM inside a MacOS X Maverick.
user@xubuntu64:~$ uname -a
Linux xubuntu64 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
You need to have access to the grub menu.
1) boot your VM
2) at the grub menu, press “e” on the ubuntu entry
3) go to the line starting with linux and add at the end “rw init=/bin/bash” (if you have “ro” at the end, remove it – don’t leave both ro and rw)
4) press cntrl-x to boot the VM
5) you will end up at the bash shell (no password asked)
6) verify that the root filesystem is mounted in rw mode (touch /etc/aa; rm /etc/aa)
7) execute “passwd root” and provide the new password
8) execute a “sync” (quite certainly useless but it won’t harm)
9) send your VM a cntrl-alt-del via VM menu (here reboot, init, halt and shutdown commands will not work and if you type “exit” the kernel will panic)
I did a
I should have used the service command instead.
After the killall, if I check the status of the service I get an unusual message:
[root@steve run]# service docker status
docker dead but subsys locked
A lock file has been left behind:
[root@steve run]# cd /var/lock/subsys/
[root@steve subsys]# ls -l
-rw-r--r--. 1 root root 0 May 30 20:03 docker
[root@steve subsys]# fuser docker
[root@steve subsys]# rm docker
rm: remove regular empty file `docker'? y
[root@steve subsys]# service docker status
docker is stopped
In /var/run there was also a docker.sock file which I also removed.
This workaround applies to any service either killed by hand or crashed which had a lock file in /var/lock/subsys.
SELECT table_schema "DB NAME",
Round(Sum(data_length + index_length) / 1024 / 1024, 1) "DB SIZE (MB)"
GROUP BY table_schema;