Hi,
On 2019-05-02 17:47, Goswin von Brederlow wrote:
Hi,
I can't reproduce this error with the same settings so it doesn't seem to be related to the choices you made in the installer. I'm thinking that something odd must happen before that causing the error.
Race conditions are difficult to reproduce. In our case it could be caused by stealing CPU time from parallel threads in sqlalchemy code by other users cloud VM's. Quick search on internet found this
https://stackoverflow.com/questions/11900553/sqlalchemy-table-already-exists
and it suggest to use checkfirst=True. I'll try to test with it, if I'll find the way how to change schema.py (I'm not good python developer).
Regards, Rolandas
Please capture the whole output of qlustar-initial-config using
qlustar-initial-config 2>&1 | tee log
and attach that. Maybe there is some error that scrolls by too fast so you missed it.
Regards, Goswin von Brederlow _______________________________________________ Qlustar-General mailing list -- qlustar-general@qlustar.org To unsubscribe send an email to qlustar-general-leave@qlustar.org