Closed
Bug 1246634
Opened 8 years ago
Closed 8 years ago
Error building bmoweb image
Categories
(MozReview Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcote, Assigned: gps)
Details
Attachments
(2 files)
I am currently unable to build the bmoweb image using docker 1.8.1. It fails with File "/Users/mcote/projects/version-control-tools/testing/vcttesting/docker_mach_commands.py", line 90, in build_all self.d.build_all_images(verbose=True) File "/Users/mcote/projects/version-control-tools/testing/vcttesting/docker.py", line 1236, in build_all_images bmo_result = f_bmo.result() if bmo else None File "/Users/mcote/projects/version-control-tools/venv/lib/python2.7/site-packages/concurrent/futures/_base.py", line 400, in result return self.__get_result() File "/Users/mcote/projects/version-control-tools/venv/lib/python2.7/site-packages/concurrent/futures/_base.py", line 359, in __get_result reraise(self._exception, self._traceback) File "/Users/mcote/projects/version-control-tools/venv/lib/python2.7/site-packages/concurrent/futures/_compat.py", line 107, in reraise exec('raise exc_type, exc_value, traceback', {}, locals_) File "/Users/mcote/projects/version-control-tools/venv/lib/python2.7/site-packages/concurrent/futures/thread.py", line 61, in run result = self.fn(*self.args, **self.kwargs) File "/Users/mcote/projects/version-control-tools/testing/vcttesting/docker.py", line 685, in build_bmo bmoweb_bootstrap = self._bootstrap_bmo(bmo_images['bmoweb']) File "/Users/mcote/projects/version-control-tools/testing/vcttesting/docker.py", line 788, in _bootstrap_bmo extra_check_fn=self._get_assert_container_running_fn(web_id)) File "/Users/mcote/projects/version-control-tools/testing/vcttesting/util.py", line 50, in wait_for_http extra_check_fn() File "/Users/mcote/projects/version-control-tools/testing/vcttesting/docker.py", line 1610, in assert_running raise Exception('Container stopped running: %s' % cid) The docker logs for that container are attached. One thing that stands out is that /var/run/mysqld/mysqld.sock does not exist. I verified that the directory belongs to the correct user.
Assignee | ||
Comment 1•8 years ago
|
||
From the container logs: <== Installed dependencies for .. Finishing Warning: Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Warning: Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Traceback (most recent call last): File "/bmoweb_entrypoint.py", line 166, in <module> cc(mysql_args + ['-e', 'CREATE DATABASE %s;' % db_name]) File "/usr/lib/python3.4/subprocess.py", line 557, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/usr/bin/mysql', '-uroot', '-ppassword', '-h', 'localhost', '-P', '3306', '-e', 'CREATE DATABASE bugs;']' returned non-zero exit status 1 So, it is complaining about connecting to a socket via /var/run/mysqld/mysqld.sock yet the command we invoke clearly passes "-h localhost -P 3306" to specify TCP connectivity. WTF.
Comment 2•8 years ago
|
||
After a complete rebuild of my environment, I'm now hitting this as well :(
Reporter | ||
Comment 3•8 years ago
|
||
This is the log from mysqld, which I pulled down after the container stopped.
Updated•8 years ago
|
Product: Developer Services → MozReview
Assignee | ||
Comment 4•8 years ago
|
||
https://hg.mozilla.org/hgcustom/version-control-tools/rev/8e7b9b7313633d975aff16ccd2cd9e92c0d87627 docker/bmoweb: use mysqld instead of mysqld_safe (bug 1246634) https://hg.mozilla.org/hgcustom/version-control-tools/rev/52aaee1436b7d4cf07bce337287600135396ea9c docker/bmoweb: start mysql after cpan module installation (bug 1246634) https://hg.mozilla.org/hgcustom/version-control-tools/rev/aca609c335630243fbac9d5540bb9aa99544e3de docker/bmoweb: explicitly wait on mysqld process to exit (bug 1246634) https://hg.mozilla.org/hgcustom/version-control-tools/rev/ae18684189a0f3c6045f5a8aa08ee579a8d715c2 docker/bmoweb: use socket for connecting to MySQL (bug 1246634)
Assignee | ||
Comment 5•8 years ago
|
||
I fixed a number of issues with mysql integration. Please pull down v-c-t and reopen the bug if the issue persists. The bmoweb image should rebuild automatically - no image deletion should be necessary.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → gps
You need to log in
before you can comment on or make changes to this bug.
Description
•