<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/05/2013 08:00 AM, Antonio Tirri
wrote:<br>
</div>
<blockquote
cite="mid:CABumyWpgQwb2rueig6Q3qrcsEEnVBr25OiK_YV48SmKTmKbCCg@mail.gmail.com"
type="cite">Hi all,<br>
actually i'm trying to install OpenStack through DevStack script.
Unfortunately the installation is not successful because the
keystone service doesn't start. <br>
<br>
This is the log of the script:<br>
<br>
2013-02-05 13:19:05 + SCREEN_NAME=stack<br>
2013-02-05 13:19:05 + SCREENRC=/opt/stack/devstack/stack-screenrc<br>
2013-02-05 13:19:05 + [[ ! -e /opt/stack/devstack/stack-screenrc
]]<br>
2013-02-05 13:19:05 + grep key /opt/stack/devstack/stack-screenrc<br>
2013-02-05 13:19:05 ++ echo -ne '\015'<br>
2013-02-05 13:19:05 + NL=$'\r'<br>
2013-02-05 13:19:05 + echo 'screen -t key bash'<br>
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<br>
"'<br>
2013-02-05 13:19:05 + screen -S stack -X screen -t key<br>
2013-02-05 13:19:05 + sleep 1.5<br>
2013-02-05 13:19:06 + [[ -n '' ]]<br>
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"<br>
'<br>
2013-02-05 13:19:06 + echo 'Waiting for keystone to start...'<br>
2013-02-05 13:19:06 Waiting for keystone to start...<br>
2013-02-05 13:19:06 + timeout 60 sh -c 'while ! http_proxy= curl
-s <a moz-do-not-send="true"
href="http://163.162.24.167:5000/v2.0/">http://163.162.24.167:5000/v2.0/</a>
>/dev/null; do sleep 1; done'<br>
]0;stack@openstack-controller:
~/devstackstack@openstack-controller:~/devstack$ 2013-02-05
13:20:06 + echo 'keystone did not start'<br>
2013-02-05 13:20:06 keystone did not start<br>
2013-02-05 13:20:06 + exit 1<br>
2013-02-05 13:20:06 + clean<br>
2013-02-05 13:20:06 + local r=1<br>
2013-02-05 13:20:06 ++ jobs -p<br>
2013-02-05 13:20:06 + kill<br>
2013-02-05 13:20:06 + exit 1<br>
<br>
How this problem can be solved?<br>
<br>
Antonio<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
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"<br>
<br>
<br>
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:<br>
<br>
cd /opt/stack/keystone<br>
<br>
/opt/stack/keystone/bin/keystone-all --config-file
/etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf
-d --debug<br>
<br>
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<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>