Thank you Andreas. I completed SRU verification for Jammy: Test environment:
- Jammy VM (Ubuntu 22.04.5 LTS) With chrony 4.2-2ubuntu2, I stopped chronyd and started waitsync: ubuntu@chrony-verify:~$ sudo strace -e trace=connect,socket,write chronyc waitsync 0 0.1 0.0 0.1 506 Cannot talk to daemon 506 Cannot talk to daemon ... waitsync kept reporting '506 Cannot talk to daemon'. Starting chronyd did not recover the existing waitsync process. I then installed chrony 4.2-2ubuntu2.1 from jammy-proposed and repeated the test. After chronyd was started, waitsync exited successfully: ubuntu@chrony-verify:~$ sudo apt update ubuntu@chrony-verify:~$ sudo apt install -y chrony=4.2-2ubuntu2.1 ubuntu@chrony-verify:~$ sudo strace -e trace=connect,socket,write chronyc waitsync 0 0.1 0.0 0.1 506 Cannot talk to daemon 506 Cannot talk to daemon ... try: 66, refid: 00000000, correction: 0.000000000, skew: 0.000 try: 67, refid: 00000000, correction: 0.000000000, skew: 0.000 ... try: 133, refid: 6D3D6D8C, correction: 0.001611474, skew: 1000000.000 ubuntu@chrony-verify:~$ echo $? 0 The proposed package fixes the issue on Jammy. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165114 Title: chronyc fails to reconnect to chronyd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2165114/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
