-
Notifications
You must be signed in to change notification settings - Fork 188
Can't finish syncdb #68
Comments
let me check |
Are you using MySQL or MariaDB? |
It's mariadb |
That's where the problem lies. I had similar problems when using MariaDB and ended up chucking it and going back to MySQL via the community repos. I simply forgot to file a ticket about it while having the problem, but I can confirm it's related to the interactiong with MariaDB. |
I found it was a permissions issue. I had created the openduty user before the database. all I had to do was grant the user permissions on the DB. I chose to just give them full permissions as this is my initial test. GRANT ALL ON openduty.* TO 'openduty'@'%'; |
You can also do the following:
|
since @sofixa helped with this one i'm closing this one. |
Hi @deathowl, if ! mysql -h $DATABASES_DEFAULT_HOST -u $DATABASES_DEFAULT_USER -p$DATABASES_DEFAULT_PASSWORD -e 'SHOW DATABASES;' | grep -q $DATABASES_DEFAULT_NAME; then
mysql -h $DATABASES_DEFAULT_HOST -u $DATABASES_DEFAULT_USER -p$DATABASES_DEFAULT_PASSWORD -e "CREATE DATABASE $DATABASES_DEFAULT_NAME;"
export DJANGO_SETTINGS_MODULE=openduty.settings_docker
python manage.py syncdb
python manage.py migrate
python manage.py collectstatic --noinput
fi |
Same here. Manually tried with all solutions in the thread, both with MySQL and MariaDB and always getting foreign key errors. In both cases I've manually granted ALL privileges to OD MySQL user, just slightly different error texts:
With MariaDB 10.x:
|
It's the same with me. |
@deathowl : Any tips? Anything else needed from us to help diagnose where is the problem? |
I got the same error, but changed the order to this instead: got through without errors |
guys, please help me out. Stuck on this:
File "/home/openduty/openduty/env/lib/python2.7/site-packages/django/db/migrations/loader.py", line 191, in build_graph
|
The installation docs should be updated |
Did nothing, just created mysql db, user, started using "getting started" instructions and it fails:
The text was updated successfully, but these errors were encountered: