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

MySQL error after running --update flag #446

Closed
stevenromero02 opened this issue Jun 23, 2021 · 4 comments
Closed

MySQL error after running --update flag #446

stevenromero02 opened this issue Jun 23, 2021 · 4 comments
Labels
can't reproduce Dev unable to reproduce the issue to properly address it without involved user assistance.

Comments

@stevenromero02
Copy link

I have received the following error after updating an installation that we used last October (used rootthebox.py --update):

[I 210623 18:16:38 init:266] Checking for Database Updates...
[E 210623 18:16:38 rootthebox:54] Error: (MySQLdb._exceptions.OperationalError) (2005, "Unknown MySQL server host 'password@127.0.0.1' (22)")
(Background on this error at: http://sqlalche.me/e/14/e3q8)

I have also tried to re-run depends.sh to see if I was missing some dependency. If the error is difficult to fix, is it possible to extract the contents of the database to use in a fresh RTB installation?

@eljeffeg
Copy link
Collaborator

The formatting of your hostname looks odd. I wouldn't think it would have the username in there for this error, as that's specified in its own config entry. And password seems like an odd user account. So I'm confused about what's happening there. I can't reproduce this error when I try it and I'm not aware of any changes that would break the MySQL connection.

As for exporting, we do have built in exporting of an XML, but it requires the database connection. However, you should be able to copy out that database or reuse it. It appears to be a connection problem, so if you resolve the connection issue, but reinstalling RTB or fixing the issue, it should work.

@punitdarji
Copy link

punitdarji commented Jun 23, 2021

It is working fine. Please check your mysql connection string.

@eljeffeg
Copy link
Collaborator

eljeffeg commented Aug 4, 2021

@stevenromero02 Did you ever get this resolved? Looking back at my comment and the odd username. I have seen this type of thing before when the mysql password has an @ symbol in it. SQLAlchemy reads it as a delimiter #448 I plan to look at it soon and implement a check / fix. Not sure if it will address your issue though.

@eljeffeg eljeffeg added the can't reproduce Dev unable to reproduce the issue to properly address it without involved user assistance. label Aug 6, 2021
@stevenromero02
Copy link
Author

I did manage to resolve the issue a few weeks ago by removing the @ symbol from the password. I wasn't aware that the symbol was a delimiter, but I figured something must be wrong with the password since that is where the error was occurring. Thanks for checking back on this.

eljeffeg added a commit that referenced this issue Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can't reproduce Dev unable to reproduce the issue to properly address it without involved user assistance.
Projects
None yet
Development

No branches or pull requests

3 participants