[ERROR] /opt/stack/devstack/lib/glance:364 g-api did not start
The above error was given during the installation of Devstack on a single VM. I have searched this and I am unable to find the fix. Please help.
Hello,
I also got same problem
2018-02-08 09:12:23.017 | ++:: curl -g -k --noproxy '' -s -o /dev/null -w '%{http_code}' http://127.0.0.1/image 2018-02-08 09:12:23.030 | +:: [[ 503 == 503 ]] 2018-02-08 09:12:23.033 | +:: sleep 1 2018-02-08 09:12:24.040 | ++:: curl -g -k --noproxy '' -s -o /dev/null -w '%{http_code}' http://127.0.0.1/image 2018-02-08 09:12:24.054 | +:: [[ 503 == 503 ]] 2018-02-08 09:12:24.058 | +:: sleep 1 2018-02-08 09:12:24.684 | [Call Trace] 2018-02-08 09:12:24.684 | ./stack.sh:1236:start_glance 2018-02-08 09:12:24.685 | /opt/stack/devstack/lib/glance:364:die 2018-02-08 09:12:24.688 | [ERROR] /opt/stack/devstack/lib/glance:364 g-api did not start 2018-02-08 09:12:25.693 | Error on exit
Does anyone have idea?
Thanks!
I have the same issue. No logs in journalctl -u devstack@g-api.service but when I run manually command (/usr/local/bin/uwsgi --procname-prefix keystone --ini /etc/keystone/keystone-uwsgi-public.ini) which should be executed by systemd service, glance is starts succesfully.
Ok, I found out that when I started glance uwsgi under stack user, I got perrmission denied exception:
ERROR glance IOError: [Errno 13] Permission denied: '/opt/stack/data/glance/locks/image_cache_db_init'
I changed the owner on a directory to stack:stack and it works.
I'm getting the same results as well. RHEL 7.4 and latest devstack.
[Call Trace] ./stack.sh:1240:start_glance /opt/stack/devstack/lib/glance:352:die [ERROR] /opt/stack/devstack/lib/glance:352 g-api did not start Error on exit World dumping... see /opt/stack/logs/worlddump-2018-05-04-205711.txt for details [stack@devstacktesting devstack]$
Asked: 2018-01-18 20:30:30 -0600
Seen: 1,709 times
Last updated: May 04 '18
364 is the line number in /opt/stack/devstack/lib/glance. Check the Glance API log to find out why it didn’t start. If your DevStack is a recent version,
journalctl -u devstack@g-api. Otherwise, probably /opt/stack/logs/g-api.log.There may also be clues in earlier DevStack installation messages.
+1 .. Seeing the same exception