ok, it seems that you have a lot datasets created (by docker) and this is why ZSys is still timeouting:
1. You never remove stopped containers? (docker ps -a should show them) This is fixed by docker.io package https://launchpad.net/ubuntu/+source/docker.io/19.03.8-0ubuntu2 and any new install are not impacted. 2. What the docker package version you are on? However, I think the migration failed for you because you created another pool for docker (zpooldocker) and the zfs rename for the migration didn’t work. 3. I think docker isn’t able to restart your old containers that were created before your (this is a docker bug, mind filing it after confirming?) 4. If you docker rm the stopped containers, things will get better, but because of 3. you might need to do it manually for the datasets under rpool/ROOT/ubuntu_pzg8hb/var/lib/ (remember to keep dpkg, apt and AccountServices datasets, so don’t remove everything blindly). So yeah, the migration is a mitigation for people who jumped in, but it would be good to confirm this is your use case (creating the secondary pool prevented for our fix to work for you :)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882090 Title: "ERROR couldn't connect to zsys daemon: timed out waiting for server handshake" after every apt upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1882090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
