forums.mozilla.org/addons has a amo auth plugin which connects to the AMO DB RO VIP for user auth. Since our db servers have recently changed, we will need to update this. The new RO VIP is 10.32.126.31.
This blocks logins for all new accounts.
I thought we had the ability to use the auth api now? I'm not a big fan of giving a phpbb install read access to our prod db.
Network flows are open and mysql grants are in place. @webops could you assist with updating forums.mozilla.org amo auth plugin to use the new vip?
update phpbb_config set config_value=('db.ro.mktns.mktdb.services.phx1.mozilla.com') where config_name=('amo_hostname'); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 [firstname.lastname@example.org jcrowe]# nc -vz db.ro.mktns.mktdb.services.phx1.mozilla.com 3306 Connection to db.ro.mktns.mktdb.services.phx1.mozilla.com 3306 port [tcp/mysql] succeeded! Let me know if there are issues :)
Assignee: server-ops-webops → jcrowe
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
This broke data consistency across the generic cluster and alerted our checksums today as generic1 is not the master of the generic cluster. I fixed it, but please be careful when running inserts/updates directly on the cluster. Preferrably we would ask that you run them through the VIP. If that's not possible, be sure to check the MOTD on the server when you sudo up to root for whether or not it's the master. Small mishaps like these can cost a few hours of time on the db end. :)
This I do not understand. I specifically ran these commands on generic2.db as its MOTD stated it was the master. I ask as I was following the established procedures and am curious where the failure was that would have caused issue?
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.