Hi tech team,
We've noticed several Acoustic/Silverpop failmails that have continued from this past week. The latest was from last night. Can we triage?
cc: @PPenloglou-WMF @NNgu-WMF for visibility
| nisrael | |
| Jan 13 2025, 12:26 AM |
| F58180211: Screenshot 2025-01-12 at 7.25.11 PM.png | |
| Jan 13 2025, 12:26 AM |
Hi tech team,
We've noticed several Acoustic/Silverpop failmails that have continued from this past week. The latest was from last night. Can we triage?
cc: @PPenloglou-WMF @NNgu-WMF for visibility
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Update omnimail-silverpop | wikimedia/fundraising/crm | master | +4 -4 |
@Eileenmcnaughton wonders if this might be related to snooze testing, and will resolve now that's done.
This is related to DNS lookup failures:
8 │ 2025-01-14 03:29:53,087 ERROR Cannot connect to transfer.silverpop.com:22 [transfer.silverpop.com:22]. Error 0. [notice] 9 │ 2025-01-14 03:29:53,087 ERROR php_network_getaddresses: getaddrinfo failed: Name or service not 10 │ 2025-01-14 03:29:53,087 ERROR known SSH2.php:1312 11 │ 2025-01-14 03:29:53,087 ERROR Omnimail\Exception\Exception: Login Failed in [error]
When doing a query, you can see that the address is not known:
dwisehaupt@stealth:~$ host transfer.silverpop.com Host transfer.silverpop.com not found: 3(NXDOMAIN) dwisehaupt@stealth:~$ dig transfer.silverpop.com ; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> transfer.silverpop.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63249 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;transfer.silverpop.com. IN A ;; AUTHORITY SECTION: silverpop.com. 769 IN SOA ns1.acoustic-adm.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 ;; Query time: 9 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Tue Jan 14 10:44:38 PST 2025 ;; MSG SIZE rcvd: 129
Has acoustic changed the endpoint name we are supposed to connect to? In our ipset config, we have an set for acoustic-transfer which does a lookup on transfer-campaign-us-4.goacoustic.com
It still works correctly with
transfer4.silverpop.com
which is what we have been using - maybe a deployment messed with the 4 - regardless we should probably confirm the correct on (@bsisolak ) & switch to it now we are discussion
That is the domain for SFTP (transfer-campaign-us-4.goacoustic.com), which resolves to 3.209.96.38. I don't know what transfer.silverpop.com is or where that came from. Does that answer the question?
Change #1111337 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Update omnimail-silverpop
Change #1111337 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Update omnimail-silverpop
OK - this seems to be working now - @nisrael - I pushed up last nights file & tonights' should go up in the next few hours - if all good we can close