[mythtv-users] Frequent backend crashes

jacek burghardt jaceksburghardt at gmail.com
Tue Apr 22 02:25:45 UTC 2014


Well I had fixed my mythbackend crashes under arch linux by deleting all
channels under setup  and re-downloading them from schedule direct.


On Mon, Apr 21, 2014 at 8:20 PM, Bryan Dagerman <bdagerman at gmail.com> wrote:

> My mythbackend process started crashing while sitting idle or during
> playback within the last week. It hasn't yet crashed while recording. The
> crash happens quite frequently, about every 45 minutes on average. This is
> the message from systemd when the crash happens:
>
> Apr 21 18:55:38 apollo mythbackend[16054]: 2014-04-21 18:55:38.055362 C
>>  MainServer::HandleVersion - Client speaks protocol version 8 but we speak
>> 77!
>> Apr 21 18:55:42 apollo mythbackend[16054]: 2014-04-21 18:55:42.272493 C
>>  MainServer::HandleVersion - Client speaks protocol version 8 but we speak
>> 77!
>> Apr 21 18:55:47 apollo mythbackend[16054]: 2014-04-21 18:55:47.491242 C
>>  MainServer::HandleVersion - Client speaks protocol version 8 but we speak
>> 77!
>> Apr 21 18:55:52 apollo mythbackend[16054]: (process:16054): GLib-ERROR
>> **: Creating pipes for GWakeup: Too many open files
>> Apr 21 18:55:52 apollo kernel: traps: mythbackend[19001] trap int3
>> ip:7faa5b8f9993 sp:7fa7aa76bb70 error:0
>> Apr 21 18:56:01 apollo systemd-coredump[19002]: Core too large, core will
>> not be stored.
>> Apr 21 18:56:01 apollo systemd-coredump[19002]: Process 16054
>> (mythbackend) dumped core.
>> Apr 21 18:56:02 apollo systemd[1]: mythbackend.service: main process
>> exited, code=killed, status=5/TRAP
>> Apr 21 18:56:09 apollo mythshutdown[19003]: Setting scheduled wakeup
>> time: Attempting to connect to master server...
>> Apr 21 18:56:10 apollo mythshutdown[19003]: Setting scheduled wakeup
>> time: Could not connect to master server!
>> Apr 21 18:56:10 apollo systemd[1]: mythbackend.service: control process
>> exited, code=exited status=1
>> Apr 21 18:56:10 apollo systemd[1]: Unit mythbackend.service entered
>> failed state.
>
>
> Googling the error hasn't provided much help. The client protocol message
> starts right after the backend starts, repeating every 5 or so seconds. I'm
> not sure if it is related or what client it is referring to. The frontend
> (on a different machine) is running  v0.27, network protocol 77. The
> backend displays the protocol message even when the frontend isn't running.
>
> I'm running Arch with the latest package updates. Here is the version
> report:
>
> mythbackend --version
>> Please attach all output as a file in bug reports.
>> MythTV Version : 317d5b7
>> MythTV Branch : tag: v0.27
>> Network Protocol : 77
>> Library API : 0.27.20130902-1
>> QT Version : 4.8.5
>> Options compiled in:
>>  linux profile use_hidesyms using_alsa using_oss using_pulse
>> using_pulseoutput using_backend using_bindings_perl using_bindings_python
>> using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun
>> using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec
>> using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_libudf
>> using_lirc using_mheg using_opengl using_opengl_video using_qtwebkit
>> using_qtscript using_qtdbus using_taglib using_v4l2 using_x11 using_xrandr
>> using_xv using_profiletype using_mythlogserver using_bindings_perl
>> using_bindings_python using_bindings_php using_mythtranscode using_opengl
>> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
>> using_libxml2 using_libudf
>
>
> Here is a typical log file, set on debug logtype.
> http://pastebin.com/awrgTixY
>
> Any help would be appreciated. I set up systemd to automatically restart
> the backend if it crashes. I'm hoping it doesn't start crashing during
> recording.
>
> Thanks
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140421/a174b5bd/attachment.html>


More information about the mythtv-users mailing list