You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/01/27 21:55:40 UTC

[jira] [Commented] (AURORA-123) Building/provisioning vagrant VMs fails on OSX Mavericks.=

    [ https://issues.apache.org/jira/browse/AURORA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883280#comment-13883280 ] 

Mark Chu-Carroll commented on AURORA-123:
-----------------------------------------

By default,  the open file limit in OXS bash is set to just 256. Vagrant needs a higher setting. Running with "ulimit -n 512" works without error.


> Building/provisioning vagrant VMs fails on OSX Mavericks.=
> ----------------------------------------------------------
>
>                 Key: AURORA-123
>                 URL: https://issues.apache.org/jira/browse/AURORA-123
>             Project: Aurora
>          Issue Type: Bug
>          Components: Deploy, Testing
>         Environment: OS/X mavericks
>            Reporter: Mark Chu-Carroll
>         Attachments: vagrant-trans.txt
>
>
> After upgrading my laptop to OSX mavericks, the process of creating the virtual machines fails. (I'll attach the error transcript to this message.) Creating the machines doesn't finish because of this error.
> Running "vagrant destroy" to get rid of the VMs and trying over produces exactly the same failure.
> Running "vagrant up" again after the failure (but without destroying the VMs) produces no error. But once the machine comes up, there's no scheduler running on it. It does all of the configuration, including a generated clusters.json config in /etc/aurora.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)