CODEWITHSUNDEEP
typo3typo3-6.2.x
Rossi
Rossi

Reputation: 1

Crashed rootserver, problems getting typo3 up and running from backups, now db problems (mariadb)

Due to a libc mismatch (or the like) while dist-upgrading an older Debian server I had to re-install it completely. I choose Debian bookworm, and installed Apache (2.4.57-2) along with MariaDB (1:10.11.3-1). I had in mind to update Typo3 to a current version later, but I thought it would be better to get the old Typo3 version up and running first (6.2.30, by the way), and then update Typo3 to successively higher version later. As I did not expect to get an old Typo3 running using PHP 8.2 I installed PHP 5.6 from the Sury repository. Importing the databases went smoothly; just copied the binary files (to /var/lib/mysql etc.), and after running mariadb-upgrade (if I remember correctly) the databases were up and running. Access to DB via socket and port (3306/mysqld.sock) no problem so far.

Well, Typo3 now throws an error "Oops, an error occurred!", [sitename]/typo3 along with [sitename]/typo3/sysext/install/Start/Install.php (which I also tried, having file backups I thought why not) both yield (sorry, that's long):

Oops, an error occurred!

It looks like the character set utf8 is not used for this connection even though it is configured as connection  charset. This TYPO3 installation is using the  $GLOBALS['TYPO3_CONF_VARS']['SYS']['setDBinit'] property with the  following value: "". Please make sure that this command does not  overwrite the configured charset. Please note that for the TYPO3  database everything other than utf8 is unsupported since version 4.7.

I tried, of course, to find something in the 'net about that error messages, but I am a bit overwhelmed from a lot of results about Typo3 versions either too old (like 4.5, text) or too new, eg. text, or (perhaps more fitting) text. As I strongly suspected an utf8/utf8mb4 mismatch (as Debian installs MariaDB using UTF8MB4, as far I I know), I inserted 'charset' => 'utf8mb4' to LocalConfiguration.php, but it did not change anything.

Now I am unsure what to do, and so I thought it would be perhaps better to ask for some help. And, well, I'm not a DB person. I noticed most Typo3 mailing lists seem to be dead, but I found a hint (in typo3_src-12.4.6/README.md, just got the sources, didn't do anything with V12) about stackoverflow, so I came here. As you perhaps see my Typo3 days are some years past, too, so I'd be very grateful for some hints how to go on:).

Edit: I forgot one thing… the "Oops" error page mentioned above also has a link at "More information regarding this error might be available online.", this leads to https://docs.typo3.org/typo3cms/exceptions/main/en-us/Exceptions/1389697515.html Exception 1389697515, which did not yield me much of a clue.

Upvotes: 0

Views: 312

Answers (1)

Garvin Hicking
Garvin Hicking

Reputation: 526

TYPO3 6.2 was using MySQL 5.1 at the time. More recent versions of that, or newer MariaDBs will probably yield all sorts of issues. This is only the tip of the iceberg, like you found out, utf8 instead of utf8mb4 is needed for this old TYPO3.

How complex was your installation? It would probably be easiest if you install a fresh TYPO3v12 and try to import your content (pages&tt_content) there, but that can be a huge task depending on how many and which extensions you used, if multidomain/multilanguge/workspaces etc were involved etc...

(Another option: try to instead setup a mysql 5.1 server, on another port or so - or mariadb 5.1. Try to import an SQL dump, not a binary, from your currenr install)

HTH - this will not be an easy task.

Upvotes: 0

Related Questions