[mythtv-users] hang playing in-progress recordings on 0.27

[Mark Perkins]

> On 2 Dec 2013, at 7:37 am, "Brian J. Murrell" <brian at interlinx.bc.ca> wrote:
> 
> After upgrading to 0.27, I'm finding that trying to play a recording
> that is still being recorded results in a hung frontend.  The frontend
> typically reports:
> 
> 2013-12-01 16:03:52.156289 I  TV: Creating TV object
> 2013-12-01 16:03:52.280977 N  Suspending idle timer
> 2013-12-01 16:03:52.296149 I  TV: Created TvPlayWindow.
> 2013-12-01 16:03:52.324760 I  TV: Attempting to change from None to WatchingRecording
> 2013-12-01 16:03:52.459859 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
> 2013-12-01 16:03:52.471896 E  MythSocket(130a600:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:02.655888 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 2 of 5)
> 2013-12-01 16:04:02.665474 E  MythSocket(1303b80:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:12.787156 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 3 of 5)
> 2013-12-01 16:04:12.798511 E  MythSocket(1303b80:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:22.864699 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 4 of 5)
> 2013-12-01 16:04:22.874390 E  MythSocket(1303b80:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:32.992001 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 5 of 5)
> 2013-12-01 16:04:33.002546 E  MythSocket(1303b80:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:33.002929 E  Connection to master server timed out.
>            Either the server is down or the master server settings
>            in mythtv-settings does not contain the proper IP address
> 
> 2013-12-01 16:04:33.002960 E  RemoteEncoder::Setup(): Failed to connect to backend
> 2013-12-01 16:04:33.434641 E  ALSA: snd_pcm_info_get_card: Operation not permitted
> 2013-12-01 16:04:33.497701 N  AudioPlayer: Enabling Audio
> 2013-12-01 16:04:36.953967 I  AFD: codec MP2 has 2 channels
> 2013-12-01 16:04:36.954392 I  AFD: Opened codec 0x6336240, id(MP2) type(Audio)
> 2013-12-01 16:04:37.220239 I  AFD: Opened codec 0x6334b00, id(MPEG2VIDEO) type(Video)
> 2013-12-01 16:04:37.220297 I  AOBase: Opening audio device 'pulse' ch 2(2) sr 48000 sf signed 16 bit reenc 0
> 2013-12-01 16:04:37.238174 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
> 2013-12-01 16:04:37.242508 E  MythSocket(674c660:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 2013-12-01 16:04:47.324642 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 2 of 5)
> 2013-12-01 16:04:47.336050 E  MythSocket(6334790:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
> 
> Eventually the frontend reports through an onscreen notification that it
> cannot connect the master backend server.
> 
> I'm happy to collect more info to help diagnose if somebody just wants
> to say what additional info would be useful for such a situation.
> 
> Cheers,
> b.
> 
> _______________________________________________
> 
Just to confirm - if you wait until the recording completes it does play correctly via the same frontend?