Re: panic at reboot - tsc_test_sync_ap

2022-12-14 Thread Scott Cheloha
On Wed, Dec 14, 2022 at 11:37:14AM +, Pedro Caetano wrote: > Hi bugs@ > > In the process of upgrading a pair of servers to release 7.2, the following > panic was triggered after sysupgrade reboot. (dell poweredge R740) > > One of the reboots happened before syspatch, the other happened after

Re: acme-client canary corrupted issue

2022-12-14 Thread Theo Buehler
> Try this ok tb > > Index: revokeproc.c > === > RCS file: /home/cvs/src/usr.sbin/acme-client/revokeproc.c,v > retrieving revision 1.19 > diff -u -p -r1.19 revokeproc.c > --- revokeproc.c 22 Nov 2021 08:26:08 - 1.19 >

Re: acme-client canary corrupted issue

2022-12-14 Thread Renaud Allard
On 12/14/22 15:56, Otto Moerbeek wrote: On Wed, Dec 14, 2022 at 03:51:44PM +0100, Renaud Allard wrote: On 12/14/22 14:44, Theo de Raadt wrote: sysctl kern.nosuidcoredump=3 mkdir /var/crash/acme-client and then try to reproduce, and see if a core file is delivered there. This coredump

Re: acme-client canary corrupted issue

2022-12-14 Thread Renaud Allard
On 12/14/22 15:56, Otto Moerbeek wrote: On Wed, Dec 14, 2022 at 03:51:44PM +0100, Renaud Allard wrote: On 12/14/22 14:44, Theo de Raadt wrote: sysctl kern.nosuidcoredump=3 mkdir /var/crash/acme-client and then try to reproduce, and see if a core file is delivered there. This coredump

Re: acme-client canary corrupted issue

2022-12-14 Thread Otto Moerbeek
On Wed, Dec 14, 2022 at 03:51:44PM +0100, Renaud Allard wrote: > > > On 12/14/22 14:44, Theo de Raadt wrote: > > sysctl kern.nosuidcoredump=3 > > > > mkdir /var/crash/acme-client > > > > and then try to reproduce, and see if a core file is delivered there. > > This coredump mechanism was

Re: acme-client canary corrupted issue

2022-12-14 Thread Renaud Allard
On 12/14/22 14:44, Theo de Raadt wrote: sysctl kern.nosuidcoredump=3 mkdir /var/crash/acme-client and then try to reproduce, and see if a core file is delivered there. This coredump mechanism was added to capture some hard-to-capture coredumps, you can see more info in core(5) and sysctl(3)

Re: acme-client canary corrupted issue

2022-12-14 Thread Otto Moerbeek
On Wed, Dec 14, 2022 at 12:30:25PM +0100, Renaud Allard wrote: > Hi Otto, > > > On 12/14/22 12:01, Otto Moerbeek wrote: > > On Tue, Dec 13, 2022 at 10:34:53AM +0100, Renaud Allard wrote: > > > > > Hello, > > > > > > I was force renewing some certs because I removed some domains from > > > the

Re: acme-client canary corrupted issue

2022-12-14 Thread Theo de Raadt
sysctl kern.nosuidcoredump=3 mkdir /var/crash/acme-client and then try to reproduce, and see if a core file is delivered there. This coredump mechanism was added to capture some hard-to-capture coredumps, you can see more info in core(5) and sysctl(3) Renaud Allard wrote: > Hi Otto, > > >

Re: acme-client canary corrupted issue

2022-12-14 Thread Renaud Allard
Hi Otto, On 12/14/22 12:01, Otto Moerbeek wrote: On Tue, Dec 13, 2022 at 10:34:53AM +0100, Renaud Allard wrote: Hello, I was force renewing some certs because I removed some domains from the cert, and got this: acme-client(53931) in free(): chunk canary corrupted 0xa06cb09db00 0xb0@0xb0 I

Re: acme-client canary corrupted issue

2022-12-14 Thread Otto Moerbeek
On Tue, Dec 13, 2022 at 10:34:53AM +0100, Renaud Allard wrote: > Hello, > > I was force renewing some certs because I removed some domains from > the cert, and got this: > acme-client(53931) in free(): chunk canary corrupted 0xa06cb09db00 0xb0@0xb0 > > I am using vm.malloc_conf=SUR>> > > Best