keystone did not start

Bug #1210851 reported by geetha
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
devstack
Confirmed
Undecided
Unassigned

Bug Description

 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/ke'stone/logging.conf -d --debug || touch "/opt/stack/status/stack/key.failure"
+ echo 'Waiting for keystone to start...'
Waiting for keystone to start...
+ timeout 60 sh -c 'while ! http_proxy= curl -s http://10.0.2.15:5000/v2.0/ >/dev/null; do sleep 1; done'
+ die 316 'keystone did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:880:start_keystone
/devstack/lib/keystone:316:die
[ERROR] /home/devstack/lib/keystone:316 keystone did not start

Thierry Carrez (ttx)
information type: Private Security → Public
Revision history for this message
Satya Sanjibani Routray (satroutr) wrote :

++ echo -ne '\015'
+ NL=$'\r'
+ echo 'screen -t key bash'
"'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
+ [[ True = \T\r\u\e ]]
+ screen -S stack -X screen -t key
+ [[ -n '' ]]
+ sleep 1.5
++ echo -ne '\015'
+ NL=$'\r'
+ 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 || echo "key 'ailed to start" | tee "/opt/stack/status/stack/key.failure"
+ echo 'Waiting for keystone to start...'
Waiting for keystone to start...
+ timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s http://192.168.255.167:5000/v2.0/ >/dev/null; do sleep 1; done'
+ die 378 'keystone did not start'
+ local exitcode=0
+ set +o xtrace
[Call Trace]
./stack.sh:868:start_keystone
/home/satya/devstack/lib/keystone:378:die
[ERROR] /home/satya/devstack/lib/keystone:378 keystone did not start

Revision history for this message
shake.chen (shake-chen) wrote :

2013-11-20 19:06:14 + echo 'screen -t key bash'
2013-11-20 19:06:14 + echo 'stuff "cd /opt/stack/keystone && /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /et"'keystone/logging.conf -d --debug
2013-11-20 19:06:14 + [[ True = \T\r\u\e ]]
2013-11-20 19:06:14 + screen -S stack -X screen -t key
2013-11-20 19:06:14 + [[ -n /opt/stack/logs ]]
2013-11-20 19:06:14 + screen -S stack -p key -X logfile /opt/stack/logs/screen-key.2013-11-20-190457.log
2013-11-20 19:06:14 + screen -S stack -p key -X log on
2013-11-20 19:06:14 + ln -sf /opt/stack/logs/screen-key.2013-11-20-190457.log /opt/stack/logs/screen-key.log
2013-11-20 19:06:14 + sleep 1.5
2013-11-20 19:06:15 ++ echo -ne '\015'
2013-11-20 19:06:15 + NL=$'\r'
2013-11-20 19:06:15 + screen -S stack -p key -X stuff 'cd /opt/stack/keystone && /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.c'nf --log-config /etc/keystone/logging.conf -d --debug || echo "key failed to start" | tee "/opt/stack/status/stack/key.failure"
2013-11-20 19:06:15 + echo 'Waiting for keystone to start...'
2013-11-20 19:06:15 Waiting for keystone to start...
2013-11-20 19:06:15 + timeout 60 sh -c 'while ! curl --noproxy '\''*'\'' -s http://10.1.199.132:5000/v2.0/ >/dev/null; do sleep 1; done'
2013-11-20 19:07:15 + die 378 'keystone did not start'
2013-11-20 19:07:15 + local exitcode=0
2013-11-20 19:07:15 + set +o xtrace
2013-11-20 19:07:15 [Call Trace]
[stack@g132 devstack]$ 2013-11-20 19:07:15 ./stack.sh:840:start_keystone
2013-11-20 19:07:15 /home/devstack/lib/keystone:378:die
2013-11-20 19:07:15 [ERROR] /home/devstack/lib/keystone:378 keystone did not start

Revision history for this message
Max Grishkin (grishkin) wrote :

Please try to start keystone manually after failure:
 cd /opt/stack/keystone && /opt/stack/keystone/bin/keystone-all --config-file /etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d --debug || echo "key failed to 'tart" | tee "/opt/stack/status/stack/key.failure"
Then paste error message from keystone here.

Changed in devstack:
status: New → Incomplete
Revision history for this message
Max Grishkin (grishkin) wrote :

Looks like %(admin_port) and %(public_port) in keystone.conf are not expanded:
admin_endpoint = http://10.1.2.44:%(admin_port)s/
public_endpoint = http://10.1.2.44:%(public_port)s/

Changed in devstack:
status: Incomplete → Confirmed
Revision history for this message
Max Grishkin (grishkin) wrote :

Workaround: set SERVICE_HOST=127.0.0.1 in localrc.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.