Bad talloc magic value
Stefan.Paetow at jisc.ac.uk
Wed Jul 7 22:36:05 CEST 2021
Thank you very much!
Federated Roaming Technical Specialist
t: +44 (0)1235 822 125
xmpp: stefanp at jabber.dev.ja.net
In line with government advice, at Jisc we’re now working from home and our offices are currently closed. Read our statement on coronavirus <https://www.jisc.ac.uk/about/corporate/coronavirus-statement>.
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
On 06/07/2021, 12:59, "Freeradius-Users on behalf of Alan DeKok" <freeradius-users-bounces+stefan.paetow=jisc.ac.uk at lists.freeradius.org on behalf of aland at deployingradius.com> wrote:
On Jul 6, 2021, at 7:19 AM, Stefan Paetow via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
> I’m seeing a lot of crashes after upgrading to the NR packaged versions of FreeRADIUS 3.0.23:
> Tue Jul 6 03:46:10 2021 : Auth: (145) Login OK: [anonymous at realm] (from client roaming1 port 0 cli 70-6F-6C-69-73-68)
> Bad talloc magic value - unknown value
> talloc abort: Bad talloc magic value - unknown value
> Tue Jul 6 03:46:24 2021 : Info: Debugger not attached
> Tue Jul 6 03:46:24 2021 : Info: systemd watchdog is disabled
> 3.0.22 ran nicely, but now I’m concerned about 50 crashes with the above message since 3am this morning... Any ideas, gents? *looks at Arran, Alan and Matthew expectantly*
We have a patch into the v3.0.x branch. Matthew is looking to release updated packages for 3.0.23.
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users