Skip to content
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

[mattermost] Fix mysql recovery docs #810

Closed
robinmetral opened this issue Mar 27, 2023 · 2 comments
Closed

[mattermost] Fix mysql recovery docs #810

robinmetral opened this issue Mar 27, 2023 · 2 comments
Assignees
Labels
mysql on-hold Issues or Pull Requests with this label will never be considered stale

Comments

@robinmetral
Copy link

robinmetral commented Mar 27, 2023

Describe your suggestion as much as you can

Hi there—I've been using Bitnami for my Mattermost server for years. In general, things mostly just work (thank you).

But whenever there's the smallest hitch, Bitnami docs are outdated, flawed, or simply nonexistent. The best resource for support used to be the community forum, which is now unfortunately defunct (see #133, #116 et.al.)

Today I find myself locked out of mysql on my Bitnami Mattermost install. Full access to the app itself via SSH and full access to the AWS instance it's been deployed to, yet I can't find a way to access my database.

The Bitnami docs for resetting the mysql password are either wrong, or outdated. Instructions seem to just fail without so much as an error message, which makes the issue hard to pinpoint. My install is completely standard and I practically never SSH into the server (I prefer to avoid it at all costs, that's why I'm using Bitnami), so I have strong doubts that this is an isolated case (though I might naturally be wrong).

This is not the first time I run into something like this: the community forums don't exist anymore for me to reference old posts, but I have already ran into similar issues with documentation. Back then, someone on the community forums helpfully pointed out the issue, and docs were eventually updated. To me, this kind of issues are a red flag for a developer tool, especially one with self-serve support: I don't trust Bitnami to troubleshoot issues anymore.

I hope that you'll take a look at the docs I shared above and see if anything should be fixed, for the sake of other Bitnami users in the future. Unfortunately I won't be using it anymore, and can't recommend it as a tool.

@github-actions github-actions bot added the triage Triage is needed label Mar 27, 2023
@robinmetral
Copy link
Author

Managed to get in by adding skip-grant-tables in ~/stack/mysql/my.cnf (mysql config file):

# ...

[mysqld]
skip-grant-tables
some-other-options = 123

# ...

I restarted mysql with /opt/bitnami/ctlscript.sh restart mysql, and could then log into the DB with mysql -u root (no password prompt) and reset my password using the following:

FLUSH PRIVILEGES;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';

(from the official docs)

(Afterward, remove the skip-grant-tables from the mysql config again, and restart the service again)

@jotamartos
Copy link
Collaborator

Hi @robinmetral,

Thank you for taking the time to report this and post your solution. I'll create a task on our side to review and improve that guide. Sorry for the inconvenience.

@github-actions github-actions bot added on-hold Issues or Pull Requests with this label will never be considered stale and removed triage Triage is needed labels Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mysql on-hold Issues or Pull Requests with this label will never be considered stale
Projects
None yet
Development

No branches or pull requests

2 participants