Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

myth backend crashing

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


gbr at majentis

May 1, 2012, 5:39 PM

Post #1 of 4 (604 views)
Permalink
myth backend crashing

Subject says it all. Dual Firewire inputs.


May 1 18:57:23 mythserver kernel: [ 279.172305] init: mythtv-backend main process (2259) killed by TERM signal
May 1 18:57:31 mythserver kernel: [ 287.038744] show_signal_msg: 39 callbacks suppressed
May 1 18:57:31 mythserver kernel: [ 287.038749] mythbackend[2260]: segfault at 6 ip b51d20ac sp bfde15b0 error 4 in libc-2.15.so[b515e000+19f000]
May 1 19:09:01 mythserver CRON[3089]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
May 1 19:17:01 mythserver CRON[3099]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 1 19:35:40 mythserver kernel: [ 2576.014126] mythbackend[2959]: segfault at eb8000c ip b52060d5 sp a97fea50 error 4 in libc-2.15.so[b5192000+19f000]
May 1 19:35:41 mythserver kernel: [ 2576.778301] init: mythtv-backend main process (2948) terminated with status 139
May 1 19:35:41 mythserver kernel: [ 2576.778325] init: mythtv-backend main process ended, respawning
May 1 19:36:54 mythserver kernel: [ 2649.675298] init: mythtv-backend main process (3716) killed by TERM signal

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

May 1, 2012, 9:41 PM

Post #2 of 4 (569 views)
Permalink
Re: myth backend crashing [In reply to]

On 05/01/2012 08:39 PM, Gerald Brandt wrote:
> Subject says it all. Dual Firewire inputs.
>
>
> May 1 18:57:23 mythserver kernel: [ 279.172305] init: mythtv-backend main process (2259) killed by TERM signal
> May 1 18:57:31 mythserver kernel: [ 287.038744] show_signal_msg: 39 callbacks suppressed
> May 1 18:57:31 mythserver kernel: [ 287.038749] mythbackend[2260]: segfault at 6 ip b51d20ac sp bfde15b0 error 4 in libc-2.15.so[b515e000+19f000]
> May 1 19:09:01 mythserver CRON[3089]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ]&& [ -d /var/lib/php5 ]&& find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
> May 1 19:17:01 mythserver CRON[3099]: (root) CMD ( cd /&& run-parts --report /etc/cron.hourly)
> May 1 19:35:40 mythserver kernel: [ 2576.014126] mythbackend[2959]: segfault at eb8000c ip b52060d5 sp a97fea50 error 4 in libc-2.15.so[b5192000+19f000]
> May 1 19:35:41 mythserver kernel: [ 2576.778301] init: mythtv-backend main process (2948) terminated with status 139
> May 1 19:35:41 mythserver kernel: [ 2576.778325] init: mythtv-backend main process ended, respawning
> May 1 19:36:54 mythserver kernel: [ 2649.675298] init: mythtv-backend main process (3716) killed by TERM signal
>

We'll need a backtrace as described at http://www.mythtv.org/wiki/Debugging

Thanks,
Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

May 1, 2012, 9:43 PM

Post #3 of 4 (568 views)
Permalink
Re: myth backend crashing [In reply to]

