Opened 6 years ago

Closed 5 years ago

#11976 closed Bug Report - Hang/Deadlock (Won't Fix)

trying to play recording in progress hangs frontend

Reported by: brian@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.27-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

When I try to play a recording that is currently in progress of being recorded the front-end hangs and reports that it lost contact with the master.

Output from -v playback:

2013-12-11 15:51:32.464176 I  TV: Creating TV object
2013-12-11 15:51:32.652797 I  TV: Finished creating TV object
2013-12-11 15:51:32.652810 I  TV: StartTV() -- begin
2013-12-11 15:51:32.652828 N  Suspending idle timer
2013-12-11 15:51:32.652839 I  TV: Init -- begin
2013-12-11 15:51:32.663764 I  TV: Created TvPlayWindow.
2013-12-11 15:51:32.664857 I  TV: DrawUnusedRects() -- begin
2013-12-11 15:51:32.664876 I  TV: DrawUnusedRects() -- end
2013-12-11 15:51:32.682351 I  TV: Init -- end
2013-12-11 15:51:32.682381 I  TV: tv->Playback() -- begin
2013-12-11 15:51:32.702227 I  TV: HandleStateChange(0) -- begin
2013-12-11 15:51:32.702248 I  TV: Attempting to change from None to WatchingRecording
2013-12-11 15:51:32.705468 I  FileRingBuf(/storage2/3015_20131211203200.mpg): OpenFile(/storage2/3015_20131211203200.mpg, 2000 ms)
2013-12-11 15:51:32.745380 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2013-12-11 15:51:32.749092 E  MythSocket(352f5e0:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
2013-12-11 15:51:42.891198 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 2 of 5)
2013-12-11 15:51:42.901016 E  MythSocket(35d2830:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported
2013-12-11 15:51:52.979440 I  MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 3 of 5)
2013-12-11 15:51:52.989269 E  MythSocket(35d2830:-1): Failed to connect to (10.75.22.2:6543) Operation on socket is not supported

So what could the Operation on socket is not supported be all about?

Change History (2)

comment:1 Changed 6 years ago by brian@…

So, this appears to be due to having an http_proxy environment setting.

But that is a valid setting in my network here. All machines MUST use the proxy, no exceptions.

It has been suggested that my network is "broken" because it doesn't have "transparent" proxies, but I completely reject this characterization. Applications are supposed to be able to work with non-transparent proxies defined using the http_proxy environment variable and every application that I use here does work that way. Mythfrontend is the only application that I have that is broken in this manner.

When 20 things work and 1 thing doesn't, all indications are that that 1 thing is the broken thing.

comment:2 Changed 5 years ago by JYA

Resolution: Won't Fix
Status: newclosed
Note: See TracTickets for help on using tickets.