Thanks for persisting with this and sorry it's still causing pain...
Re your latest experience, assuming I understand correctly, in Domhnall's last post he noted that he used 'root' without a password. To quote him (my bold):
[...] threw root in there with no password and it came right up and ran [...]
Although he did also note:
[...] I had tried that previously on the ISO version and it didn't work [...]
So I really don't understand what the hell is going on here and it's really frustrating...
I can only imagine what a PITA it is for you! My guess is that you're just trying to get some work done... So much for "turnkey"... :(
Regardless, thanks again for persevering and helping out.
Moving on to your post specifically (that I'm replying to):
[...] used root and the password, and can see inside the db.
[...]
i rebooted the server, and error 500 reappeared.
TBH, I think that's the bit causing the issue: I.e. setting a root password, without also recreating/adding an additional system user - with the password stored somewhere and the service adjusted to use that user/password. As I think I may have mentioned elsewhere above, AFAIK the service uses 'root' (mysql user) for starting/stopping, then drops to the 'mysql' user for all other functionality. I do recall working that out back when the 'root' user socket authentication first became the default. But given the experiences noted in this thread, I need to double check my understanding.
In the meantime, do you still have a snapshot of a working system? If so, could you try NOT setting a 'root' MariaDB user password as per what Domhall noted above and see how that goes? If MariaDB and Redmine continue to work after that, please double check by rebooting and/or restarting the MariaDB service.
If not that's cool.
I should also post how the 'root' user can be configured back to using socket authentication. If we can confirm that not setting a 'root' MariaDB "fixes" it, then that would be additional confirmation that my thoughts here are correct.
Rereading this thread, I'm still a bit concerned as some of your and Domhnall's other posts (in this thread) do suggest that perhaps there is something else/additional going on here too? Perhaps a race condition somewhere? *sigh* They're the bane of my existence as they are hard to recreate, thus really hard to fix... As a general rule, if I can recreate the issue myself, I can fix it - or at least devise a workaround.
Regardless, now you guys have provided more info, I definitely need to try to recreate this again. That will hopefully assist me to fully understand this issue better and both provide a work around for "fixing" it, plus look at how I can ensure that users such as you guys avoid hitting it in future.
Thanks for persisting and sorry it's still causing pain...
Thanks for persisting with this and sorry it's still causing pain...
Re your latest experience, assuming I understand correctly, in Domhnall's last post he noted that he used 'root' without a password. To quote him (my bold):
Although he did also note:
So I really don't understand what the hell is going on here and it's really frustrating...
I can only imagine what a PITA it is for you! My guess is that you're just trying to get some work done... So much for "turnkey"... :(
Regardless, thanks again for persevering and helping out.
Moving on to your post specifically (that I'm replying to):
TBH, I think that's the bit causing the issue: I.e. setting a root password, without also recreating/adding an additional system user - with the password stored somewhere and the service adjusted to use that user/password. As I think I may have mentioned elsewhere above, AFAIK the service uses 'root' (mysql user) for starting/stopping, then drops to the 'mysql' user for all other functionality. I do recall working that out back when the 'root' user socket authentication first became the default. But given the experiences noted in this thread, I need to double check my understanding.
In the meantime, do you still have a snapshot of a working system? If so, could you try NOT setting a 'root' MariaDB user password as per what Domhall noted above and see how that goes? If MariaDB and Redmine continue to work after that, please double check by rebooting and/or restarting the MariaDB service.
If not that's cool.
I should also post how the 'root' user can be configured back to using socket authentication. If we can confirm that not setting a 'root' MariaDB "fixes" it, then that would be additional confirmation that my thoughts here are correct.
Rereading this thread, I'm still a bit concerned as some of your and Domhnall's other posts (in this thread) do suggest that perhaps there is something else/additional going on here too? Perhaps a race condition somewhere? *sigh* They're the bane of my existence as they are hard to recreate, thus really hard to fix... As a general rule, if I can recreate the issue myself, I can fix it - or at least devise a workaround.
Regardless, now you guys have provided more info, I definitely need to try to recreate this again. That will hopefully assist me to fully understand this issue better and both provide a work around for "fixing" it, plus look at how I can ensure that users such as you guys avoid hitting it in future.