Comment 2 for bug 1870556

ahhh, that seems to be the trick. I had killed it with a dirty kill -15 and was restarting it manually from the commandline.

so restarting the service itself seems to work fine, it's just when I have killed it and try launchign it manually that I get that traceback, so I guess that's due to launching manually?