You are here
L. Arnold - Sat, 2022/02/19 - 21:22
I spent a fair bit of time getting SSL certs functioing. All essential services except for MariaDB are able to run and function. Webmin. SSH (Webshell still has an SSL issue).
I need MariaDB to start.
I have run
turnkey-init a few times. Part of the issue is the old system had a shorter password (7 charachters) while 16.x requires 8 charachters.
I have also done the following
apt-get update
apt-get install mariadb-server
Not sure what to do from here other than turn the old system on (doing that now). Unfortunately my paid SSL just expired and TKL 15.x is not taking LetsEncrypt from confconsole. (will try again).
Any thoughts on how to proceed?
thank you.
Forum:
Header of the last post had the subject:
copied here for clarity:
Not able to get MariaDB to start after a TKLbam restore migrating TKL Joomla3 15.x to TKL Joomla3 16.1
Pulled the dehydrated certs etc from failing DB install (worked)
Well I have a few month's to work it out.
Last time I went to move Joomla3 up a TKL generation I remember lot's of work arounds.
I don't know if those workarounds caused this issue or whether Joomla just does not like to jump through TKLBAM.
Seems like everything moved across. Just can't start the database... anyway, we have a system for now TKL 15.x. Dehydrated won't generate but the 16.x certs work with 15.x when manually placed and called.. I'll loop back around on this.
What errors is MySQL/MariaDB giving?
If a service isn't starting, then the first thing to check is it's logs. Hopefully that might give some insight.
For insight into the MySQL/MariaDB service, you can check the journal:
There may also be a log file in /var/log. I forget, but I think it was /var/log/mysql?
MariaDB also have a troubleshooting page that might give some further ideas.
Please feel free to post back logs and/or other info if you want some further feedback.
I will check
I bought myself those few months with the cert "copy over" to the old server.. but that is coming up and I should work through this on Joomla. Have not been working with Joomla too much (just letting it run).. Need to do so again though. It's moved many generations. Why stop now?
I have done manual migrations before. May need to do that again. A bit of a pain TBH.
Trying to migrate Joomla 15->16... progress but not yet
MariaDB was not starting after tklbam-restore
Log is:
/usr/sbin/mysqld: unknown variable 'innodb_file_format_max=Barracuda'
I read that the version installed is 10.3.4
however, when reading about that variable, it was removed in 10.3.1
MariaDB Docs return the following:
innodb_file_format_max
Description: The highest XtraDB/InnoDB file format. This is set to the value of the file format tag in the shared tablespace on startup (see innodb_file_format_check). If the server later creates a higher table format, innodb_file_format_max is set to that value. See XtraDB/InnoDB File Format for more on the file formats.
Commandline: --innodb-file-format-max=value
Scope: Global
Dynamic: Yes
Data Type: string
Default Value: Antelope
Valid Values: Antelope, Barracuda
Deprecated: MariaDB 10.2
Removed: MariaDB 10.3.1
removed from
/etc/mysql/conf.d/innodb_barracuda.cnf
Well, that allowed me to start MariaDB to start.
But Unfortunately, Joomla is not starting however.
I get "error" simply on both the main web and the admin interface.
I believe the issue is around the MySQL password.
In the old version TKL Joomla 15.1) I had a 7 charachter Password.
In the new one I ran "turnkey-init" after the Tklbam Restore to try to get control.
Basically this process likely changed my Root and Joomla Password.
However, when I go into Adminer, I can only get to the Data with my OLD MySQL Password (at Root).
likely to try "turnkey-init" again. as I think MariaDB/Mysql was not running when I ran turnkey-init.
Failing that I likely need to change it in the backend and find out if Joomla writes a password somewhere as well.
I suggest re-running the non-interactive "regen-secrets' script
Please try re-running the firstboot non-interactive "regen-secrets' script. Note that that isn't re-run when you you run 'turnkey-init'. Rerun the script like this:
Hopefully that should "just work", and regenerate the database password.
Nope
Adminer password does not change after turnkey-init
I believe the Maria/Mysql DB does.
I do not know if the configuration.php password changes in Joomla when turnkey-init is run.
All I know is that Joomla will not start (gives an "error") but nothing else.
I do think the issue of the required password lengths between tkl15 and tkl16 is part of this.
Again, this started with tklbam-restore (joomla) going from gen 15 to gen 16 TKL.
A bit stumped. Would rather not do this through some Joomla Addon but may be required.
I'm not 100% sure...
I'm not 100% sure, but please try re-running the "regen-secrets" script as I just noted above (as I mentioned above - this isn't re-run when you run 'tturnkey-init').
Also, deep apologies on my crazy slow response. I've been really burried with both personal and behind-the-scenes TurnKey stuff. I'm still not completely clear, but have cleared enough backlog to put aside some time to catch up on the forums.
Add new comment