Error connected to database

[puckel]

Error connected to database

[puckel]

I've same warnings but everything works. Not sure yet, but I think it's caused by airflow who doesn't call mysql_close before exiting (I tried w/ airflow backfill command)

[rothnic]

Have you tried this with boot2docker? The backfill seems to run, but the other example tasks that are in there don't seem to do anything for me. This is what I see printed out during the tutorial:

worker_1    | Logging into: /usr/local/airflow/logs/tutorial/templated/2015-05-27T00:00:00
worker_1    | Logging into: /usr/local/airflow/logs/tutorial/templated/2015-05-22T00:00:00
worker_1    | Logging into: /usr/local/airflow/logs/tutorial/sleep/2015-06-01T00:00:00
worker_1    | Logging into: /usr/local/airflow/logs/tutorial/templated/2015-05-31T00:00:00
mariadb_1   | 150731  5:02:55 [Warning] Aborted connection 178 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:55 [Warning] Aborted connection 181 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:55 [Warning] Aborted connection 168 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:55 [Warning] Aborted connection 175 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:55 [Warning] IP address '172.17.0.4' could not be resolved: Temporary failure in name resolution
mariadb_1   | 150731  5:02:55 [Warning] Aborted connection 199 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
worker_1    | Logging into: /usr/local/airflow/logs/tutorial/sleep/2015-05-28T00:00:00
worker_1    | Logging into: /usr/local/airflow/logs/tutorial/templated/2015-05-23T00:00:00
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 174 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 182 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 192 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 194 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 196 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)
mariadb_1   | 150731  5:02:56 [Warning] Aborted connection 197 to db: 'airflow' user: 'airflow' host: '172.17.0.4' (Unknown error)

[puckel]

I try with Boot2Docker-cli version: v1.7.0. Same warnings, but the backfilll works fine 👍

2015-07-31 13:25:14,011 INFO - [backfill progress] waiting: 0 | succeeded: 6 | kicked_off: 6 | failed: 0 | skipped: 0
2015-07-31 13:25:14,011 INFO - All done. Exiting.

[rothnic]

Right, the backfill works fine for me. When clicking run on the shell command task, does it do anything for you? I see the http get, then nothing else happens.

[rothnic]

This is still an issue. While you can kick off the backfill, any of the scheduling that uses the database likely won't work correctly. The problem is the database my.cnf file in that docker image, which isn't compatible with allowing connections from the docker host (172....).

A quick fix for me was to replace with the tutum/mysql image which does take care of this. The name of the database in the docker-compose.yml would need to be changed, but this worked:

mariadb:
    image: tutum/mysql
    restart: always
    ports:
        - "3306:3306"
    environment:
        - MYSQL_USER=airflow
        - MYSQL_PASS=airflow
        - ON_CREATE_DB=airflow

[puckel]

Thanks for your feedback Nick. I pushed the changes.