search

jgmize / mozorg-env

Mozilla Public License 2.0
0 stars 0 forks source link

Error when running start-bedrock-mysql #1

Open sgarrity opened 9 years ago

sgarrity commented 9 years ago

When running bin/start-bedrock-mysql, I get the following error.

Note, this is with boot2docker on OS X.

$ bin/start-bedrock-mysql
+ trap 'trap - SIGTERM && kill -- -42450' SIGINT SIGTERM EXIT
+ BIN=bin
+ PROJECT=mozorg
+ BEDROCK_PATH=/app
+ '[' -e bin/../.env ']'
+ . bin/bedrock-init
++ '[' '!' ']'
++ BIN=bin
++ export BEDROCK=bin/../apache/bedrock/base/bedrock
++ BEDROCK=bin/../apache/bedrock/base/bedrock
++ '[' '!' -e bin/../apache/bedrock/base/bedrock ']'
++ '[' '!' -e bin/../apache/bedrock/base/bedrock/bedrock/settings/local.py ']'
+ . bin/b2d
++ BIN=bin
++ '[' -e bin/../.env ']'
+++ uname
++ '[' Darwin == Darwin ']'
++ '[' tcp://192.168.59.103:2376 ']'
+++ boot2docker ip
++ [[ tcp://192.168.59.103:2376 =~ 192\.168\.59\.103 ]]
++ export B2D=1
++ B2D=1
+ '[' 1 ']'
+ bin/b2d-fswatch-rsync bin/../apache/bedrock/base/bedrock
++ docker images
++ grep mozorg_bedrock
+ VOLUMES=/var/lib/docker/volumes
+ TARGET=/var/lib/docker/volumes/mozilla
+ boot2docker ssh 'sudo mkdir -p /var/lib/docker/volumes/mozilla && sudo chown -R docker /var/lib/docker/volumes && tce-load -wi rsync'
+ '[' '!' '' ']'
+ '[' '' == -b ']'
+ bin/compose pull bedrock
+ BIN=bin
+ PROJECT=mozorg
+ '[' -e bin/../.env ']'
+ '[' '!' ']'
+ COMPOSE_ARGS=(-p $PROJECT)
+ '[' pull == -b ']'
+ '[' pull == build ']'
+ [[ !  -p mozorg =~  -f  ]]
+ . bin/b2d
++ BIN=bin
++ '[' -e bin/../.env ']'
+++ uname
++ '[' Darwin == Darwin ']'
++ '[' tcp://192.168.59.103:2376 ']'
+++ boot2docker ip
++ [[ tcp://192.168.59.103:2376 =~ 192\.168\.59\.103 ]]
++ export B2D=1
++ B2D=1
+ '[' 1 ']'
+ '[' ']'
+ COMPOSE_ARGS+=(-f $BIN/../b2d.yml)
++ which docker-compose
+ '[' '!' /usr/local/bin/docker-compose ']'
+ COMPOSE_ARGS+=($@)
+ docker-compose -p mozorg -f bin/../b2d.yml pull bedrock
Downloading: rsync.tcz
Pulling mysql (mysql:5.6)...
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: rsync.tcz.md5.txt: No such file or directory
Error on rsync.tcz
error in run: exit status 1
Pulling bedrock (mozorg/bedrock:latest)...
++ docker images
++ grep mysql
++ awk '{print $2}'
++ grep 5.6
+ '[' '!' 5.6 ']'
+ sleep 10
+ bin/compose up mysql bedrock
+ BIN=bin
+ PROJECT=mozorg
+ '[' -e bin/../.env ']'
+ '[' '!' ']'
+ COMPOSE_ARGS=(-p $PROJECT)
+ '[' up == -b ']'
+ '[' up == build ']'
+ [[ !  -p mozorg =~  -f  ]]
+ . bin/b2d
++ BIN=bin
++ '[' -e bin/../.env ']'
+++ uname
++ '[' Darwin == Darwin ']'
++ '[' tcp://192.168.59.103:2376 ']'
+++ boot2docker ip
++ [[ tcp://192.168.59.103:2376 =~ 192\.168\.59\.103 ]]
++ export B2D=1
++ B2D=1
+ '[' 1 ']'
+ '[' ']'
+ COMPOSE_ARGS+=(-f $BIN/../b2d.yml)
++ which docker-compose
+ '[' '!' /usr/local/bin/docker-compose ']'
+ COMPOSE_ARGS+=($@)
+ docker-compose -p mozorg -f bin/../b2d.yml up mysql bedrock
Recreating mozorg_mysql_1...
Recreating mozorg_bedrock_1...
Attaching to mozorg_mysql_1, mozorg_bedrock_1
mysql_1   | 2015-06-30 13:54:51 0 [Note] mysqld (mysqld 5.6.25) starting as process 1 ...
mysql_1   | 2015-06-30 13:54:51 1 [Note] Plugin 'FEDERATED' is disabled.
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: The InnoDB memory heap is disabled
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Memory barrier is not used
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Compressed tables use zlib 1.2.7
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Using Linux native AIO
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Not using CPU crc32 instructions
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Completed initialization of buffer pool
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Highest supported file format is Barracuda.
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: 128 rollback segment(s) are active.
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: Waiting for purge to start
mysql_1   | 2015-06-30 13:54:51 1 [Note] InnoDB: 5.6.25 started; log sequence number 1626057
mysql_1   | 2015-06-30 13:54:51 1 [Note] Server hostname (bind-address): '*'; port: 3306
mysql_1   | 2015-06-30 13:54:51 1 [Note] IPv6 is available.
mysql_1   | 2015-06-30 13:54:51 1 [Note]   - '::' resolves to '::';
mysql_1   | 2015-06-30 13:54:51 1 [Note] Server socket created on IP: '::'.
mysql_1   | 2015-06-30 13:54:51 1 [Note] Event Scheduler: Loaded 0 events
mysql_1   | 2015-06-30 13:54:51 1 [Note] mysqld: ready for connections.
mysql_1   | Version: '5.6.25'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
bedrock_1 | python: can't open file 'manage.py': [Errno 2] No such file or directory
mozorg_bedrock_1 exited with code 2
Gracefully stopping... (press Ctrl+C again to force)
Stopping mozorg_mysql_1...
+ docker exec mozorg_mysql_1 bash -c 'echo "create database if not exists bedrock;" | mysql --password=$MYSQL_ROOT_PASSWORD'
FATA[0000] Error response from daemon: Container mozorg_mysql_1 is not running
+ trap - SIGTERM
+ kill -- -42450
Terminated: 15
jgmize commented 9 years ago

@sgarrity it looks like you were affected by the same issue as @jpetto -- the rsync package for boot2docker >= 1.7 is missing. I just pushed a workaround for the missing package; would you mind pulling the latest master and trying again?

sgarrity commented 9 years ago

@jgmize Hey, shouldn't you be in a :tent: or something?

I pulled the latest and tried again, but I think I'm still getting the error. It's possible that the issue is with my local boot2docker config. Here's the output I get now: https://gist.github.com/sgarrity/585aacdfeb73672ea69d

jgmize commented 9 years ago

@sgarrity based on https://gist.github.com/sgarrity/585aacdfeb73672ea69d#file-gistfile1-txt-L34 it looks like you were bit by https://github.com/boot2docker/boot2docker/issues/824 -- https://github.com/boot2docker/boot2docker/pull/960 should fix it when 1.7.1 is released in the next few days, but in the meantime you can try to work around the issue by deleting the VM image with the bad cert with boot2docker delete and then try running bin/start-bedrock-mysql again.

jgmize commented 9 years ago

@sgarrity I ran into https://github.com/boot2docker/boot2docker/issues/824 myself and found that just running boot2docker delete wasn't sufficent. I went through it enough times that I automated it with a new script: bin/b2d-rebuild-vm and did some refactoring and other fixes along the way. It's an annoying bug, and rebuilding the VM shouldn't be needed that often, and as soon as 1.7.1 is released (which should be soon) I'm going to recommend running a boot2docker update to get the fix.