Nope the keystone files are there, not links.
I do not see rejoin starting apache and when I do it manually it doesn't
listen on 5000, just 80
I've work around this problem by not using unstack anymore, just
restarting the specific services impacted by my change
On 15/10/14 03:02, Борис Боб
On Tue, Oct 14, 2014 at 9:02 PM, Борис Бобров wrote:
> Have a look at /etc/apache2/sites-available. For some reason
> keystone's .conf files is not linked to /etc/apache2/sites-enabled, so it
> doesn't go up when apache is restarted. Try creating symlink manually.
>
DevStack manages that symlink
В сообщении от Tuesday 14 of October 2014 21:14:52 Paul написал:
> Hi
>
> I'm using devstack and doing 'unstack.sh' to stop devstack then making
> code/config changes and doing 'rejoin_stack.sh' to restart it but it is
> not starting apache or keystone processes. I've tried restarting
> apache my
As a relatively new DevStack / OpenStack developer ... how would we guess
usual workflow? :)
(I did figure out the local.conf => nova.conf push. The Devstack unstack /
rejoin / clean is still slightly foggy.)
On Tue, Oct 14, 2014 at 6:31 PM, Dean Troyer wrote:
> On Tue, Oct 14, 2014 at 12:14
On Tue, Oct 14, 2014 at 12:14 PM, Paul Carlton wrote:
> I'm using devstack and doing 'unstack.sh' to stop devstack then making
> code/config changes and doing 'rejoin_stack.sh' to restart it but it is not
> starting apache or keystone processes. I've tried restarting apache myself
> before and a
Hi
I'm using devstack and doing 'unstack.sh' to stop devstack then making
code/config changes and doing 'rejoin_stack.sh' to restart it but it is
not starting apache or keystone processes. I've tried restarting apache
myself before and after rejoin but no joy.
I can fix this by doing 'stack
