Hi Rob, I regularly see those "Database connection" events in rdimport.log files (nearly every time a new file appears in a dropbox directory). This is on Debian 8 (Jessie) running the Tryphon-packaged Rivendell version 2.10.3.
I also see similar messages from rdairplay on version 2.10.3 as well, but not nearly as often. Most frequently near midnight when the next day's log is loaded (with an explicit LL macro call, not a "chain to"). I had chalked it up to a bug in version 2.10.3, so it's interesting to know that you're experiencing it on a more recent version and on a different Linux distribution. ~David On 02/26/2017 10:04 PM, Rob Landry wrote: > > I've just installed RD 2.15.2 (compiled from source) on a new PC running > CentOS 6 (64-bit). > > When I start rdairplay and go to load a log, the name of the log appears > under Main Log at the bottom of the screen, as it should, but the log > never loads, and no events appear on the left or right half of the > rdairplay screen. > > rdairplay.log (I always set Rivendell to maintain separate log files) > shows: > > 26/02/2017 - 22:42:22.609 : Database connection failed : select > `bs_LOG`.ID,`bs_LOG`.CART_NUMBER,`bs_LOG`.START_TIME,`bs_LOG`.TIME_TYPE,`bs_LOG`.TRANS_TYPE,`bs_LOG`.START_POINT,`bs_LOG`.END_POINT,`bs_LOG`.SEGUE_START_POINT,`bs_LOG`.SEGUE_END_POINT,CART.TYPE,CART.GROUP_NAME,CART.TITLE,CART.ARTIST,CART.ALBUM,CART.YEAR,CART.LABEL,CART.CLIENT,CART.AGENCY,CART.USER_DEFINED,CART.CONDUCTOR,CART.SONG_ID,CART.FORCED_LENGTH,CART.CUT_QUANTITY,CART.LAST_CUT_PLAYED,CART.PLAY_ORDER,CART.ENFORCE_LENGTH,CART.PRESERVE_PITCH > ,`bs_LOG`.TYPE,`bs_LOG`.COMMENT,`bs_LOG`.LABEL,`bs_LOG`.GRACE_TIME,`bs_LOG`.POST_POINT,`bs_LOG`.SOURCE,`bs_LOG`.EXT_START_TIME,`bs_LOG`.EXT_LENGTH,`bs_LOG`.EXT_DATA,`bs_LOG`.EXT_EVENT_ID,`bs_LOG`.EXT_ANNC_TYPE,`bs_LOG`.EXT_CART_NAME,CART.ASYNCRONOUS,`bs_LOG`.FADEUP_POINT,`bs_LOG`.FADEUP_GAIN,`bs_LOG`.FADEDOWN_POINT,`bs_LOG`.FADEDOWN_GAIN,`bs_LOG`.SEGUE_GAIN,CART.PUBLISHER,CART.COMPOSER,CART.USAGE_CODE,CART.AVERAGE_SEGUE_LENGTH,`bs_LOG`.LINK_EVENT_NAME,`bs_LOG`.LINK_START_TIME,`bs_LOG`.LINK_LENGTH,`bs_LOG`.LINK_ID, > `bs_LOG`.LINK_EMBEDDED,`bs_LOG`.ORIGIN_USER,`bs_LOG`.ORIGIN_DATETIME,CART.VALIDITY, > `bs_LOG`.LINK_START_SLOP,`bs_LOG`.LINK_END_SLOP, > `bs_LOG`.DUCK_UP_GAIN,`bs_LOG`.DUCK_DOWN_GAIN,CART.START_DATETIME,CART.END_DATETIME,`bs_LOG`.EVENT_LENGTH,CART.USE_EVENT_LENGTH,CART.NOTES > from `bs_LOG` left join CART on `bs_LOG`.CART_NUMBER=CART.NUMBER order > by COUNT > 26/02/2017 - 22:42:22.610 : Database connection restored. > > I've never seen this behavior in rdairplay before. Why would the > database connection fail and then come back .02 seconds later? > > Weird, huh? > > > Rob > > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
