Re: [vdr] VDR exited with status 134

[Ville Skyttä]

On Sunday 14 June 2009, Martin Gansser wrote:
> Hi,
>
> VDR 1.6.0 exited with status 134, when generating a iso-file with
> vdr-burn.
>
> system is Fedora 11 x86_64

Possibly a vdr-burn/boost compile/runtime mismatch.  
https://bugzilla.redhat.com/show_bug.cgi?id=505893


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR exited with status 134

[Martin Gansser]

Hi,

VDR 1.6.0 exited with status 134, when generating a iso-file with
vdr-burn.

system is Fedora 11 x86_64

installed rpm packages:
vdr-osdteletext-0.8.1-2.fc11.x86_64
vdr-burn-debuginfo-0.1.0-0.18.pre21.fc11.x86_64
vdr-1.6.0-21.fc11.x86_64
vdr-mp3-0.10.1-7.fc11.x86_64
vdr-devel-1.6.0-21.fc11.x86_64
vdr-text2skin-debuginfo-1.1-24.cvsext0.10.fc11.x86_64
vdr-skinsoppalusikka-debuginfo-1.6.4-1.fc11.x86_64
vdr-skinsoppalusikka-1.6.4-1.fc11.x86_64
vdr-mp3-debuginfo-0.10.1-7.fc11.x86_64
vdr-sudoku-0.3.4-2.fc11.x86_64
vdr-streamdev-debuginfo-0.3.4-3.fc11.x86_64
vdr-ttxtsubs-0.0.9-1.fc11.x86_64
vdrsync-0.1.3-14.PRE1.050322.fc11.noarch
vdr-ttxtsubs-debuginfo-0.0.9-1.fc11.x86_64
vdr-debuginfo-1.6.0-21.fc11.x86_64
vdr-tvonscreen-1.0.141-5.fc11.x86_64
vdr-femon-1.6.6-2.fc11.x86_64
vdr-osdteletext-debuginfo-0.8.1-2.fc11.x86_64
vdr-sudoku-debuginfo-0.3.4-2.fc11.x86_64
vdr-tvonscreen-debuginfo-1.0.141-5.fc11.x86_64
vdr-mplayer-0.10.1-7.fc11.x86_64
vdr-femon-debuginfo-1.6.6-2.fc11.x86_64
vdr-text2skin-1.1-24.cvsext0.10.fc11.x86_64
vdr-streamdev-server-0.3.4-3.fc11.x86_64
vdr-burn-0.1.0-0.18.pre21.fc11.x86_64
vdr-skins-20081124-5.fc11.noarch

/var/log/messages reports this message:

Jun 14 00:06:38 gecko vdr: [4824] burn: ISO_FILE=/film/Falling Down - Ein ganz
normaler Tag.iso
Jun 14 00:06:38 gecko runvdr: VDR exited with status 134, attempting restart

I set DAEMON_COREFILE_LIMIT=unlimited at 
end of /etc/sysconfig/vdr so that a core file could be dumped in /tmp.

# ulimit -c unlimited
set core dumps file size unlimited.

teling the kernel to become more verbose:

# echo "core.%e.%p" > /proc/sys/kernel/core_pattern

install all necessary debug files:
# debuginfo-install vdr-1.6.0-21.fc11.x86_64
vdr-burn-0.1.0-0.18.pre21.fc11.x86_64.

Debug the core file

[r...@gecko tmp]# gdb /usr/sbin/vdr ./core.vdr.4724 
GNU gdb (GDB) Fedora (6.8.50.20090302-23.fc11)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New Thread 4729]
[New Thread 4731]
[New Thread 4735]
[New Thread 4781]
[New Thread 4728]
[New Thread 4730]
[New Thread 4727]
[New Thread 4732]
[New Thread 4733]
[New Thread 4734]
[New Thread 4780]

