Rael's picture

I'm asking a big courtesy, have someone the iso file for the Turnkey/Joomla 16 to send me or know where i can find it?

I'd search for it, but it's too old :-(

I've a problem with an old installation of Turnkey/Joomla 16. It's a VM and is crashed, and now there is no way to start mysql, I've try everything but it's definitively dead :-(

But now i don't know how to restore the DB on a differen machine with a more recent mysql.

So i want to create a new VM with Turnkey/Joomla16, and move all the DB and joomla data on the new machine, but I haven't the iso.

If someone could help me I'll be gratefull for all life :-)

Jeremy Davis's picture

We do not have any of the really old TurnKey appliances. FWIW our policy is to keep only the most recent TurnKey version, plus the previous, most recent TurnKey major version. So currently that is v14.2 (old version) and the latest v15.x release. I'm not 100% sure, but my guess is that you are needing v12.x, or perhaps even v11.x.

When you say that that your VM has crashed and "there is no way to start mysql, I've try everything but it's definitively dead", could you please elaborate?

IMO the first thing to check is free space within your VM. Over time servers can build up a fair bit of cruft, so it may simply be that it's run out of free disk space, thus stopping MySQL from being able to start. Assuming that it is only MySQL that won't start and you can still start the VM itself and log in via SSH, to check free space, run this:

df -h

And look for the line that ends with '/'. E.g. here is the output from a local VM I have running:

# df -h
Filesystem                Size  Used Avail Use% Mounted on
udev                      2.0G     0  2.0G   0% /dev
tmpfs                     396M   23M  374M   6% /run
/dev/mapper/turnkey-root   25G  6.7G   17G  29% /
tmpfs                     2.0G     0  2.0G   0% /dev/shm
tmpfs                     5.0M     0  5.0M   0% /run/lock
tmpfs                     2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/sdb1                  76G  5.6G   66G   8% /mnt

The line that ends with '/' is this one:

/dev/mapper/turnkey-root   25G  6.7G   17G  29% /

So that shows I'm using 29% (6.7GB) of my 25GB root volume (17GB free space remaining). If yours has less than a few hundred MB free then that could well be the issue!

If that's the case, then you can free up some space by doing a bit of a clean up, but I suspect that the best longer term way to address a lack of free space, would be to increase the size of the root volume (or add an additional volume). Let's cross that bridge when we get to it though.

If that isn't the issue, one other thing worth checking is the free space on the host. If your VM uses a "sparse" disk (i.e. only takes up the space that the files within it are using, rather than have the full size of the virtual HDD) then if the host has run out of free space, then even if the VM is reporting sufficient free space, it may not be able to expand to accommodate new files.

As well/instead it would also be useful to see the last few log entries for MySQL. That should either confirm that the issue is lack of disk space, otherwise, give us some indication of how terminal your issues are. Hopefully, the following should still apply to your old server, please post the output of:

tail -20 /var/log/mysql/error.log

As for moving your DB to a newer version of MySQL, that should be possible, although I'm not sure how involved it may be. Moving your old Joomla to a newer version of PHP is almost certainly going to be a nightmare!

So unless someone comes along with a copy of TurnKey that matches what you have (I wouldn't hold your breath, past experience suggests that it unlikely), I suspect that trying to resurrect your old server will be your best bet.

Also before you go any further, if you haven't already, I would encourage you to create a backup copy of your VM. A snapshot is ok (and I would certainly do that for easy rollback if required), but IMO, exporting the whole thing would be well worth the effort. That way if you completely bork it, you will be able to get back to exactly where you are now.

Good luck and look forward to hearing back.

Rael's picture

Hello Jeremy,
thanks for your support, I've solved the issue!
The problem was effectively a disk space issue.
The system have two disks of 30Gb connected as a LVM group.
The df command was reporting 15Gb free, but looking at the % used it was reporting 100% used (!?)
So i reduced with gparted the partition with the free space, created a new LVM partition in the new free space, and connect the new partition to the volume group.
Now the system report 15 GB free and 85% used :-)
And mysql returned to work fine :-)
Thanks again for your assistance!

p.s. we are used to backup the machines in our VM enviroment, but the machine is used occasionally, and when user realized that it wasn't working, the backup was corrupted too :-(


Jeremy Davis's picture

Great news! Glad you worked it out. :)

Add new comment