Can't install on OS X 10.9
Closed this issue · 26 comments
Trying to install on OS X 10.9 with VirtualBox 4.3.18 / Vagrant 1.6.5.
When I do "vagrant up", I get the following error:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'opengenera'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: opengenera_default_1413605625638_85781
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5901 => 5902 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /Users/seth/opengenera
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
usage: sudo [-HPSb] [-p prompt] [-u username|#uid]
{ -e file [...] | -i | -s | <command> }
Stderr from the command:
sudo: illegal option `-E'
usage: sudo -K | -L | -V | -h | -k | -l | -v
This was fixed in 2a1b, but requires the basebox be recreated. You might avoid the rebuild by applying the 'sudo' workaround at the end of https://github.com/ynniv/opengenera/blob/master/definitions/ubuntu-7.10-server-amd64/postinstall.sh.
I installed fresh from a brand new clone of the repo and made sure to delete all of my baseboxes, but it's still failing in exactly the same way for me in 7cc10e6. Am I missing something obvious?
I installed from a brand new clone and got this result -->
BEGIN>>>
f want to use Phusion Passenger (http://www.modrails.com) in combination
with Ruby Enterprise Edition, then you must reinstall Phusion Passenger against
Ruby Enterprise Edition, as follows:
/opt/ruby/bin/passenger-install-apache2-module
Make sure you don't forget to paste the Apache configuration directives that
the installer gives you.
If you ever want to uninstall Ruby Enterprise Edition, simply remove this
directory:
/opt/ruby
If you have any questions, feel free to visit our website:
http://www.rubyenterpriseedition.com
Enjoy Ruby Enterprise Edition, a product of Phusion (www.phusion.nl) :-)
ERROR: Could not find a valid gem 'chef' (>= 0) in any repository
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)
SocketError: getaddrinfo: Name or service not known (http://rubygems.org/latest_specs.4.8.gz)
ERROR: exit code 1
Error executing command echo 'vagrant'|sudo -S sh './postinstall.sh' : Exitcode was not what we expected
Exitcode was not what we expected
Checking user - OK
Checking sudo - OK
Checking ruby - OK
Checking gem - OK
Checking chef - FAILED
Command: . /etc/profile ;chef-client --version 2> /dev/null 1>/dev/null; echo $?
Expected string 0
Output:
Checking puppet - FAILED
Command: . /etc/profile ;puppet --version 2> /dev/null 1>/dev/null; echo $?
Expected string 0
Output:
Checking shared folder - FAILED
Command: mount|grep veewee-validation; echo $?
Expected string 0
Output:
Vagrant requires the box to be shutdown, before it can export
Sudo also needs to work for user vagrant
Performing a clean shutdown now.
Waiting for ssh login on 127.0.0.1 with user vagrant to sshd on port => 7222 to work, timeout=10000 sec
.
Executing command: echo 'shutdown -P now' > /tmp/shutdown.sh
Waiting for ssh login on 127.0.0.1 with user vagrant to sshd on port => 7222 to work, timeout=10000 sec
.
Executing command: chmod +x /tmp/shutdown.sh
Waiting for ssh login on 127.0.0.1 with user vagrant to sshd on port => 7222 to work, timeout=10000 sec
.
Executing command: echo 'vagrant'|sudo -S sh '/tmp/shutdown.sh'
Broadcast message from root@ubuntu-7.10-server-amd64
(unknown) at 11:43 ...
The system is going down for power off NOW!
...........
Machine ubuntu-7.10-server-amd64 is powered off cleanly
Creating a temporary directory for export
Adding additional files
Creating Vagrantfile
Exporting the box
Executing VBoxManage export "ubuntu-7.10-server-amd64" --output "/var/folders/pd/l_ms46x55n7704409tgxyp9w0000gp/T/d20141022-4051-1e44xyr/box.ovf"
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully exported 1 machine(s).
Packaging the box
Cleaning up temporary directory
To import it into vagrant type:
vagrant box add 'ubuntu-7.10-server-amd64' '/Users/M_M/Documents/og/ubuntu-7.10-server-amd64.box'
To use it:
vagrant init 'ubuntu-7.10-server-amd64'
vagrant up
vagrant ssh
==> box: Adding box 'opengenera' (v0) for provider:
box: Downloading: file:///Users/M_M/Documents/og/ubuntu-7.10-server-amd64.box
==> box: Successfully added box 'opengenera' (v0) for 'virtualbox'!
[10/22 11:44:52] M_M@admins-iMac:og (2501)$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'opengenera'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: og_default_1414003515202_94423
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5901 => 5902 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
END>>>
Note that not all the Ruby packages were found... I killed the execution, since it never succeeded in connecting. I also turned off Remote Management on the Macintosh, so that it would be possible to use VNC and SSH to the 'localhost' address.
With vagrant there are opportunities for stale data, even with a clean repo. Try vagrant box list, and if there is still a box named opengenera, remove that with vagrant box remove opengenera. You might also remove any opengenera directory in ~/.vagrant.d/boxes/. I probably need to update the clean target in Makefile.
Hi:
I was doing the 'vagrant box remove opengenera', since I'd noticed that the 'make clean' followed by a 'make' was not doing anything... I'll look at the '.vagrant.d' directory as well.
----- Original Message -----
From: "Vinny Fiano" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Thursday, October 23, 2014 7:03:32 AM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
With vagrant there are opportunities for stale data, even with a clean repo. Try vagrant box list`, and if there is still a box named opengenera, remove that with vagrant box remove opengenera``. You might also remove any opengenera directory in ~/.vagrant.d/boxes/. I probably need to update the clean target in Makefile.
—
Reply to this email directly or view it on GitHub .
Even a successful build has some output that looks like failure. Check your output against the just-added notes/full-make.log.
Also, you don't need to modify Remote Management because we're using port 5902 instead of 5901.
Hi Vinny:
I followed in the log (in parallel) while redoing the full install after 'make clean' and the 'vagrant' commands to eliminate the old information.
It logs on now, but I only get as far as -
BEGIN>>>
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5901 => 5902 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /Users/M_M/Documents/og
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
usage: sudo [-HPSb] [-p prompt] [-u username|#uid]
{ -e file [...] | -i | -s | }
Stderr from the command:
sudo: illegal option `-E'
usage: sudo -K | -L | -V | -h | -k | -l | -v
END>>>
There are a lot of commands after this in the log of a successful install, so I'm pretty sure that the virtual machine isn't ready for use at this point.
There's mention of having to rebuild the 'box' in order to resolve the SSH issue, but the link to how to build the base box [http://docs-v1.vagrantup.com/v1/docs/base_boxes.html] is quite vague. Can you provide any hints on what the next step is that I should take?
----- Original Message -----
From: "Vinny Fiano" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Thursday, October 23, 2014 1:09:54 PM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
Even a successful build has some output that looks like failure. Check your output against the just-added notes/full-make.log.
Also, you don't need to modify Remote Management because we're using port 5902 instead of 5901.
—
Reply to this email directly or view it on GitHub .
I'm pretty sure that I have a fix for this. There were a couple of minor issues in the veewee base box build. I've issued a pull request (#11) that I hope addresses them.
I manually merged changes for the VirtualBox additions script and sudo wrapper executable bit. I haven't verified the output of these changes, but they both seem necessary. I also added an echo to the beginning and end of the postinstall script. If you don't see POSTINSTALL COMPLETE, something is still wrong.
The install almost completes!
Instead of the last four lines
BEGIN>>>
==> default: start opengenera under vnc
==> default: xauth: creating new authority file /root/.Xauthority
==> default:
==> default: New 'genera-host:1 (root)' desktop is genera-host:1
==> default: Starting applications specified in /root/.vnc/xstartup
==> default: Log file is /root/.vnc/genera-host:1.log
END>>>
I see
BEGIN>>>
==> default: start opengenera under vnc
==> default:
==> default: You will require a password to access your desktops.
==> default: getpassword error: Invalid argument
==> default: Password:
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
END>>>
I'm not sure why this would work on my machine and not yours, but I just pushed a change that specifies HOME in the same way that /etc/rc.local does. This may fix this problem for you.
The install completes!
However, when I VNC to the VirtualBox, using either 'open vnc://localhost:5902' or via a VNC client application, I get a white screen with 'root@genera-host:~#' displayed at the top, not the Genera opening screen.
The .vnc/genera-host:1.log file is:
BEGIN>>>
Xvnc Free Edition 4.1.1
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 70000000, The X.Org Foundation
Tue Oct 28 16:18:46 2014
vncext: VNC extension running!
vncext: Listening for VNC connections on port 5901
vncext: creating VNC server for screen 0
error opening security policy file /etc/X11/server/SecurityPolicy
Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /usr/share/fonts/X11/Type1/, removing from list!
Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
Could not init font path element /usr/share/fonts/X11/100dpi/, removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi/, removing from list!
Tue Oct 28 16:18:54 2014
Connections: accepted: 10.0.2.2::59198
SConnection: Client needs protocol version 3.3
Tue Oct 28 16:18:59 2014
Connections: closed: 10.0.2.2::58198 (Clean disconnection)
Connections: accepted: 10.0.2.2::59199
SConnection: Client needs protocol version 3.3
VNCSConnST: Server default pixel format depth 16 (16bpp) little-endian rgb565
VNCSConnST: Client pixel format depth 32 (32bpp) little-endian rob max
255,255,255 shift 16,8,0
END>>>
[I couldn't do a text-capture from the VNC client screen, so I've just re-typed it.]
When I did a 'restart-genera' from the displayed command line on the VNC client, I got the message
BEGIN>>>
Command 'restart-genera' is available in '/usr/local/bin/restart-genera'
The command could not be located because '/usr/local/bin' is not included in the PATH environment variable.
bash: restart-genera: command not found
END>>>
I got a similar message when entering the 'run-genera' command.
When I manually added '/usr/local/bin' to the PATH environment variable for root and entered the 'run-genera' command (or the 'restart-genera' command), nothing appeared to happen.
The 'ps -ax' command shows nothing other than kernel threads, executables from /sbin and /usr/sbin, the Xvnc and ratpoison executables and the bash shell.
The /var/lib/symbolics directory is present and appears to be complete - it has Genera-8-5.vld, README, VLM_debugger, dot.VLM, genera, the rel-8-5 and sys.sct directories and the restart-genera and run-genera scripts.
If I 'cd /var/lib/symbolics' and issue the './genera' command, I get the blank Genera screen; issuing the 'vagrant ssh -c restart-genera' command from the Mac OS X command-line causes Genera to exit on the VNC display with the following:
BEGIN>>>
tx ip: 10.0.0.2 10.0.0.1
rx ip: 10.0.0.1 10.0.0.2
... repeated many times
tx ip: 10.0.0.2 255.255.255.255 udp; 1025 37
rx ip: 10.0.0.1 10.0.0.2 udp; 37 1025
keycode1 0, keycode2 0
dec keyboard
keycode1 0, keycode2 65
Lisp is running!
If you exit, the current state of Lisp will be lost.
All information in its memory image (e.g., any modified editor
buffers) will be irretrievably lost. Further, Lisp will abandon
any tasks it is performing for its clients.
Do you still wish to exit? (yes or no) Bus error
END>>>
That's basically all that I was able to do.
Yes, this is common bug. Per the README, run vagrant ssh -c restart-genera.
I issued the 'vagrant ssh -c restart-genera' command several different times; sometimes I restarted the VM before doing it, sometimes I did it after doing the 'open' and getting the console prompt.
I could watch the processes with 'top' and 'restart-genera' would appear briefly and then vanish, with no other effect.
Can you link to a https://gist.github.com/ of the file /var/lib/symbolics/genera.log? Also, I think from your previous issue with HOME that you have somehow misconfigured something. Starting from make clean, what commands have you run?
Hi:
The commands that I used were -
- make clean
- make && vagrant up
- open vnc://localhost:5902
From the command-line, I couldn't scp into or out of the machine, so I've done a screen capture of the .vnc/genera:1.log file and the /var/lib/symbolics directory, where there is no genera.log file.
----- Original Message -----
From: "Vinny Fiano" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Tuesday, October 28, 2014 1:08:55 PM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
Can you link to a https://gist.github.com/ of the file /var/lib/symbolics/genera.log? Also, I think from your previous issue with HOME that you have somehow misconfigured something. Starting from make clean , what commands have you run?
—
Reply to this email directly or view it on GitHub .
You should be able to use vagrant ssh to connect to the virtual machine, where you can cat the log file and copy it out of the terminal. You may need to use sudo -s to become root to access some things.
Hi Vinny:
In my earlier post, I had logged in via VNC, and opened each of the directories that you were interested in.
This time, I used 'vagrant ssh' as you recommended - which works just fine - and used 'cat' for the .vnc log file:
BEGIN>>
Xvnc Free Edition 4.1.1
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 70000000, The X.Org Foundation
Wed Oct 29 15:48:26 2014
vncext: VNC extension running!
vncext: Listening for VNC connections on port 5901
vncext: created VNC server for screen 0
error opening security policy file /etc/X11/xserver/SecurityPolicy
Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /usr/share/fonts/X11/Type1/, removing from list!
Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
Could not init font path element /usr/share/fonts/X11/100dpi/, removing from list!
Could not init font path element /usr/share/fonts/X11/75dpi/, removing from list!
END>>
Note that there is no log file in the /var/lib/symbolics directory. I don't think that genera actually got started - the genera executable does not appear in 'ps ax'.
----- Original Message -----
From: "Vinny Fiano" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Tuesday, October 28, 2014 4:19:14 PM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
You should be able to use vagrant ssh to connect to the virtual machine, where you can cat the log file and copy it out of the terminal. You may need to use sudo -s to become root to access some things.
—
Reply to this email directly or view it on GitHub .
I'm having problems on OS X Yosemite:
When running vagrant up it gets to a certain point and just stops. How far it gets varies between runs. I've made a gist of the output from make as well as a few examples from vagrant up https://gist.github.com/bishboria/0cc91d8386163ece7273
after vagrant up stops I tried vagrant ssh just in case. It complains that "VM must be created before running this command. Run vagrant up first."
I'd love to get this project running! :) I think I'm quite close.
In case it helps anyone, I had a similar issue where the X session would have one xterm open but genera wouldn't launch at all. I found that if, in that xterm, I just launched genera manually with something like "./genera" it would come up once partway with the black bar at the bottom. After killing it and re-running "./genera" it would come up fine and everything would work from then on.
Further, I found that you can, indeed, save your world. The catch is that you can't save it to the same file that you loaded it from. That seems to crash genera and also corrupt the world file. If you just give it a different name at the Save World prompt, it works fine and can then be loaded with "./genera -world my-world.vlod"
Hopefully this helps some of you get up and running. It's a fascinating system!
I list the steps that made it work for me on OS X 10.10:
-
open
definitions/ubuntu-7.10-server-amd64/postinstall.sh -
Remove the lines
#Installing chef & Puppet /opt/ruby/bin/gem install chef --no-ri --no-rdoc /opt/ruby/bin/gem install puppet --no-ri --no-rdocand save the file
-
run
make -
After
makehas finished (this complaints that chef and puppet cannot be found. But just ignore it), firevagrant up -
When the box is running proceed with
open vnc://localhost:5902. This opens an xterm window in Screen Sharing App. -
In the xterm window, go to
/var/lib/symbolics -
Type in
./genera. This starts genera in a somehow "broken" state. -
In your other terminal window (your host terminal. The one you typed in
vagrant up) runvagrant ssh -c restart-genera. -
Back in the xterm window type again
./genera -
Presto! Genera should be running.
Which lines?
----- Original Message -----
From: "Sebastian Christ" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Saturday, December 13, 2014 3:00:09 AM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
I list the steps that made it work for me on OS X 10.10:
1. open definitions/ubuntu-7.10-server-amd64/postinstall.sh
2. Remove the lines
—
Reply to this email directly or view it on GitHub .
@opendragon I hit the comment button too early, accidentally. After that I edited my comment multiple times. It seem that you get email notifications and so you missed the edits. Anyway, the lines i removed again:
#Installing chef & Puppet
/opt/ruby/bin/gem install chef --no-ri --no-rdoc
/opt/ruby/bin/gem install puppet --no-ri --no-rdoc
Thanks, rudolfochrist, your instructions helped me getting it to run... over the December break I'm going to explore what is involved in getting vagrant and VMware to work with it.
[I've got the Lisp Machine book [Lisp Lore] as well as a MacIvory II and the full (printed) documentation set, so I should have no issues on the Lisp side!]
This is independent of the host version. Chef installs Phusion Passenger, which wants to install an addition that requires a ruby version greater than the one installed. rudolfochrist's changes resolve this and don't cause trouble later in the installation, so I have applied them.
Hi:
I've never 'committed' a change to a repository that I didn't manage, but I have a change that I'd like to suggest, and I've enclosed the patch for it.
The 'ubuntu-7.10-server-amd64.box' file that gets built does not need to be put in the repository, and should be ignored.
----- Original Message -----
From: "Vinny Fiano" notifications@github.com
To: "ynniv/opengenera" opengenera@noreply.github.com
Cc: "opendragon" turing@shaw.ca
Sent: Thursday, February 19, 2015 7:08:12 AM
Subject: Re: [opengenera] Can't install on OS X 10.9 (#10)
This is independent of the host version. Chef installs Phusion Passenger, which wants to install an addition that requires a ruby version greater than the one installed. rudolfochrist's changes resolve this and don't cause trouble later in the installation, so I have applied them.
—
Reply to this email directly or view it on GitHub .