+++ Jeroen Massar [2013-01-13 06:42 -0000]: > > So it looks lot like aiccu dropped te connction during the upgrade. > > Replacing a package (and thus the binary) implies restarting AICCU to > get the new binary up and running. > > The only way to figure out what happened and what failed is to see the > log, which is not attached.
If/When I manage to get access to the machine again (hopefully soon) I will find the log and add it here. > > preserve connections wherever possible, > > Due to the restart of the binary, that is impossible. In these kind of > situations one could say to not upgrade tools like this remotely.... Yes. After more than a decade of remote upgrades 'just working' due to whatever magic ssh uses I forgot that this is actually a very tricky thing. It is the first time I have ever used aiccu to get to a remote box (useful because it does the NAT traversal through the router at the far end). > Note that the way that ssh "solves" this is to run an other binary on a > different port, OK. I don't understand how that is done transparently, but I guess I can read about it somewhere. > this is not possible with AICCU as it is actualy > providing the connectivity. > > The other work around is of course to use IPv4, at least as a backup, as > that connectivity is likely there; thus: ssh into the box using IPv6, > set up a reverse SSH over IPv4 as a backup connection (similar to the > SSH scenario where the alternative port SSH is the backup) and then get > into that one over IPv4 too to be sure to be able to survive the AICCU > restart. Right. I now know about this procedure and will indeed use it in future. I guess when we have native IPv6 then remote upgrades will not have this problem and will be at least as reliable as ipv4 ssh upgrades. > In the end though this is a non-bug mostly. Though there could maybe > be a huge warning, similar to the SSH case, to note to the user that > AICCU (and any other VPN tool like OpenVPN etc) is being used and that > it might be that that connection gets lost, in the same way as SSH. A warning would have helped me enormously. I did not notice aiccu in the list of 300MB of packages, but even if I had I probably wouldn't have thought about the connection-loss risk without a hint. I accept that this is not really a bug - or at best wishlist bug for a warning. This filing may help a few other people to avoid tripping over it. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099002 Title: Remote upgrade over aiccu connection failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1099002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
