12 Mar
2021
12 Mar
'21
11:06 a.m.
Hi Andy,
MariaDB error log:
2021-03-12 10:17:51 3078658496 [Note] InnoDB: Highest supported file format
is Barracuda.
2021-03-12 10:17:51 3078658496 [Note] InnoDB: 128 rollback segment(s) are
active.
2021-03-12 10:17:51 3078658496 [Note] InnoDB: Waiting for purge to start
2021-03-12 10:17:51 3078658496 [Note] InnoDB: Percona XtraDB (
http://www.percona.com) 5.6.49-89.0 started; log sequence number 72327871660
2021-03-12 10:17:51 2483026752 [Note] InnoDB: Dumping buffer pool(s) not
yet started
2021-03-12 10:17:51 3078658496 [Note] Plugin 'FEEDBACK' is disabled.
2021-03-12 10:17:51 3078658496 [Note] Recovering after a crash using tc.log
2021-03-12 10:17:51 3078658496 [ERROR] Can't init tc log
When starting MariaDB I just get that first error message I posted:
Job for mariadb.service failed because the control process exited with
error code.
See "systemctl status mariadb.service" and "journalctl -xe" for
details.
Re: the original reboot, the system wouldn't respond when I tried to grow
the disk, sorry didn't capture any error messages at that stage but the
only thing wrong at that point was chocka full disk. Disk expand completed
successfully after rebooting and the new space is showing.
Cheers,
Andy
On Fri, 12 Mar 2021 at 10:43, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Andy,
On Fri, Mar 12, 2021 at 10:35:59AM +0000, andy.duffell(a)gmail.com wrote:
Background: I let the disk get completely full on
my VPS (oops!). Bought
another 5GB but the system was pretty unresponsive due to lack of disk
space. Rebooted, thinking to dump some old kernels to free space, had to
do
this in Xen and it took an absolute age to shut
down. Booted and resized
disk successfully, but...
Was there a reason why you couldn't grow the disk before/without
rebooting?
Status: "MariaDB server is down"
What does MariaDB say in its error log as you try to start it? You
can normally find that at /var/log/mysql/error.log on Debian,
probably the same for Ubuntu.
$ tail -F /var/log/mysql/error.log
then in another window
$ sudo systemctl start mariadb
Webmin also returns this fault code when prompted
to start the DB:
DBI connect failed : Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock'
Just means that mariadb isn't running.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users