On 05/02/2012 12:41 AM, Michael T. Dean wrote:
> On 05/01/2012 08:39 PM, Gerald Brandt wrote:
>> Subject says it all. Dual Firewire inputs.
>>
>>
>> May 1 18:57:23 mythserver kernel: [ 279.172305] init:
>> mythtv-backend main process (2259) killed by TERM signal
>> May 1 18:57:31 mythserver kernel: [ 287.038744] show_signal_msg: 39
>> callbacks suppressed
>> May 1 18:57:31 mythserver kernel: [ 287.038749] mythbackend[2260]:
>> segfault at 6 ip b51d20ac sp bfde15b0 error 4 in
>> libc-2.15.so[b515e000+19f000]
>> May 1 19:09:01 mythserver CRON[3089]: (root) CMD ( [ -x
>> /usr/lib/php5/maxlifetime ]&& [ -d /var/lib/php5 ]&& find
>> /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin
>> +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \;
>> -delete)
>> May 1 19:17:01 mythserver CRON[3099]: (root) CMD ( cd /&&
>> run-parts --report /etc/cron.hourly)
>> May 1 19:35:40 mythserver kernel: [ 2576.014126] mythbackend[2959]:
>> segfault at eb8000c ip b52060d5 sp a97fea50 error 4 in
>> libc-2.15.so[b5192000+19f000]
>> May 1 19:35:41 mythserver kernel: [ 2576.778301] init:
>> mythtv-backend main process (2948) terminated with status 139
>> May 1 19:35:41 mythserver kernel: [ 2576.778325] init:
>> mythtv-backend main process ended, respawning
>> May 1 19:36:54 mythserver kernel: [ 2649.675298] init:
>> mythtv-backend main process (3716) killed by TERM signal
>>
>
> We'll need a backtrace as described at
> http://www.mythtv.org/wiki/Debugging

Actually, that's a TERM signal, not a crash... Someone is sending it a
signal saying to shut down.

Broken start script/process monitor/upstart/...?

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

May 1, 2012, 9:45 PM

Post #4 of 4 (568 views)
Permalink
Re: myth backend crashing [In reply to]

On 05/02/2012 12:43 AM, Michael T. Dean wrote:
> On 05/02/2012 12:41 AM, Michael T. Dean wrote:
>> On 05/01/2012 08:39 PM, Gerald Brandt wrote:
>>> Subject says it all. Dual Firewire inputs.
>>>
>>>
>>> May 1 18:57:23 mythserver kernel: [ 279.172305] init:
>>> mythtv-backend main process (2259) killed by TERM signal
>>> May 1 18:57:31 mythserver kernel: [ 287.038744] show_signal_msg:
>>> 39 callbacks suppressed
>>> May 1 18:57:31 mythserver kernel: [ 287.038749] mythbackend[2260]:
>>> segfault at 6 ip b51d20ac sp bfde15b0 error 4 in
>>> libc-2.15.so[b515e000+19f000]
>>> May 1 19:09:01 mythserver CRON[3089]: (root) CMD ( [ -x
>>> /usr/lib/php5/maxlifetime ]&& [ -d /var/lib/php5 ]&& find
>>> /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin
>>> +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \;
>>> -delete)
>>> May 1 19:17:01 mythserver CRON[3099]: (root) CMD ( cd /&&
>>> run-parts --report /etc/cron.hourly)
>>> May 1 19:35:40 mythserver kernel: [ 2576.014126] mythbackend[2959]:
>>> segfault at eb8000c ip b52060d5 sp a97fea50 error 4 in
>>> libc-2.15.so[b5192000+19f000]
>>> May 1 19:35:41 mythserver kernel: [ 2576.778301] init:
>>> mythtv-backend main process (2948) terminated with status 139
>>> May 1 19:35:41 mythserver kernel: [ 2576.778325] init:
>>> mythtv-backend main process ended, respawning
>>> May 1 19:36:54 mythserver kernel: [ 2649.675298] init:
>>> mythtv-backend main process (3716) killed by TERM signal
>>>
>>
>> We'll need a backtrace as described at
>> http://www.mythtv.org/wiki/Debugging
>
> Actually, that's a TERM signal, not a crash... Someone is sending it
> a signal saying to shut down.
>
> Broken start script/process monitor/upstart/...?

Ah, ignore that followup. mythbackend is crashing, but mythtv-backend
wrapper script is getting a TERM.

So, we're back to, "We'll need a backtrace as described at
http://www.mythtv.org/wiki/Debugging."

And seems I'm too tired to be replying to the list, so I need to get
some sleep.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.