Skip to content
This repository has been archived by the owner on Jun 25, 2023. It is now read-only.

Landrush 1.1.2 failing to start - OSX 10.11, Vagrant 1.8.6 #288

Closed
fatmcgav opened this issue Oct 31, 2016 · 9 comments
Closed

Landrush 1.1.2 failing to start - OSX 10.11, Vagrant 1.8.6 #288

fatmcgav opened this issue Oct 31, 2016 · 9 comments
Milestone
v1.2.0

Comments

@fatmcgav
Copy link

Morning all

I've just updated Landrush to v1.1.2, from a pre 1.x version.
However Landrush is now failing to start, with no obvious cause.

gavinw@lt0772  ~/.vagrant.d/data  vagrant landrush start
gavinw@lt0772  ~/.vagrant.d/data  vagrant landrush status
Daemon status: unknown
/Users/gavinw/.vagrant.d/data/landrush/run/landrush.pid exists, but process is not running
Check log file: /Users/gavinw/.vagrant.d/data/landrush/log/landrush.log

But there's no 'landrush.log' for me to review :(

gavinw@lt0772  ~/.vagrant.d/data  tree landrush
landrush
└── run
└── landrush.pid

1 directory, 1 file

I've tried uninstalling and reinstalling Landrush with no change in behaviour.
Nothing of any use in system.log.

Any pointers on how to investigate?
@hferentschik
Copy link
Contributor

I think this might be related with your upgrade to Vagrant 1.8.6. I have seen a similar behavior as well. I need to investigate.

@fatmcgav
Copy link
Author

@hferentschik Cheers for the update. I'll try rolling Vagrant back to 1.8.5 and see if it resolves...

hferentschik added a commit to hferentschik/landrush that referenced this issue Oct 31, 2016
@hferentschik
Issue vagrant-landrush#288
b336392
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script
4f4e95a 
- Server.start needs now the machine passed
- Updating tests
- Making feature tests independnet from ~/.vagrant.d
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script
c0ebadd 
- Server.start needs now the machine passed
- Updating tests
- Making feature tests independnet from ~/.vagrant.d
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script
baa0db8 
- Server.start needs now the machine passed
- Updating tests
- Making feature tests independnet from ~/.vagrant.d
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Adding a setter for gems_dir
cad0fc3
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Adding a setter for gems_dir
affdd8d
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Adding a setter for gems_dir
e6ddc8e
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 1, 2016
@hferentschik
Issue vagrant-landrush#288 Adding a setter for gems_dir
3a69cd4
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Setting right gems dir for tests
6c13a39
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
42f7c79 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
c2c752b 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
2ec3cd0 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
d6cdd81 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
07d72e0 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 2, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
3a91df3 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 3, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
6bf9f6c 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
@hferentschik hferentschik mentioned this issue Nov 3, 2016
Merged
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 3, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
d81603a 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d

Issue vagrant-landrush#288 Adding a setter for gems_dir

Issue vagrant-landrush#288 Setting right gems dir for tests
hferentschik added a commit to hferentschik/landrush that referenced this issue Nov 3, 2016
@hferentschik
Issue vagrant-landrush#288 Starting the server via external script st…
d9f7e51 
…art_server.rb which gets gems path passed in order to configure load path

- Updating tests
- Making feature tests independnet from ~/.vagrant.d. Everything is now local to build/.vagrant.d
@hferentschik
Copy link
Contributor

@fatmcgav could you test a gem for me. You can download it from this AppVeyor CI build - https://ci.appveyor.com/project/hferentschik/landrush-3agrx/build/artifacts

You can install it via:

$ vagrant plugin install <path to gem>

For all I can tell, this works with Vagrant 1.8.6, but I'd like to get a second opinion.

@fatmcgav
Copy link
Author

fatmcgav commented Nov 3, 2016

@hferentschik sure, I'll give it a go tomorrow and report back...

@hferentschik
Copy link
Contributor

sure, I'll give it a go tomorrow and report back...

Awesome, thanks.

@fatmcgav
Copy link
Author

fatmcgav commented Nov 7, 2016

@hferentschik Sorry for the delay in testing...

Installed the 1.2.0.dev version this morning, and it starts correctly, local and VM DNS resolution works...

So big 👍 from me :)

Cheers

@hferentschik
Copy link
Contributor

@fatmcgav Thanks for testing. I'll merge it asap and try to cut a new release. There is one more outstanding issue I would like to get merged.

@hferentschik
Copy link
Contributor

Fixed via pull request #288

@hferentschik hferentschik added this to the v1.2.0 milestone Nov 17, 2016
@willrowe
Copy link

willrowe commented Mar 3, 2017 •
edited
Loading

I have Vagrant v1.8.6 installed on Mac OS X v10.11 and tried to update Landrush to v1.2.0 and got the same issue described at the beginning of this issue. I ended up having to rollback Landrush to v0.19.0 in order to get it to work correctly.
Can anyone confirm that v1.2.0 is actually working with Vagrant v1.8.6?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.2.0
Development

No branches or pull requests
3 participants
@hferentschik @fatmcgav @willrowe