[mythtv-users] /find_orphans.py crashes mythbackend

[Udo van den Heuvel]

On 02-09-16 16:03, Stuart Auchterlonie wrote:
> How do you prove that without a backtrace, or at very least an
> strace showing that the return code from a system call indicated
> the out of file descriptor condition?

Huh?
If the backend (!) logs in /var/log/messages:

/var/log/messages-20160821:Aug 30 08:57:27 recorder mythbackend:
(process:1905): GLib-ERROR **: Creating pipes for GWakeup: Too many open
files
/var/log/messages-20160821:Aug 30 08:57:27 recorder mythbackend:
(process:1905): GLib-ERROR **: Creating pipes for GWakeup: Too many open
files
/var/log/messages-20160821:Aug 30 08:57:27 recorder mythbackend:
(process:1905): GLib-ERROR **: Creating pipes for GWakeup: Too many open
files
/var/log/messages-20160821:Sep  1 17:15:24 recorder mythbackend:
(process:12476): GLib-ERROR **: Creating pipes for GWakeup: Too many
open files
/var/log/messages-20160821:Sep  1 17:20:51 recorder mythbackend:
(process:28205): GLib-ERROR **: Creating pipes for GWakeup: Too many
open files
/var/log/messages-20160821:Sep  1 17:31:15 recorder mythbackend:
(process:29226): GLib-ERROR **: Creating pipes for GWakeup: Too many
open files

Who am I to doubt it's utterings?
You do doubt the backend.

If you doubt the code itself, while more or less defending it by putting
the work on my side, then what am I to think in this simple situation?

That the code is not very stable? That the error messages cannot be
trusted? That logic is not enough to debug this thing?

Well then.
I did a few of the very same thing:
I tried to delete 4000+ orphaned recordings via find_orphans.
Every time the backend would stop being a process. Exit. Vanish. Go away.
Every time it logged the irrelevant messages that I pasted a few lines
above this one.
I do not see any relation between these things but I want them to go away.
Maybe you want them to go away as well because another user might run
into the same stuff and be not so handy with sql and a tiny bit of shell
magic.

Udo