Do not overwrite the /etc/init/keystone.conf. Use the above file to create a file in /etc/keystone/ called keystone.conf. On Oct 26, 2011 8:22 PM, "Neil Andrews" < question173861@answers.launchpad.net > wrote:

Your question #173861 on Keystone changed: https://answers.launchpad.net/keystone/+question/173861 (https://answers.launchpad.net/keyston...)

Neil Andrews posted a new comment: I'm really confused with the solution that has been provided above, to begin with after following the steps before the comments the error I get afterwards is. To clarify I'm running on Ubuntu 11.04.

ERROR: Error loading config /etc/keystone/keystone.conf: File contains no section headers. file: /etc/keystone/keystone.conf, line: 1 'how more verbose log output (sets INFO log level output)\n'

As for the following comment guide, it is mentioned that /etc/init/keystone.conf is appended to or overwritten by that given in the github. I have tried both and still receive the above error. Upon deleting /etc/keystone/keystone.conf I get the following error. (the text is different depending on the append or overwrite, but I don't think that matters)

ERROR: Error loading config /etc/init/keystone.conf: File contains no section headers. file: /etc/init/keystone.conf, line: 1 'how more verbose log output (sets INFO log level output)\n'

Can someone clarify or give me some insight on something I'm missing? Thanks

---

You received this question notification because you asked the question.

I had to alter the /etc/init/keystone file from

su -c"...

to

su - -c"...

so that keystone knew that keystone.db was in /var/lib/keystone. (Yes, I'm going to convert to mysql tomorrow,but...)

That mostly worked. I can start keystone manually, but it will not run as a service.