Question thread #149

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[pauamma]

In addition to my suggestions in that same thread (those that you haven't ruled out as inapplicable, I'd look at whether the database got corrupted on shutdown or restart. (Unfortunately, not being a MySQL database admin, I have no idea how to do that. Perhaps someone who does can elaborate.)

[adrenalinerush]

Apparently putting it out there into the world is enough for the answer to pop up into my face. 😂 Just circling back in case anyone else runs into this issue with installation (and I don't recall seeing anything specifically about this in the install guidelines I used but I very well could have overlooked it and online documentation for MySQL seems to indicate this would not be an issue):

The problem was, in fact, with the database, specifically within the character_set and collation parameters and a mismatch with the character_set_system being utf8mb3 where everything else was utf8mb4/utf8mb4_0900_ai_ci.

Essentially what was happening is the utf8mb3 was causing the garbage/blank character spaces to actually write to the database in lieu of some posted comments/posts - I was able to track that down with watching the database table populate between comments to spot the pattern (it was specifically related to some emojis and iOS "special" characters like curly quotes). All seemed fine on the front end with Memcached masking the issue - they'd post correctly to Memcached but fail in the database, so with restarts - bye bye data.

Thank you again!

[pauamma]

Thank you for the postmortem.