Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL-DB not starting correctly #2

Open
tobiassoltermann opened this issue May 12, 2015 · 8 comments
Open

MySQL-DB not starting correctly #2

tobiassoltermann opened this issue May 12, 2015 · 8 comments

Comments

@tobiassoltermann
Copy link

Like stated in the readme, I ran

docker build -t zuhkov/paperwork .

and then

docker run -d -v /your-config-location:/config -p 8888:80 zuhkov/paperwork

I cannot create a new user as the database seems to fail starting. Here's the log excerpt:

root@server01:/tmp/docker-containers/paperwork# docker logs 642d
*** Running /etc/my_init.d/firstrun.sh...
Loading PHP config from default.
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 19
Initializing Data Directory.
Installation complete.
May 12 07:36:20 642d050d7de8 syslog-ng[31]: syslog-ng starting up; version='3.5.3'
May 12 07:36:23 642d050d7de8 mysqld_safe: Starting mysqld daemon with databases from /config/databases
May 12 07:36:23 642d050d7de8 mysqld: 150512  7:36:23 [Note] /usr/sbin/mysqld (mysqld 5.5.43-MariaDB-1~trusty-log) starting as process 739 ...
May 12 07:36:23 642d050d7de8 mysqld: 150512  7:36:23 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.index' not found (Errcode: 13)

May 12 07:36:23 642d050d7de8 mysqld: 150512  7:36:23 [ERROR] Aborting
May 12 07:36:23 642d050d7de8 mysqld:
May 12 07:36:23 642d050d7de8 mysqld: 150512  7:36:23 [Note] /usr/sbin/mysqld: Shutdown complete
May 12 07:36:23 642d050d7de8 mysqld:
May 12 07:36:23 642d050d7de8 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

I actually verified, the file is there.

@luclu
Copy link

luclu commented Jun 3, 2015

+1!

@nmaas87
Copy link

nmaas87 commented Jan 8, 2016

+1

@nmaas87 nmaas87 mentioned this issue Jan 8, 2016
@EnMod
Copy link

EnMod commented Feb 19, 2016

+1 same here, it's preventing me from being able to log in. Any ideas @pmosbach ?

@panypopo
Copy link

I solved this issue by:
docker run -d -v /your-config-location:/config -v /your-mysql-log-location:/var/log/mysql -p 8888:80 zuhkov/paperwork

@downforce
Copy link

I also used @panypopo's solution, however, I had to start the container, then restart it to get the DB to start properly.

@csphoenix1
Copy link

csphoenix1 commented Nov 16, 2017

Hi all!
It's look like MariaDB locks the /var/log/mysql directory, and users other than root can't write inside.

You can try with this Dockerfile by following the instruction bellow.
It made my tests like that. So it's not a perfect demo, but it's did the trick :)

Dockerfile.txt

@csphoenix1
Copy link

And this is my workaround (compare with the original Dockerfile).

Dockerfile.txt

@subin8848
Copy link

I am still having issue with it. The following is the error I received:

Starting MariaDB...
190708 16:32:53 mysqld_safe Logging to '/config/databases/af6e28e0452a.err'.
190708 16:32:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
190708 16:32:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Previously, I received this error:
Starting MariaDB...
190708 16:32:53 mysqld_safe Logging to '/config/databases/af6e28e0452a.err'.
190708 16:32:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
190708 16:32:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

But, somehow the error message seems changed strangely!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants