-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Job for mariadb.service failed because the control process exited with error code. #8
Comments
Hi and thanks for the feedback... Yes, it seems Debian 12 breaks a bunch of things.. :( I ran up a vanilla Debian 12 and it seems theres a few new and screwy things that might have changed around various OS behvaviour, db defaults, root permissions, unix socket access and such ... but Im not fully sure of the exact cause as yet. I can replicate a range of errors around database creation where db root access is needed (parts that have worked perfectly for years) and there is an earlier mysql timezone fix that now breaks mariadb cold. As I'm a but time limited it would seem prundent to hold back from and wait for the dust to settle with such a new OS version and to absorb a bit more backgounf info on whats changed. Best to stay closer to Bullseye / 11 variants for the time being. I'll leave this open with intent to take a closer look when I can find time... or if some other kind soul wants to help and submit PR that would be awesome! |
Thank you for the feedback! As you are time constrained, I'm knowledge constrained :) but will tinker to see if I can learn anything. |
Tim, An update: Just now I was able to massage the code through in smaller chunks and I could successfully create the guacamole database. This might be a Maria bug coz no other versions have had any issue with this exact script syntax in years, unless I’m missing something really dumb... To reproduce the error, run these commands in a script running as sudo : will return The error is a bit misleading because if I omit the port number in the script commands, auth works fine and the SQL code runs perfectly :
Weird |
closed this, replaced with a more specific issue #10 |
Hello,
Working with the script on Debian 12, getting the subject error. Didn't see any history on this, thought I would raise it as an issue.
The text was updated successfully, but these errors were encountered: