Two things I noticed when I tried to investigate creating a new CVS account in bug 772257: 1) http://despot.mozilla.org no longer re-directs to https://despot.mozilla.org (arguably a feature, doesn't really matter that much, but I mention because it may be related) 2) Trying to sign-in at https://despot.mozilla.org results in: Can't connect to database server at /opt/webtools/despot/despot.cgi line 111. AFAIK the modules Christina wants access to in bug 772257 won't be accessible unless she has the appropriate despot permissions, so this is blocking getting her that access.
Sure enough, this is having problems accessing the database. I believe a network flow is in order. [email@example.com despot]# grep db_host config.pl $::db_host = '10.22.70.105'; [firstname.lastname@example.org despot]# nc -z 10.22.70.105 3306 [email@example.com despot]# echo $? 1 We'll need a network route open up for this.
The network connection has been fixed, although credentials are being ignored. [firstname.lastname@example.org despot]# mysql -udespot -p -h10.22.70.105 despot Enter password: ERROR 1045 (28000): Access denied for user 'despot'@'10.22.74.60' (using password: YES) [email@example.com despot]# cat config.pl #!/usr/bin/perl # # Despot configuration file # $::db_host = '10.22.70.105'; $::db_name = 'despot'; $::db_user = 'despot'; $::db_pass = 'omgseekrits'; $::sitename = 'mozilla.org'; # site name $::ownersurl = 'http://www.mozilla.org/owners.html'; # owners page URL $::adminname = 'sysadmins'; # owner name $::adminmail = 'firstname.lastname@example.org'; # owner e-mail address #$::anonymous_sysuser = 'cvsuser'; # the system user the "anonymous" account will use for pserver 1; Off to the DBA's, hopefully they can get some auth working for this.
For reference the password is not 'omgseekrits'. I edited out the real password.
added access for email@example.com using existing password
Out of curiosity, do you guys know what broke this?
The datacenter migration probably broke this. It broke both the user-host access field in the MySQL auth tables and network access was not explicitly allowed (which it needed to be)
Looks fixed now, any reason to leave this open?
Can't think of anything.