[mythtv-users] mythbackend keeps crashing

[Hika van den Hoven]

Hoi Gabe,

Sunday, March 9, 2014, 8:36:26 PM, you wrote:

> mainserver.cpp:6221 (reconnectTimeout) - Connecting to master server: 192.168.1.101:6543
> 2014-03-09 12:31:33.300888 N [1643/1643] CoreContext
> mainserver.cpp:6231 (reconnectTimeout) - Connected successfully
> 2014-03-09 12:32:03.331591 E [1643/1681] MythSocketThread(-1)
> mythsocket.cpp:790 (ReadStringListReal) - MythSocket(1c47fc0:34):
> ReadStringList: Error, timed out after 30000 ms.
> 2014-03-09 12:32:03.331740 W [1643/1681] MythSocketThread(-1)
> mainserver.cpp:5933 (connectionClosed) - MainServer: Unknown socket closing MythSocket(0x1c47fc0)
> 2014-03-09 12:32:03.331869 E [1643/1643] CoreContext
> mythsocket.cpp:353 (SendReceiveStringList) - MythSocket(1c47fc0:-1): No response.
> 2014-03-09 12:32:03.331894 E [1643/1643] CoreContext
> mainserver.cpp:6268 (reconnectTimeout) - MainServer: Failed to open master server socket, timeout
> 2014-03-09 12:32:03.337658 I [1643/1673] ProcessRequest
> mainserver.cpp:1472 (HandleAnnounce) - adding: Mythbox as a slave backend server
> 2014-03-09 12:32:03.337748 E [1643/1681] MythSocketThread(31)
> mythsocket.cpp:685 (WriteStringListReal) - MythSocket(1c7a970:-1):
> WriteStringList: Error, called with unconnected socket.
> 2014-03-09 12:32:04.332923 N [1643/1643] CoreContext
> mainserver.cpp:6221 (reconnectTimeout) - Connecting to master server: 192.168.1.101:6543
> 2014-03-09 12:32:04.333618 N [1643/1643] CoreContext
> mainserver.cpp:6231 (reconnectTimeout) - Connected successfully
> 2014-03-09 12:32:34.365553 E [1643/1694] MythSocketThread(-1)
> mythsocket.cpp:790 (ReadStringListReal) - MythSocket(1c7a970:34):
> ReadStringList: Error, timed out after 30000 ms.
> 2014-03-09 12:32:34.365866 E [1643/1643] CoreContext
> mythsocket.cpp:353 (SendReceiveStringList) - MythSocket(1c7a970:-1): No response.
> 2014-03-09 12:32:34.366004 E [1643/1643] CoreContext
> mainserver.cpp:6268 (reconnectTimeout) - MainServer: Failed to open master server socket, timeout

I also see it trying to connect to 192.168.1.101:6543 and failing to
build a socket. I that maybe the old IP.




Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens
--