We have seen this error on 2 bind servers, both Samba AD DCs, both virtualised on kvm. They are both in the same organisation but not the same site, and the other 5 in the organisation have not been impacted. All are at the same version (9.16.1-0ubuntu2.11), both stayed functional following that update for >1 month, both failed with a similar message but at different dates/times:
Nov 08 12:33:30 <server> kernel: isc-worker0001[3857097]: segfault at 8 ip 00007f1b2d75f166 sp 00007f1b2932a530 error 4 in libisc.so.1601.0.0[7f1b2d73d000+46000]
Nov 08 12:33:30 <server> kernel: Code: 00 00 48 8d 3d ab b4 02 00 e8 66 39 fe ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 4c 8b 67 10 <41> 83 7c 24 08 02 0f 85 be 00 00 00 49 89 fd 49 8b 7c 24 10 48 89
We have seen this error on 2 bind servers, both Samba AD DCs, both virtualised on kvm. They are both in the same organisation but not the same site, and the other 5 in the organisation have not been impacted. All are at the same version (9.16.1- 0ubuntu2. 11), both stayed functional following that update for >1 month, both failed with a similar message but at different dates/times:
Nov 08 12:33:30 <server> kernel: isc-worker0001[ 3857097] : segfault at 8 ip 00007f1b2d75f166 sp 00007f1b2932a530 error 4 in libisc. so.1601. 0.0[7f1b2d73d00 0+46000]
Nov 08 12:33:30 <server> kernel: Code: 00 00 48 8d 3d ab b4 02 00 e8 66 39 fe ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 4c 8b 67 10 <41> 83 7c 24 08 02 0f 85 be 00 00 00 49 89 fd 49 8b 7c 24 10 48 89