Opened 6 years ago

Closed 6 years ago

#11217 closed Bug Report - Crash (Unverified)

mythtv-backend main process (31836) terminated with status

Reported by: brian@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Last night, without warning, my backend:

MythTV Version : v0.25.3
MythTV Branch : fixes/0.25
Network Protocol : 72
Library API : 0.25.20120506-1
QT Version : 4.8.1
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_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

exited with a status of 134, as reported by upstart.

There is nothing useful in the log indicating why this is:

Nov  1 20:30:01 pvr mythbackend[31837]: E CoreContext programinfo.cpp:2278 (GetPlaybackURL) ProgramInfo(3057_20121101203000.mpg): GetPlaybackURL: '3057_20121101203000.mpg' should be local, b
ut it can not be found.
Nov  1 20:30:01 pvr mythbackend[31837]: I TVRecEvent tv_rec.cpp:3503 (TuningCheckForHWChange) TVRec(18): HW Tuner: 18->18
Nov  1 20:30:01 pvr mythbackend[31837]: I RecThread tv_rec.cpp:3300 (RingBufferChanged) TVRec(24): RingBufferChanged()
Nov  1 20:30:01 pvr mythbackend[31837]: I CoreContext scheduler.cpp:637 (UpdateRecStatus) Updating status for "Storage Wars" on cardid 24 (Recording => Recorded)
Nov  1 20:30:02 pvr mythbackend[31837]: I RecThread recordinginfo.cpp:1113 (FinishedRecording) Finished recording Storage Wars: channel 1025
Nov  1 20:30:13 pvr mythbackend[25077]: C thread_unknown mythcommandlineparser.cpp:2534 (ConfigureLogging) mythbackend version: fixes/0.25 [v0.25.3] www.mythtv.org
Nov  1 20:30:13 pvr mythbackend[25077]: C thread_unknown mythcommandlineparser.cpp:2536 (ConfigureLogging) Qt version: compile: 4.8.1, runtime: 4.8.1
Nov  1 20:30:13 pvr mythbackend[25077]: N thread_unknown mythcommandlineparser.cpp:2538 (ConfigureLogging) Enabled verbose msgs:  general

According to apt-get policy, I do have the latest 0.25 packages installed. I am reluctant to go around upgrading to 0.26 at the moment and will wait a while while the early-adopters shake out the bugs. :-/

Any thoughts as to why this might have happened?

Change History (4)

comment:1 Changed 6 years ago by paulh

Status: newinfoneeded_new

Brian, has this problem reoccurred since?

Assuming upstart is reporting the exit code from the mythbackend then exit code 134 is GENERIC_EXIT_DB_ERROR so for some reason the backend had a problem executing a database query but the log snipped doesn't show any database errors.

comment:2 Changed 6 years ago by sphery

If it exited without warning, it's probably a crash from an abort, and we would need a proper backtrace ( http://www.mythtv.org/wiki/Debugging ) of the abort to see if it's code we can fix (since MythTV doesn't generally use aborts, the abort is probably in a library, such as ffmpeg). It could have been caused, for example, by bad input video (due to a bad signal or whatever) that yielded corrupt video data for ffmpeg.

comment:3 Changed 6 years ago by brian@…

I don't think I have seen this since, no.

comment:4 Changed 6 years ago by sphery

Resolution: Unverified
Status: infoneeded_newclosed

Since it's not a recurring problem, and since it may not be possible to get a backtrace, I'm going to close this one. If you are able to obtain a backtrace or core dump of a similar crash, please open a new ticket with the additional information. Thanks for the report and for the quick response to the request for information.

Note: See TracTickets for help on using tickets.