mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

The other possible change might be making a sysctl change because
mythbackend runs suid

sudo sysctl -w fs.suid_dumpable=2



On Mon, Nov 5, 2012 at 6:04 PM, Mario Limonciello <superm1@xxxxxxxxxx>wrote:

> I believe there was some sort of problem starting in 0.24 that the ulimit
> needs to be raised to allow the process to core dump
>
> If you add this to the upstart script:
>
> ulimit -c unlimited
>
>
> that will allow mythbackend to do core dumps.  I'm unsure of the security
> implications of this though (there might be some).
>
> On Wed, Oct 31, 2012 at 10:09 AM, Brian J. Murrell <brian@xxxxxxxxxxxxxxx>wrote:
>
>> On 12-10-31 10:40 AM, Thomas Mashos wrote:
>> > Shouldn't the crash file already be written to /var/crash/  ?
>>
>> Interesting point.  It doesn't seem to be the case however.  Given this
>> segfault:
>>
>> Oct 30 22:00:03 pvr kernel: [1937721.428406] mythbackend[13502]:
>> segfault at 28 ip 0620ef91 sp b2ffe140 error 4 in
>> libQtCore.so.4.8.1[607d000+2d4000]
>>
>> There was nothing in /var/crash about it.
>>
>> However given a different segfault:
>>
>> Oct 29 16:02:05 pvr kernel: [1829843.051149] mythcommflag[2020]:
>> segfault at b37fb3f4 ip 080626cc sp bfa4d1f0 error 4 in
>> mythcommflag[8048000+6e000]
>>
>> There is indeed a:
>>
>> -rw-r-----  1 mythtv mythtv 11878631 Oct 29 16:02
>> _usr_bin_mythcommflag.103.crash
>>
>> So what's different about these processes and why one's segfault is
>> being caught by apport and the other is not?
>>
>> --
>> You received this bug notification because you are a member of Mythbuntu
>> Bug Team, which is subscribed to mythtv in Ubuntu.
>> https://bugs.launchpad.net/bugs/1073580
>>
>> Title:
>>   mythtv-backend needs to run in writable directory
>>
>> Status in “mythtv” package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   The mythtv-backend process needs to be run in a directory that it can
>>   write into, ~mythtv for example.  This is required so that a core file
>>   can be collected if/when it segfaults -- like it has been doing here.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 12.04
>>   Package: mythtv-backend
>> 2:0.25.2+fixes.20121002.139bd59-0ubuntu0mythbuntu4 [origin:
>> LP-PPA-mythbuntu-0.25]
>>   ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
>>   Uname: Linux 3.2.0-31-generic i686
>>   .var.log.mythtv.mythavtest.log:
>>
>>   .var.log.mythtv.mythbackend.log:
>>
>>   .var.log.mythtv.mythccextractor.log:
>>
>>   .var.log.mythtv.mythcommflag.log:
>>
>>   .var.log.mythtv.mythfrontend.log:
>>
>>   .var.log.mythtv.mythjobqueue.log:
>>
>>   .var.log.mythtv.mythlcdserver.log:
>>
>>   .var.log.mythtv.mythmediaserver.log:
>>
>>   .var.log.mythtv.mythmetadatalookup.log:
>>
>>   .var.log.mythtv.mythpreviewgen.log:
>>
>>   .var.log.mythtv.mythshutdown.log:
>>
>>   .var.log.mythtv.mythtranscode.log:
>>
>>   .var.log.mythtv.mythtv.setup.log:
>>
>>   .var.log.mythtv.mythutil.log:
>>
>>   .var.log.mythtv.mythwelcome.log:
>>
>>   ApportVersion: 2.0.1-0ubuntu13
>>   Architecture: i386
>>   CrashDB: mythbuntu
>>   Date: Wed Oct 31 10:07:13 2012
>>   Installed_mythtv_dbg: 2:0.25.2+fixes.20121002.139bd59-0ubuntu0mythbuntu4
>>   ProcEnviron:
>>    TERM=xterm
>>    PATH=(custom, no user)
>>    LANG=en_CA.UTF-8
>>    SHELL=/bin/bash
>>   SourcePackage: mythtv
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   modified.conffile..etc.logrotate.d.mythtv.backend: [modified]
>>   mtime.conffile..etc.init.mythtv.backend.conf: 2012-10-31T10:05:57
>>   mtime.conffile..etc.logrotate.d.mythtv.backend: 2012-06-04T22:15:10
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1073580/+subscriptions
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~mythbuntu-bugs
>> Post to     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Mario Limonciello
> superm1@xxxxxxxxx
>



-- 
Mario Limonciello
superm1@xxxxxxxxx