[mythtv-users] Recent fixes-35 intermittent backend crash

[Paul Gardiner]

On 05/05/2025 11:39, Stephen Worthington wrote:
> On Mon, 5 May 2025 10:58:24 +0100, you wrote:
> 
>> I see this crash - maybe once a month or so - always with the multiple
>> AutoExpire lines preceding. Anyone else seeing similar? How best should
>> I try to track this down?
>>
>> May 05 08:10:46 glidos mythbackend[1808]: 2025-05-05 08:10:46.428483 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 08:25:46 glidos mythbackend[1808]: 2025-05-05 08:25:46.440167 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 08:40:46 glidos mythbackend[1808]: 2025-05-05 08:40:46.451210 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 08:55:46 glidos mythbackend[1808]: 2025-05-05 08:55:46.461349 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 09:10:46 glidos mythbackend[1808]: 2025-05-05 09:10:46.471869 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 09:25:46 glidos mythbackend[1808]: 2025-05-05 09:25:46.483031 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 09:40:46 glidos mythbackend[1808]: 2025-05-05 09:40:46.494307 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 09:55:46 glidos mythbackend[1808]: 2025-05-05 09:55:46.505451 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 10:10:46 glidos mythbackend[1808]: 2025-05-05 10:10:46.516461 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 10:25:46 glidos mythbackend[1808]: 2025-05-05 10:25:46.527269 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 10:40:46 glidos mythbackend[1808]: 2025-05-05 10:40:46.537265 N
>> AutoExpire: CalcParams(): Max required Free Space: 4.0 GB w/freq: 15 min
>> May 05 10:46:39 glidos kernel: HTTP3[26847]: segfault at 3b3c55558 ip
>> 00007ff1e52e7908 sp 00007ff0ebffe5f0 error 4 likely on CPU 0 (core 0,
>> socket 0)
>> May 05 10:46:39 glidos kernel: Code: 81 08 01 00 00 4c 8d 70 10 48 63 50
>> 0c 48 63 40 08 48 c1 e2 03 48 c1 e0 03 4d 8d 3c 16 49 01 c6 48 39 c2 74
>> 21 0f 1f 44 00 00 <49> 8b 3e 48 89 de e8 3d 99 f6 ff 84 c0 75 88 49 83
>> c6 08 4d 39 f7
>> May 05 10:46:39 glidos systemd[1]: mythbackend.service: Main process
>> exited, code=dumped, status=11/SEGV
>> May 05 10:46:39 glidos systemd[1]: mythbackend.service: Failed with
>> result 'core-dump'.
>> May 05 10:46:39 glidos systemd[1]: mythbackend.service: Consumed 6min
>> 23.379s CPU time.
> 
> You really need a backtrace to figure out where it is happening.  If
> this is on Ubuntu, the MythTV programs in the Ubuntu packages are
> built with debug symbols, so there may be a backtrace automatically
> created in /var/crash.

Okay, thanks. I thought the way forward was likely something of that 
sort. Not Ubuntu, but I can build locally