warning: Can't read pathname for load map: Eingabe-/Ausgabefehler.
Reading symbols from /usr/lib64/libjpeg.so.62.0.0...Reading symbols from
/usr/lib/debug/usr/lib64/libjpeg.so.62.0.0.debug...done.
done.
Loaded symbols for /usr/lib64/libjpeg.so.62.0.0
Reading symbols from /lib64/libpthread-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libpthread-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libpthread-2.10.1.so
Reading symbols from /lib64/libdl-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libdl-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libdl-2.10.1.so
Reading symbols from /lib64/libcap.so.2.16...Reading symbols from
/usr/lib/debug/lib64/libcap.so.2.16.debug...done.
done.
Loaded symbols for /lib64/libcap.so.2.16
Reading symbols from /lib64/librt-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/librt-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/librt-2.10.1.so
Reading symbols from /usr/lib64/libfreetype.so.6.3.20...Reading symbols from
/usr/lib/debug/usr/lib64/libfreetype.so.6.3.20.debug...done.
done.
Loaded symbols for /usr/lib64/libfreetype.so.6.3.20
Reading symbols from /usr/lib64/libfontconfig.so.1.3.0...Reading symbols from
/usr/lib/debug/usr/lib64/libfontconfig.so.1.3.0.debug...done.
done.
Loaded symbols for /usr/lib64/libfontconfig.so.1.3.0
Reading symbols from /usr/lib64/libstdc++.so.6.0.11...Reading symbols from
/usr/lib/debug/usr/lib64/libstdc++.so.6.0.11.debug...done.
done.
Loaded symbols for /usr/lib64/libstdc++.so.6.0.11
Reading symbols from /lib64/libm-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libm-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libm-2.10.1.so
Reading symbols from /lib64/libgcc_s-4.4.0-20090506.so.1...Reading symbols from
/usr/lib/debug/lib64/libgcc_s-4.4.0-20090506.so.1.debug...done.
done.
Loaded symbols for /lib64/libgcc_s-4.4.0-20090506.so.1
Reading symbols from /lib64/libc-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libc-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libc-2.10.1.so
Reading symbols from /lib64/ld-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/ld-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/ld-2.10.1.so
Reading symbols from /lib64/libattr.so.1.1.0...Reading symbols from
/usr/lib/debug/lib64/libattr.so.1.1.0.debug...done.
done.
Loaded symbols for /lib64/libattr.so.1.1.0
Reading symbols from /lib64/libexpat.so.1.5.2...Reading symbols from
/usr/lib/debug/lib64/libexpat.so.1.5.2.

Re: [vdr] VDR exited with status 134

[Ville Skyttä]

On Monday 11 June 2007, Kartsa wrote:
> Ville Skyttä kirjoitti:
> >
> > If you wish to debug it further, uncomment
> > DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if
> > core dumps start to appear in /tmp.
>
> I'll give it a try. Would -t switch be helpfull with shutdown?

No idea, I've never used that switch myself.

One possibly way to find out if the abort is because of some plugin is to 
watch /var/log/messages when shutting down vdr and to see what the last 
output before "runvdr: VDR exited with status ..." is.  If it's not "vdr: 
[...] exiting" but rather "vdr: [...] stopping plugin: foo" or "vdr: [...] 
deleting plugin: foo", it's pretty likely that the foo plugin is somehow 
involved.

> I am compiling vdr my self mostly because I like Soppalusikka :) I think
> there was some other reason(s) as well but I can not recall what :)
> I had newer actually read the README.package and it was wery illuminating.
> Maybe I'll have to start using readymade packages and give up using
> Soppalusikka :(

I don't think soppalusikka (in case you're referring to the skin) requires any 
patches to vdr, so it should be usable and buildable with the packaged 
version too.  Some dirs are obviously a bit different than in the install 
instructions, but README.package and "rpm -ql vdr" should help with those.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR exited with status 134

[Kartsa]

Ville Skyttä kirjoitti:
> On Sunday 10 June 2007, Kartsa wrote:
>   
>> I've got fedora with runvdr from fedora vdr package and it tries to
>> restart VDR if exit code is something else than 0, 2 or 137. Sometimes
>> the exit code is 137 but most of the time it is 134. This causes VDR to
>> restart (or runvdr makes VDR to restart) and dvb drivers to reload.
>>
>> What does exit code 134 mean?
>> 
>
> >From "man bash":
> The return value of a simple command is its exit status, or 128+n if the 
> command is terminated by signal n.
>
> So 134 - 128 = 6, SIGABRT ("kill -l 6").  "info SIGABRT" says:
> This signal indicates an error detected by the program itself and reported by 
> calling `abort'.
>   
Ah, did not think of  that. Thanks.
>> Why is exit code sometimes 137 and most of the times 134?
>> 
>
> It's 137 when killproc (see /etc/init.d/functions) invoked 
> from /etc/init.d/vdr gets tired of waiting for "kill -TERM" to result in vdr 
> to shut down and issues a "kill -KILL" to really get rid of it.  It's 134 
> when you got a "crash" caused by SIGABRT.
>
> If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at 
> end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp.
>   
I'll give it a try. Would -t switch be helpfull with shutdown?
>> What should exit code be when VDR is shutting down either because the
>> user pushed power button or because there has been no user activity?
>> 
>
> 0 if all went well (and if I remember correctly).
>   
Seems that it never is 0. At least in my case. Maybe I'll try VDR with 
no plugins.
>> I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some
>> plugins not in fedora packaging).
>> 
>
> In my experience, crashes at vdr shutdown are almost always caused by plugin 
> bugs.  I'm not aware of any such in the Fedora plugin packages at the moment.
>
> By the way, which packaged plugins are you missing/adding?  The last 
> crash-at-shutdown bug I saw was in ttxtsubs; in case you're using it, my 
> patch for the crash is included in Rofa's "kermanekka" edition 
> (http://www.saunalahti.fi/~rahrenbe/vdr/patches/, Fedora 7 packages at 
> http://cachalot.mine.nu/ and possibly sometime soonish in Fedora proper).
>   
I am using ttxtsubs. I do not actually need it more than occasionally 
because I have no channels witch uses this subtitling system. Maybe I 
could try without it.
> Also, just in case you weren't aware of it, if your additional plugins don't 
> require patching vdr itself (patches for subtitles and ttxtsubs plugins are 
> already included), you can use Fedora's vdr and vdr-devel packages and build 
> additional plugins for it instead of building a whole vdr of your own, 
> see /usr/share/doc/vdr-*/README.package
>   
I am compiling vdr my self mostly because I like Soppalusikka :) I think 
there was some other reason(s) as well but I can not recall what :)
I had newer actually read the README.package and it was wery illuminating.
Maybe I'll have to start using readymade packages and give up using  
Soppalusikka :(


\\Kartsa

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR exited with status 134

[Ville Skyttä]

On Sunday 10 June 2007, Kartsa wrote:

> I've got fedora with runvdr from fedora vdr package and it tries to
> restart VDR if exit code is something else than 0, 2 or 137. Sometimes
> the exit code is 137 but most of the time it is 134. This causes VDR to
> restart (or runvdr makes VDR to restart) and dvb drivers to reload.
>
> What does exit code 134 mean?

>From "man bash":
The return value of a simple command is its exit status, or 128+n if the 
command is terminated by signal n.

So 134 - 128 = 6, SIGABRT ("kill -l 6").  "info SIGABRT" says:
This signal indicates an error detected by the program itself and reported by 
calling `abort'.

> Why is exit code sometimes 137 and most of the times 134?

It's 137 when killproc (see /etc/init.d/functions) invoked 
from /etc/init.d/vdr gets tired of waiting for "kill -TERM" to result in vdr 
to shut down and issues a "kill -KILL" to really get rid of it.  It's 134 
when you got a "crash" caused by SIGABRT.

If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at 
end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp.

> What should exit code be when VDR is shutting down either because the
> user pushed power button or because there has been no user activity?

0 if all went well (and if I remember correctly).

> I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some
> plugins not in fedora packaging).

In my experience, crashes at vdr shutdown are almost always caused by plugin 
bugs.  I'm not aware of any such in the Fedora plugin packages at the moment.

By the way, which packaged plugins are you missing/adding?  The last 
crash-at-shutdown bug I saw was in ttxtsubs; in case you're using it, my 
patch for the crash is included in Rofa's "kermanekka" edition 
(http://www.saunalahti.fi/~rahrenbe/vdr/patches/, Fedora 7 packages at 
http://cachalot.mine.nu/ and possibly sometime soonish in Fedora proper).

Also, just in case you weren't aware of it, if your additional plugins don't 
require patching vdr itself (patches for subtitles and ttxtsubs plugins are 
already included), you can use Fedora's vdr and vdr-devel packages and build 
additional plugins for it instead of building a whole vdr of your own, 
see /usr/share/doc/vdr-*/README.package

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR exited with status 134

[Kartsa]

Most of the time when VDR shuts the box down using vdrshutdown script 
there is a line in the log
runvdr: VDR exited with status 134, attempting restart

I've got fedora with runvdr from fedora vdr package and it tries to 
restart VDR if exit code is something else than 0, 2 or 137. Sometimes 
the exit code is 137 but most of the time it is 134. This causes VDR to 
restart (or runvdr makes VDR to restart) and dvb drivers to reload.

What does exit code 134 mean?
Why is exit code sometimes 137 and most of the times 134?
What should exit code be when VDR is shutting down either because the 
user pushed power button or because there has been no user activity?

I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some 
plugins not in fedora packaging).

\\Kartsa

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr