Closed darylrobbins closed 9 years ago
Sorry for the trouble.
I think I might know what's going on here. Do you have a newer version of the gatekeeper checked out in workspace/gatekeeper
from master? But then I assume you haven't updated the workspace/router
project?
If that's the case, then I think that explains it: there have been changes on master to both gatekeeper and router that are sort of tied together. So in your current development environment, I think you have a new version of the gatekeeper project, but not the corresponding updated version of the router project. Normally, you'd update the router project to master too, and then things would work, but in this case, you probably don't want to do that. The master version of the "router" project is dependent on new server-side package updates that will be part of the v0.7 package release, but that's still not out yet. So if you update the router project to master, then things will unfortunately be broken in a different way until we get the v0.7 packages out.
Here are probably the two easiest options:
workspace/router/templates/etc/supervisord.conf.hbs
(in this file's case, comments are semi-colon prefixed lines, so the first line would look like ; [program:router-log-listener]
)Let me know if either of those don't work for you, though.
And apologies for making master a bit messy to work with while we're in this limbo waiting for the v0.7 packages to be released. I'll try to get those released this weekend, which should also solve this problem, since then you'll be able to update the router project to master. The changes in master and v0.7 will actually help prevent this type of situation in the future, since the gatekeeper and router are less reliant on each other moving forward. We'll also take this as a good lesson not to merge things into master before we have packaged releases ready to go.
To get the environment working:
Maybe creating a release branch during the release process would help avoid this kind of scenario in the future?
The v0.9 includes an updated vagrant box, which I think should help alleviate these type of issues moving forward.
The development environment was working less than a week ago but I am now getting an error when trying to run
vagrant up
.Output from
vagrant up
:Here is /opt/api-umbrella/var/log/supervisor/router-log-listener.log: