Open Stack

Hi Adam,
thanks for your answer.

First of all, the full log of my script is here
www.forumaltavilla.it/joomla/Documenti/log_devstack.txt

It seems that there are some problems in managing user permissions. Even if
I included the stack user in /etc/sudoers adding the following line

stack ALL=(ALL) NOPASSWD: ALL

Moreover, i can't execute the script as root because, by default, it switch
to the "stack" user.

however, the output of the command
/opt/stack/keystone/bin/keystone-all --config-file
/etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
--debug

 is

stack at openstack-controller:~/keystone$ /opt/stack/keystone/bin/keystone-all
--config-file /etc/keystone/keystone.conf --log-config
/etc/keystone/logging.conf -d --debug
Traceback (most recent call last):
  File "/opt/stack/keystone/bin/keystone-all", line 82, in <module>
    config.setup_logging(CONF)
  File "/opt/stack/keystone/keystone/config.py", line 41, in setup_logging
    logging.config.fileConfig(conf.log_config)
  File "/usr/lib/python2.7/logging/config.py", line 78, in fileConfig
    handlers = _install_handlers(cp, formatters)
  File "/usr/lib/python2.7/logging/config.py", line 156, in
_install_handlers
    h = klass(*args)
  File "/usr/lib/python2.7/logging/__init__.py", line 897, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python2.7/logging/__init__.py", line 916, in _open
    stream = open(self.baseFilename, self.mode)
IOError: [Errno 13] Permission denied: '/opt/stack/keystone/keystone.log'

while if i launch that command with sudo, it seems that it runs.

Thank you,
Antonio

On 5 February 2013 17:04, Adam Young <ayoung at redhat.com> wrote:

>  On 02/05/2013 08:00 AM, Antonio Tirri wrote:
>
> Hi all,
> actually i'm trying to install OpenStack through DevStack script.
> Unfortunately the installation is not successful because the keystone
> service doesn't start.
>
> This is the log of the script:
>
> 2013-02-05 13:19:05 + SCREEN_NAME=stack
> 2013-02-05 13:19:05 + SCREENRC=/opt/stack/devstack/stack-screenrc
> 2013-02-05 13:19:05 + [[ ! -e /opt/stack/devstack/stack-screenrc ]]
> 2013-02-05 13:19:05 + grep key /opt/stack/devstack/stack-screenrc
> 2013-02-05 13:19:05 ++ echo -ne '\015'
> 2013-02-05 13:19:05 + NL=$'\r'
> 2013-02-05 13:19:05 + echo 'screen -t key bash'
> 2013-02-05 13:19:05 + echo 'stuff "cd /opt/stack/keystone &&
> /opt/stack/keystone/bin/keystone-all --config-file
> /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
> --debug
> "'
> 2013-02-05 13:19:05 + screen -S stack -X screen -t key
> 2013-02-05 13:19:05 + sleep 1.5
> 2013-02-05 13:19:06 + [[ -n '' ]]
> 2013-02-05 13:19:06 + screen -S stack -p key -X stuff 'cd
> /opt/stack/keystone && /opt/stack/keystone/bin/keystone-all --config-file
> /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
> --debug || touch "/opt/stack/status/stack/key.failure"
> '
> 2013-02-05 13:19:06 + echo 'Waiting for keystone to start...'
> 2013-02-05 13:19:06 Waiting for keystone to start...
> 2013-02-05 13:19:06 + timeout 60 sh -c 'while ! http_proxy= curl -s
> http://163.162.24.167:5000/v2.0/ >/dev/null; do sleep 1; done'
> ]0;stack at openstack-controller: ~/devstack stack at openstack-controller:~/devstack$
> 2013-02-05 13:20:06 + echo 'keystone did not start'
> 2013-02-05 13:20:06 keystone did not start
> 2013-02-05 13:20:06 + exit 1
> 2013-02-05 13:20:06 + clean
> 2013-02-05 13:20:06 + local r=1
> 2013-02-05 13:20:06 ++ jobs -p
> 2013-02-05 13:20:06 + kill
> 2013-02-05 13:20:06 + exit 1
>
> How this problem can be solved?
>
> Antonio
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>  screen -S stack -p key -X stuff 'cd /opt/stack/keystone &&
> /opt/stack/keystone/bin/keystone-all --config-file
> /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
> --debug || touch "/opt/stack/status/stack/key.failure"
>
>
> Is the command that starts keystone.  From the above, it not clear why it
> is failing.  You should be able to run it interactively with:
>
> cd /opt/stack/keystone
>
>
> /opt/stack/keystone/bin/keystone-all --config-file
> /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
> --debug
>
> And get more output.  If it swallows all the output, look in
> /etc/keystone/logging.conf to see what it is set at.  It might be sending
> it to a log file, such as /var/log/keystone
>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130205/751ff360/attachment.html>