I am upgrading host from MIAB 65 → 67 and the installer is just sitting at Mail-in-a-Box Version: v67.
I do not see any output - is this normal and is it taking awhile to do this? It has been sitting for about 5 minutes at this prompt in the terminal window.
After about 15 minutes the following was dumped onscreen:
FAILED: add-apt-repository -y ppa:duplicity-team/duplicity-release-git
-----------------------------------------
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in <module>
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, in __init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 429, in _request
raise error
lazr.restfulclient.errors.ServerError: HTTP Error 504: Gateway Time-out
Response headers:
---
-content-encoding: gzip
cache-control: no-cache
content-length: 92
content-type: text/html
date: Sat, 23 Mar 2024 16:09:05 GMT
server: Apache/2.4.41 (Ubuntu)
status: 504
vary: Accept-Encoding
---
Response body:
---
b"<html><body><h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n</body></html>\n"
---
Not sure what the state of the v67 install/upgrade is at this point.
Tried a fresh install of v67 on a new host and got the following output from the installer:
FAILED: add-apt-repository -y ppa:duplicity-team/duplicity-release-git
-----------------------------------------
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in <module>
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/add-apt-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, in __init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 429, in _request
raise error
lazr.restfulclient.errors.ServerError: HTTP Error 503: Service Unavailable
Response headers:
---
-content-encoding: gzip
connection: close
content-length: 2155
content-type: text/html
date: Sat, 23 Mar 2024 16:25:05 GMT
server: Apache/2.4.41 (Ubuntu)
status: 503
vary: Accept-Encoding
---
Response body:
---
b'<!DOCTYPE html>\n<html\n xmlns="http://www.w3.org/1999/xhtml"\n xml:lang="en"\n lang="en"\n>\n<head>\n <title>Launchpad is temporarily unavailable</title>\n <link\n type="text/css" rel="stylesheet" media="screen, print"\n href="https://launchpad.net/+icing/basic-error.css" />\n</head>\n<body>\n <div class="page-center-wrap">\n <div class="page-center">\n <div class="page-center-content">\n <div id="header">\n <div class="graphic">\n :(\n </div>\n <div class="content">\n <!-- Before editing, please see\n https://bugs.launchpad.net/bugs/475371, especially comment #2,\n for details on this file. In particular, please maintain the\n \\r\\n line endings, at least for the HTTP header lines. -->\n <h1>Uh oh!</h1>\n <h2>Something has gone wrong. We\'re sorry!</h2>\n <p>\n If we are in the middle of an update, Launchpad will be\n back in a couple of minutes. Otherwise, we are working to\n fix the unexpected problems. Check\n <a href="https://twitter.com/launchpadstatus">@launchpadstatus</a>\n on Twitter or\n <a href="https://ubuntu.social/@launchpadstatus">@launchpadstatus@ubuntu.social</a>\n on Mastodon for updates.\n </p>\n <p>\n If the problem persists, let us know in\n <a href="irc://irc.libera.chat/#launchpad"\n >the #launchpad IRC channel on libera.chat</a>.\n </p>\n <p class="sub">\n Technically, the load balancer took too long to connect to\n an application server.\n </p>\n <p><a href="javascript:window.location.reload()">Reload</a>\n this page or try again in a few minutes</p>\n </div>\n </div>\n <div id="footer">\n <a href="https://launchpad.net/">\n <img src="https://launchpad.net/@@/launchpad-logo-and-name.png"\n width="100"\n alt="Launchpad" />\n </a>\n </div>\n </div>\n </div>\n </div>\n</body>\n</html>\n'
It looks like new installs are not working either.
It seems to be having trouble with something regarding the duplicity PPA. Did you by chance make any custom changes to your server back when we were having problems with the duplicity backup software?
On the surface, it looks like a network connectivity problem to me. The service you’re trying to contact is unavailable, or you’re being blocked by the service, or…?