Joomla 3.9.19 VM stack for Mac doesn't start anymore on macOS Big Sur

Georgeq 2020-11-19 15:58:45 UTC #1

Keywords: Joomla - OS X - Technical issue - Other
Description:
I did build my website successfully with the Joomla 3.9.19 VM stack on macOS 10 working fine until macOS 10.15. But since I updated to macOS Big Sur (11.0.1) the Joomla.app doesn't start anymore. Nothing appears on the screen when I try to start the VM

Ibone 2020-11-20 10:33:43 UTC #2

Hi @Georgeq,

Could you check this thread of the community?
Remember change WordPress for Joomla

I hope that helps you,
Ibone.

Georgeq 2020-11-21 13:43:38 UTC #3

Hi @Ibone,

thank you for your response. I'll try to solve my problem with QEMU but then I'll first have to download it to my machine. I encounter a problem already there. According to the QEMU-website I have tot use the 'brew' or the 'port' command in the terminal-window. But in the case of macOS Big Sur the response to both is: command not found. Do I have tot use another command?

Georgeq 2020-11-21 20:08:49 UTC #4

Hi @Ibone,
Sorry for my inexperience, but I discovered later that I first had to install Xcode, then MacPorts, and that I after that could install QEMU. Today I fixed all that preparations and tomorrow I'll try to fix my VM. Thanks so far George

Georgeq 2020-11-22 14:43:13 UTC #5

Hi @Ibone,
Today I succeeded in using qemu for repairing the qcow2-file just as was done in the case of Worpress.
Qemu discovered an enormous amount of errors, and after that the repair function of QEMU reported that it had fixed all the errors. And, when I tried the check of QEMU a second time it confirmed that no errors could be found. But the Joomla.app still refuses to start the vm.

So, my problem is still remaining. Regards, George

Ibone 2020-11-23 08:55:42 UTC #6

Hi @Georgeq,

Could you add the error that appears went you try to start the VM?

Regards,
Ibone.

Georgeq 2020-11-23 16:48:52 UTC #7

Hi @Ibone,

There appears no error message at all. It simply doesn't start.

Regards,
George

Ibone 2020-11-24 09:54:35 UTC #8

Hi @Georgeq,

Could you download the last version of https://bitnami.com/redirect/to/1176198/bitnami-joomla-3.9.22-1-linux-debian-10-x86_64-nami.zip and try to start this?

This last version it already supports macOS Big Sur

Regards,
Ibone.

Georgeq 2020-11-24 20:13:26 UTC #9

hi @Ibone,
What will it do with my earlier developed Joomla website? Can I leave the machine.qcow2 file where it is (after correction by Qemu)? Or, have I to restore the machine.qcow2 file as it was before correction by Qemu? Or, will it overwrite the complete Joomla-directory so that I have to restore (with Akeeba) a former backup that I made of my website? I need to know the consequences of installing a new stack and restarting.

Regards,
George

Ibone 2020-11-25 11:03:46 UTC #10

Hi @Georgeq,

I'm sorry I messed up the link, you need to download this https://downloads.bitnami.com/files/stacks/joomla/3.9.22-8/bitnami-joomla-3.9.22-8-osx-x86_64-vm.dmg and replace the folder applications in your Joomla and try to execute with that change.

I hope that helps,
Ibone.

Georgeq 2020-11-27 11:55:19 UTC #11

Hi @Ibone,

I downloaded the correct version of the Joomla 3.9.22-8 osx stack.
The first try to start this resulted in the error-message that the program couldn't find a required Mac-address.
Thereafter I wanted to try the program with its own default Joomla-website, so I deleted the .bitnami folder with all of its contents (after having stored a backup of it in a safe place). When I started the stack again all went well. The window of the program appeared without error messages and I could start the default Joomla application.
My idea is now that, when I could find the location where the default website is installed (such as htdocs), I might be able to transfer the latest backup of my website there en restore it with help of Akeeba's Kickstart.

My main question is now: would this be a feasible procedure, or should I proceed otherwise?

When the answer to this question would be 'yes' then I"ll have some additional questions (f.i. where tot find the correct directory for restoring my website; and: is the MariaDB-database in the new stack compatible with the MySQL-database of my original website?).

Regards,
George

Ibone 2020-11-30 08:27:11 UTC #12

Hi @Georgeq,

could you get the q code of the old version and put it into the new one and try to run it?
If it's work please do a backup.
Please check the logs when you try to do that.

Regards,
Ibone.

Georgeq 2020-12-01 16:33:38 UTC #13

Hi @Ibone,

I have no idea of what you mean by q code, or where to find it.

Besides you didn't answer my main question!
Moreover I'm afraid that the version of the Joomla 3.9.22-8 osx stack that you advised me to download is not yet fully tested or ready for use. When I f.i. try to reach the Joomla-directory of the mounted /opt/bitnami volume, it appears to be an alias, and when I click on it, an error message says that the original of this alias 'Joomla' cannot be found. Wouldn't it be wiser for me to wait until the Big Sur proof Joomla stack is fully developed and ready for use?

Regards,
George

Ibone 2020-12-02 11:35:50 UTC #14

Hi @Georgeq,

The last version of Joomla is working in Big Sur and the databases (MySQL to MariaDB) should be compatible.

I'm sorry I wrote it down wrong, I mean qcow

Maybe this thread of the community could help you

Regards,
Ibone.

Georgeq 2020-12-03 10:01:05 UTC #15

Hi @Ibone

As you instructed, I replaced the machine.qcow2 (corresponding with the default 'My Site') with the old machine.qcow2 file that I repaired with help of Qemu (on Nov. 22).

See the result on attached screenshot. I also send the screenshot that shows how I replaced old cow2 file for new.

If necessary I could also replace actual ssh-keys with older ones.

Regards,
George

Ibone 2020-12-04 08:36:46 UTC #16

Hi @Georgeq,

Could you check this thread of the community?

Regards,
Ibone.

Georgeq 2020-12-04 20:35:28 UTC #17

Hi @Ibone

I could find the bootlog according to the instructions you cited in your post.

Do you want me to share this boot.log file with you? How to do that? As I understand I can only upload jpeg, png or other picture formats. The boot.log file is too big for a screenshot.

Regards,
George

Georgeq 2020-12-04 20:46:56 UTC #18

hi @Ibone,

I tried to copy and paste all the lines of the boot.log file in a reply, but the amount of characters it contained was more than allowed. Is there another way of sharing this file with you?