mythbuntu 16.04 w/ mythtv 0.28 crash

[heidebock]

Hi, I've seen a couple of posts on this topic but with no resolution:
Mythbuntu 16.04 running 0.28 mythtv w. Ceton Infinitv4 tuner - backend/frontend/mythweb all running on same box. I can play video from my Ceton card just fine w/
"cat /dev/ceton/ctn91xx_mpeg0_0 | mplayer -cache 8192 -" - the card seems to be recognized by the system.

As soon as I try to watch tv from the front-end or a recording begins which was set via mythweb, then the entire box freezes. No logs show anything - I've looked at the Kernel log, syslog, & myth(front|back)end logs. There is no indication of what's going on, etc.

Here's an example of the last thing in /var/log/mythtv/mythbackend.log:

Oct 15 22:22:08 mythdruid-bo mythbackend: mythbackend[5260]: I CetonStreamHandler recorders/iptvstreamhandler.cpp:125 (run) IPTVSH(::-1): run()
Oct 15 22:22:08 mythdruid-bo mythbackend: mythbackend[5260]: I Scheduler scheduler.cpp:2821 (HandleRecordingStatusChange) Tuning recording: "Masterpiece Mystery!":"Sherlock, Series II: The Reichenbach Fall": channel 1658 on cardid 1, sourceid 1
Oct 15 22:22:08 mythdruid-bo mythbackend: mythbackend[5260]: I CetonStreamHandler recorders/cetonrtsp.cpp:413 (Setup) CetonRTSP: Transport: RTP/AVP;unicast;client_port=58213-58214

I'm beginning to think this has something to do w/ the ceton recorders being set up for RTP but at this point I'm speculating. Does anyone know how to work around this problem?

thanks!
heidebock

[bill6502]

I believe the default for *buntu is to double log in journal and syslog. But, I'd try
using journalctl to check. Or, grep ForwardTo /etc/systemd/journald.conf .

Just to get more attention, I'd edit the original post here and add Ceton (and
probably change crash to freeze.) I don't have the card, so can't offer much.

You can also look in the list archives here: https://lists.gt.net/mythtv/users/ .
I did, but didn't spot anything.

Interesting comment here: https://www.mythtv.org/wiki/Ceton#Create_the_Recorders
that may support your RTP speculation.

Finally, starting the backend with -v record:debug may add clues in mythbackend.log.
Or you can do that to the running backend with:

Code: Select all

mythbackend --setverbose record:debug

[pgbennett]

I have the ceton eth-6 which works entirely off the network and cannot stream anything to mplayer.
Perhaps the network interface for your ceton is not working. Do you have the correct drivers for it?

What I do with the eth-6, is navigate to the ceton web page, in my case http://192.168.0.193/ . In the page you can click on a tuner number, click the "tuner" tab, set a channel number and click "set channel". Then you can click the "status" tab for the tuner to see if it is tuned or is copy protected.

I don't know if this will be of any help with the internal model ceton. If you cannot get to the web page, maybe that is an indication of problems. MythTV sends commands to to ceton via http, so if http or the ceton network interface is not working MythTV will not be able to record with it.