Thanks Wayne, Absolutely spot on with that info. Are there any other tables I'm likely to run into issue with?
On 26 January 2013 20:04, waynemerricks <[email protected]>wrote: > Sounds like the Innodb problem. In the newer versions of MySQL innodb > becomes the standard db engine. This has issues because the row byte > length can't support the full row of grid clocks. Check the SQL for the > SERVICES table and see whether its set to Innodb or not. > > If it is dump the table, change the innodb bit to myisam then drop and > reimport the table. > > > On 2013-01-26 18:42, Jay Eames wrote: > > Hi guys, > > > > II am having a bit of a problem with a fresh install of Rivendell, > > using the latest ubuntu packages. > > > > As I was creating a new grid, I got half way through assigning > > clocks, > > when I started receiving these messages: > > > > invalid SQL or failed DB connection: update SERVICES set CLOCK89="" > > where NAME="Main Service" > > Database connection failed: update SERVICES set CLOCK89="" > > where NAME="Main Service" > > Database connection restored. > > > > I now cannot assign clocks to the grid at all. > > > > The clock was successfully used on previous grid slots without issue. > > Nothing was changed between it working and it not. I have rebooted > > etc, but still no luck. > > > > Any ideas? > > > > Jay > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > -- There are 2 kinds of people in the world; Those who can extrapolate from incomplete data
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
