If the log file (or system-image-cli -vv) ends with "Running group download reactor" it basically means that s-i has told udm to download a bunch of files, and it's waiting for the D-Bus signals indicating successful completion or failure. Since we're not seeing either of those, s-i will just sit and wait, although it will eventually time out.
There could be several reasons why udm is not responding, including networking problems anywhere along the path, or bugs. I don't know whether udm is being actively maintained. As an experiment, you could try `SYSTEMIMAGE_PYCURL=1 system-image-cli -vv` and see if you get different behavior. This bypasses udm and uses s-i's built-in cURL-based downloader. It's not recommended currently for production phone environments because it doesn't have the same networking behavior as udm, but this is essentially what's used in snappy. (Assuming of course that you're running s-i 3.0 or newer). If the cURL approach works, then it points to a problem in udm. If it doesn't work, you should at least get more diagnostics to help narrow it down to a problem in the networking, client, or server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508081 Title: Fails to receive OTA updates To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
