Hello,

I would suggest use

(*shell.inline = 'nohup /bin/bash
/applications/activator-1.2.10-minimal/activator run > /path/for/log.log &'*
)

I think the issue is your process doesn't finish or goes to background
automatically.

If you want  something more elegant, you can try to get a tmux console,
attach/run the command in that console and leave/dettach

then later you could do  vagrant ssh, then tmux a


hope this helps
Alvaro.


On Fri, Sep 26, 2014 at 8:30 AM, Nenad Samardzic <[email protected]>
wrote:

> Hi all,
>
> I am building a Play2 Scala application which I run using typesafe
> activator tool. Currently I am trying to build generic dev environment
> using Vagrant and chef.
> The process goes well (environment is built and parameters are set) until
> the point where I need to run the activator script.
> The moment  the server is up and app is started Vagrant stops my process,
> thus killing my app.
>
> To try to explain this by giving more details:
> Once my environment is ready and I need to run activator
> 1) ...if I ssh into the box and run '*activator run*' the app will start
> in the box and on my host machine I'll be able to hit
> *xxx.xxx.xxx.xxx:9000* that I have defined in my Vagrantfile. App works
> just fine. The response I get in the virtual box command line is:
> ...
>
> *--- (Running the application from SBT, auto-reloading is enabled) ---*
>
> *[info] play - Listening for HTTP on /0:0:0:0:0:0:0:0:9000*
> *(Server started, use Ctrl+D to stop and go back to the console...)*
>
> 2) ...if I run it from Vagrantfile (*shell.inline = '/bin/bash
> /applications/activator-1.2.10-minimal/activator run'*) the same thing
> happens, with one change - my process is killed. The response is as follows:
> ...
> *==> default: --- (Running the application from SBT, auto-reloading is
> enabled) ---*
> *==> default: [info] play - Listening for HTTP on /0:0:0:0:0:0:0:0:9000*
> *==> default: (Server started, use Ctrl+D to stop and go back to the
> console...)*
> *==> default: [success] Total time: 139 s, completed Sep 25, 2014 7:49:59
> PM*
>
> In the background activator is running sbt...this is what gets executed:
> *exec java -Dactivator.home=/applications/activator-1.2.10-minimal
> -Xms1024m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=256m -jar
> /applications/activator-1.2.10-minimal/activator-launch-1.2.10.jar run*
>
> I've tried to keep shell process alive, but that doesn't prevent Vagrant
> from closing my sbt process.
>
> Does anyone have experience with a similar problem or an idea how to solve
> this issue?
>
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to