Closed Bug 743873 Opened 13 years ago Closed 13 years ago

Command line access to mysql for marketplace-dev.allizom.org

Categories

(Data & BI Services Team :: DB: MySQL, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: scabral)

Details

Looks like the db for this domain got reloaded and I no longer have access. Could I get command line access to this development db with my existing mysql account under user kmcmillan? Same thing as bug 713166. Before I was accessing the db from cm-vpn01.
kumar, can you give me the IP you're coming from?
GRANT ALL PRIVILEGES ON `mpl_dev_allizom_org`.* TO 'kmcmillan'@'10.2.72.11' IDENTIFIED BY PASSWORD 'password hash elided';
Assignee: server-ops-database → scabral
it's on addons[1-6].stage.db.phx1.mozilla.com GRANT ALL PRIVILEGES ON `addons_dev_allizom_org`.* TO 'kmcmillan'@'10.2.72.11' IDENTIFIED BY PASSWORD '*34C58220CAA418FD354AEEC59463704FE3FDF77C';
Status: NEW → ASSIGNED
I believe we resolved this yesterday....
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
After netops opened the flow (bug 744228) I'm coming from a different IP, it looks like. [kmcmillan@cm-vpn01 ~]$ mysql -u kmcmillan -p -h db-zlb-rw.stage.addons.phx1.mozilla.com addons_dev_allizom_org Enter password: ERROR 1045 (28000): Access denied for user 'kmcmillan'@'10.8.70.202' (using password: YES)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Try now? sorry it took so long, I was at a conference last week. mysql> GRANT ALL PRIVILEGES ON `addons_dev_allizom_org`.* TO 'kmcmillan'@'10.8.70.202' IDENTIFIED BY PASSWORD 'password hash elided'; Query OK, 0 rows affected (0.04 sec) mysql> GRANT ALL PRIVILEGES ON `mpl_dev_allizom_org`.* TO 'kmcmillan'@'10.8.70.202' IDENTIFIED BY PASSWORD 'password hash elided'; Query OK, 0 rows affected (0.00 sec)
Thanks sheeri! Yep, that did it.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.