Mythfilldatabase errors, unable to connect to backend

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

Post Reply
MythicalManMonth
Newcomer
Posts: 3
Joined: Sun Sep 09, 2018 7:29 pm

Mythfilldatabase errors, unable to connect to backend

Post by MythicalManMonth » Sun Sep 09, 2018 11:11 pm

My backend died and I had to reinstall; I downloaded the 16.04 ISO and went through the install process, then installed all of the updates and configured. I appear to have almost everything running - but I have no guide data, and running MythFillDatabase generates errors. Here is my MythTV version

Sep 9 16:39:40 Hollywood mythbackend: mythbackend[1085]: C thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) mythbackend version: fixes/0.28 [v0.28.2-6-g9031599]

I can't copy/paste from the window in which the Mythfilldatabase logs appear, but here are what appear to be the most important lines:
I dbSchema 1344
I Connecting to backend server: 192.168.3.203:6543
E Failed to connect to (127.0.0.1:6543) Connection refused
I No channels are configured to use the grabber

The mythfilldatabase log file contains no errors, but neither is it current - the last entries are from yesterday, and I have run Mythfilldatabase several times today.

Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext schemawizard.cpp:120 (Compare) Current MythTV Schema Version (DBSchemaVer): 1344
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext mythcorecontext.cpp:436 (ConnectCommandSocket) MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.3.203:6543 (try 1 of 1)
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext mythcorecontext.cpp:1578 (CheckProtoVersion) MythCoreContext::CheckProtoVersion(): Using protocol version 88 XmasGift
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext main.cpp:311 (main) Opening blocking connection to master backend
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext filldata.cpp:569 (Run) Updating source #1 (Antenna) with grabber schedulesdirect1
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext filldata.cpp:588 (Run) No channels are configured to use grabber.
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext filldata.cpp:212 (GrabDDData) Retrieving datadirect data.
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext filldata.cpp:215 (GrabDDData) Grabbing ALL available data.
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1172 (GrabData) DataDirect: Grabbing listing data
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1023 (DDPost) Downloading DataDirect feed
Sep 8 17:05:37 Hollywood mythfilldatabase: mythfilldatabase[2562]: I LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1035 (DDPost) Downloaded 2127416 bytes
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1037 (DDPost) Uncompressing DataDirect feed
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1042 (DDPost) Uncompressed to 26074849 bytes
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:1048 (DDPost) Writing to temporary file: [/tmp/mythtv_ddp_QSQSjg/mythtv_ddp_ysN3Ul]
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext mythdbcon.cpp:449 (getStaticCon) New static DB connectionDataDirectCon
Sep 8 17:05:59 Hollywood mythfilldatabase: mythfilldatabase[2562]: I CoreContext datadirect.cpp:464 (characters) DataDirect: Your subscription expires on Sun Jun 9 2019 10:55 PM

Sysctrl confirms that the backend is running, and the IP address that mythfilldatabase is using matches what is shown by ifconfig. What should be my next troubleshooting steps?

Post Reply