ERPNext Foundation ERPNext Cloud User Manual Blog Discuss Frappé* Donate

Failed to start MariaDB 10.2.13 database server

bug

#1

Error
[Failed] Failed to start MariaDB 10.2.13 database server

on same time "Internal Server Error "
and bench-update "error 111 "



#2

Try ths? [solved] MariaDB 10.1 to MariaDB 10.2 upgrade crash


#3

@clarkej not worked :worried: that solution
the problems its coming after 2 , 3 day of working on erpnext
and working on localhost


#4

ok so if your database starts, then that is not the problem!


#5

I’ve got the same problem . It continuously crashes.


#6

The first step is to define the problem - what crashes how?


#7

I’ve used virtual production Image on multiple PCs. After start to use program, allways screen get faded gray color. I cannot able to click any button menu etc… It doesn’t happen in certain time or page. It look likes random. If I reboot the machine I cannot reach main page in local(Internal Server Error ). At booting “Failed to start MariaDB 10.2.13 database server” error occurs as smsars. I have tried to reboot bench, start bench , increase virtual machines ram… notting worked .
Probably it happens because of Turkish characters like (i,ü,ş, ç)

Thanks by the way.


#8

Thank you Tunc_KANAL

Some questions -

You allocate at least 1Gb for the VM image to run?

“Probably it happens because of Turkish characters like (i,ü,ş, ç)”

Why do you suspect the above may be the problem, what evidence have you?

For the database to not start sometimes is odd - what do you do to fix this for it once again to start?

edit: In addition, what causes your database to shutdown?

For clues to the problem inspect the logs for errors - please post tracebacks you find here.

The logs can be found here:

/var/lib/mysql/mysql-error.log
frappe@ubuntu:~/frappe-bench$ find . -name ‘*.log’ | xargs ls -alt
-rw-rw-r-- 1 frappe frappe 1575 Apr 9 10:00 ./logs/auto_update_log.log
-rw-r–r-- 1 root root 3109342 Mar 25 09:53 ./logs/worker.error.log
-rw-r–r-- 1 root root 6274 Mar 25 09:53 ./logs/web.error.log
-rw-r–r-- 1 root root 27441 Mar 25 09:53 ./logs/node-socketio.log
-rw-r–r-- 1 root root 16390 Mar 25 09:53 ./logs/redis-socketio.log
-rw-r–r-- 1 root root 16390 Mar 25 09:53 ./logs/redis-cache.log
-rw-r–r-- 1 root root 16390 Mar 25 09:53 ./logs/redis-queue.log
-rw-r–r-- 1 root root 270 Mar 22 20:29 ./logs/web.log
-rw-r–r-- 1 frappe frappe 8534 Mar 21 20:46 ./logs/bench.log
-rw-r–r-- 1 frappe frappe 20117 Mar 21 18:15 ./logs/frappe.log
-rw-r–r-- 1 root root 65773 Mar 21 17:16 ./logs/schedule.error.log
-rw-r–r-- 1 root root 65325 Mar 21 17:04 ./logs/node-socketio.error.log
-rw-r–r-- 1 root root 8192 Mar 21 15:11 ./logs/schedule.log
-rw-r–r-- 1 root root 0 Mar 20 17:23 ./logs/worker.log
-rw-r–r-- 1 root root 0 Mar 20 17:23 ./logs/redis-socketio.error.log
-rw-r–r-- 1 root root 0 Mar 20 17:23 ./logs/redis-cache.error.log
-rw-r–r-- 1 root root 0 Mar 20 17:23 ./logs/redis-queue.error.log


Mysql fail to load
#9

I’m currently trying out ERPNext Production in a virtual box environment (to be deployed in a garment manufacturing entity) , everything works fine for a day or two and I get error while booting the virtual machine “Failed to start MariaDB 10.2.14 database server”

Opening Localhost:8080 in browser gives an “Internal Server error”

Trying to update frappe bench results in “Errno111”

Tried the following fix without any success
" [solved] MariaDB 10.1 to MariaDB 10.2 upgrade crash "

This happened to me on three instances of my trial.

Is there any updated solution for the problem?

Regards
Vishnu


#10

Unfortunately still no idea what the problem is -

Please if you would read and respond to the previous post and request - to check your logs and post any errors you find - that would help identify the nature of the problem

thanks


#11

May this error because of the shut-down of the VM.

Be careful how you obtain to switch off your system.

You should try not to hibernate the system at all if you use SSD drive.
It can cause read write issues then it kills the database.

I had one time I had to restore the system from backup.

You should backup regularly and let switch off the VM before you switch off the computer.

Hope this helps.


#12

Thanks excellent points @krnkris - indeed be aware an improper shutdown may trash the database.


#13

FWIW this may help

Apparently the cause of the problem was mysqld was not shut down properly?


#14

mysqld --tc-heuristic-recover=ROLLBACK

service mysql start

done


#15