Closed Bug 869122 Opened 12 years ago Closed 12 years ago

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gozer, Assigned: rbryce)

Details

(Not sure where to stick this in the bugzilla queue) It's a new website in the static cluster serving ISP autoconfiguring data for Thunderbird (and other e-mail clients) It's a simple static https:// site and it returns XML documents, for instance https://autoconfig.thunderbird.net/v1.1/gmx.com: <clientConfig version="1.1"> <emailProvider id="gmx.com"> <domain>gmx.com</domain> <domain>gmx.tm</domain> <domain>gmx.us</domain> <domain>gmx.co.uk</domain> <domain>gmx.es</domain> <domain>gmx.fr</domain> <domain>gmx.ca</domain> <domain>gmx.cn</domain> <domain>gmx.co.in</domain> <domain>gmx.com.br</domain> <domain>gmx.com.my</domain> <domain>gmx.hk</domain> <domain>gmx.ie</domain> <domain>gmx.ph</domain> <domain>gmx.pt</domain> <domain>gmx.ru</domain> <domain>gmx.se</domain> <domain>gmx.sg</domain> <domain>gmx.tw</domain> <domain>gmx.com.tr</domain> <domain>gmx.it</domain> <domain>gmx.li</domain> <!-- gmx.net is same company, but different access servers --> <displayName>GMX Freemail</displayName> <displayShortName>GMX</displayShortName> <incomingServer type="imap"> <hostname>imap.gmx.com</hostname> <port>993</port> <socketType>SSL</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </incomingServer> <incomingServer type="imap"> <hostname>imap.gmx.com</hostname> <port>143</port> <socketType>STARTTLS</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </incomingServer> <incomingServer type="pop3"> <hostname>pop.gmx.com</hostname> <port>995</port> <socketType>SSL</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </incomingServer> <incomingServer type="pop3"> <hostname>pop.gmx.com</hostname> <port>110</port> <socketType>STARTTLS</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </incomingServer> <outgoingServer type="smtp"> <hostname>mail.gmx.com</hostname> <port>465</port> <socketType>SSL</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </outgoingServer> <outgoingServer type="smtp"> <hostname>mail.gmx.com</hostname> <port>587</port> <socketType>STARTTLS</socketType> <username>%EMAILADDRESS%</username> <authentication>password-cleartext</authentication> </outgoingServer> </emailProvider> </clientConfig>
Gozer, Can you fill out a mana page first for this service? Put it under https://mana.mozilla.org/wiki/display/websites/Home You can "Add page from template" and use "WebsiteTemplate". Thanks!
Flags: needinfo?(gozer)
:gozer, Thank you. One more question: who needs to be paged if there is a problem with it? If it's infra oncall, then please fill out the "Common troubleshooting" section on the page you just created, so we know how to fix if there's a problem, and also let us know who is POC for escalations (labs-ops is vague to me, is it just you?). TIA!
Flags: needinfo?(gozer)
(In reply to Dumitru Gherman [:dumitru] from comment #3) > :gozer, > Thank you. > One more question: who needs to be paged if there is a problem with it? Well, it's just a static site served by the static cluster, so I am not sure it needs any special care different from any of the other sites in there. > If it's infra oncall, then please fill out the "Common troubleshooting" section > on the page you just created, so we know how to fix if there's a problem, I'll see what other sites look like, but I suspect the only reason this site could have problems is if the static cluster as a whole has issues. > and also let us know who is POC for escalations (labs-ops is vague to me, is > it just you?). labs-ops is cyliang and me, actually.
Flags: needinfo?(gozer)
Assignee: server-ops → rbryce
Added check_https_string to the static.zlb.phx.net hostgroup to search for the string "clientConfig" in the xml output. This should not change even if the content changes in the future. Created https://mana.mozilla.org/wiki/display/NAGIOS/https+string+-+Thunderbird+Autoconfig for oncall to handle the alert. root@nagios1.private.phx1 plugins]# ./check_http -I autoconfig.thunderbird.net --onredirect=follow -H autoconfig.thunderbird.net -u /v1.1/gmx.com --ssl -s clientConfig https://nagios.mozilla.org/phx1/cgi-bin/status.cgi?host=static.zlb.phx.mozilla.net&style=detail
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Please also monitor the value that actually is/was configured in the client, namely https://live.mozillamessaging.com/autoconfig/v1.1/ Also, currently, it redirects to http (bug 886532), which is should never have done. So, please also add a check that it's SSL all the way, and that all the certs are valid (CA, expiry, hostname in cert etc).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Ben Bucksch (:BenB) from comment #6) > Please also monitor the value that actually is/was configured in the client, > namely https://live.mozillamessaging.com/autoconfig/v1.1/ Not sure what you mean here. Do you mean to test the content of a file served from this url? > Also, currently, it redirects to http (bug 886532), which is should never > have done. So, please also add a check that it's SSL all the way, and that > all the certs are valid (CA, expiry, hostname in cert etc). I'll get the cert check squared away shortly.
(In reply to Rick Bryce [:rbryce] from comment #7) > (In reply to Ben Bucksch (:BenB) from comment #6) > > https://live.mozillamessaging.com/autoconfig/v1.1/ > > Not sure what you mean here. Do you mean to test the content of a file > served from this url? I mean: Comment 0 mentions https://autoconfig.thunderbird.net/v1.1/gmx.com . However, Thunderbird requests https://live.mozillamessaging.com/autoconfig/v1.1/gmx.com (or better: gmx.net), not autoconfig.tb.net. The live.momo URL should be included in the test. And yes, it would be good to check the content, at least that it's valid XML and contains "<domain>gmx.com</domain>".
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.