[Mashiro]

Here is the isolated log piece of the failed MariaDB startup:

Code: (Select All)

Apr 22 21:16:25 vps570089 systemd[1]: Starting MariaDB 10.1.37 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has begun starting up.
Apr 22 21:16:26 vps570089 mysqld[7552]: 2019-04-22 21:16:26 140690769554816 [Note] /usr/sbin/mysqld (mysqld 10.1.37-MariaDB-0+deb9u1) starting as process 7552 ...
Apr 22 21:16:26 vps570089 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 21:16:26 vps570089 systemd[1]: Failed to start MariaDB 10.1.37 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Apr 22 21:16:26 vps570089 systemd[1]: mariadb.service: Unit entered failed state.
Apr 22 21:16:26 vps570089 systemd[1]: mariadb.service: Failed with result 'exit-code'.

I'm surprised. The log this time provides absolutely no proper information at all other than that the startup failed.

Looks like we need to get a look at other log files. Can you share logs with the file ending .err from /var/log/mysql please?

Alternatively if you want I can take a look. I will need root access to check and fix the issue. Feel free to send me a message.

[youssefbasha]

root@vps570089:/var/log/mysql# ls
error.log error.log.1.gz error.log.2.gz error.log.3.gz error.log.4.gz error.log.5.gz error.log.6.gz error.log.7.gz
root@vps570089:/var/log/mysql#
Nothing ends with .err

[Mashiro]

Unfortunately these mysql logs were also empty. Rather sadly. I managed to find hints in /var/log/daemon.log though and here is the interesting part.

Code: (Select All)

Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 7f5698726d80 InnoDB: Error: Write to file ./ib_logfile101 failed at offset 0.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: 1048576 bytes should have been written, only 0 were written.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: Operating system error number 28.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: Check that your OS and file system support files of this size.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: Check also that the disk is not full or a disk quota exceeded.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: Error number 28 means 'No space left on device'.
Apr 23 11:41:42 vps570089 mysqld: InnoDB: Some operating system error numbers are described at
Apr 23 11:41:42 vps570089 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [ERROR] InnoDB: Cannot set log file ./ib_logfile101 to size 48 MB
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [ERROR] Plugin 'InnoDB' init function returned error.
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [Note] Plugin 'FEEDBACK' is disabled.
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [ERROR] Unknown/unsupported storage engine: InnoDB
Apr 23 11:41:42 vps570089 mysqld: 2019-04-23 11:41:42 140009901550976 [ERROR] Aborting
Apr 23 11:41:42 vps570089 mysqld:
Apr 23 11:41:42 vps570089 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

And then I just executed "df -h" to see if we had free space on the disk. What a surprise! We have 0% free disk space. One good (kinda) thing though. We have plenty of inodes left   .

Disk space:

Code: (Select All)

Filesystem      Size  Used Avail Use% Mounted on
udev            968M     0  968M   0% /dev
tmpfs           196M  7.8M  188M   4% /run
/dev/sda1        20G   19G     0 100% /
tmpfs           979M     0  979M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           979M     0  979M   0% /sys/fs/cgroup

iNodes:

Code: (Select All)

Filesystem      Inodes IUsed   IFree IUse% Mounted on
udev            247559   309  247250    1% /dev
tmpfs           250415   351  250064    1% /run
/dev/sda1      1280000 69777 1210223    6% /
tmpfs           250415     1  250414    1% /dev/shm
tmpfs           250415     3  250412    1% /run/lock
tmpfs           250415    15  250400    1% /sys/fs/cgroup

The MariaDB database server cannot start because it cannot write necessary files due to lack of disk space.

I freed up about 100 MB by deleting old logs. I checked what is eat all the space and /home/* is using 17 GB of the 20 GB already. The rest is most likely used up by the OS and installed packages. Most space is used up by /home/ogp_agent/OGP_User_Files.

I guess you have to clean up or get a VPS with a much bigger disk than 20 GB.


EDIT: I used the "du" command to figure out where the most space was used. Example "du -h /" will create a list of all directories with their size in readable values like MB/GB and etc. I then just scrolled through the list and found the directories with the most used space.

[Melvin]

Hey mate, i have some experience with open game panel, i was hosting my own server on it.
what i can help you with to check this out https://www.opengamepanel.org/forum/view...ad_id=6183
i would recommand you to use open game panel forum, they are helpful and active so you will have a lot of support
good luck mate i wish you fix the issue.
https://www.opengamepanel.org/forum/view...forum_id=2

[youssefbasha]

@Hidden Refuge
I got a backup from all the files at ogp user files and deleting them now, what can i do after that?

[Mashiro]

Huh. That is a weird question. After you have freed up space you can most likely start the MariaDB database server normally.

Try it.

By the way: I never spoke about removing everything that used up the space. I was merely speaking about making some free space. If all the files you had were in use / important then of course you have nothing you can move/delete to free up the space if the files are needed for your hosted applications. Things like deleting logs and such can free up a bit of space. That might be enough to start the database server but it will not operate for long because logs will fill up quickly again and the databases also grow when in use.

[youssefbasha]

Wow thanks, worked
Appreciated @Hidden Refuge
I got a backup don't worry, i will just use the important files that i need

[Mashiro]

@youssefbasha

May I use this topic and its content to write an article about the issue you experienced on my blog?

[youssefbasha]

@youssefbasha

May I use this topic and its content to write an article about the issue you experienced on my blog?

Sure, i dont mind.
Hope u help people but dont insult me in your blog xD