id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,mlocked 4094,SBE failed to reconnect after MBE reboot,Tony Lill ,Isaac Richards,"After re-booting the master backend, the slave backend failed to re-connect to the MBE. From the log it appears that it connected to itself. From looking at the code, this shouldn't happen because it should get the correct value from the settings cache. The cache only gets cleared around the call to update the schema. So if the first connection to the MBE socket happens before the schema upgrade happens, and it doesn't try again until it needs to reconnect after a failure, and the database is unavailable, then it would use the default of localhost. I'll turn on database logging and see if I can re-create it, but it would only happen if it tried to grab the value during the time when the database was offline. It might be an idea to reload the cache with the master's IP and port and maybe a few other key values after turning it back on, if I'm correct about the cause.",defect,closed,minor,0.22,mythtv,0.20-fixes,high,fixed,,,0