Yeah, I've ran in to this before as well. Which raises a point: why are service grids stored with clock names instead of IDs?
On Wed, Dec 4, 2013 at 4:13 PM, Pedro Picoto <[email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > *I suffered the same a few weeks ago. Wayne Merricks suggested me this: > Check that your SERVICES table is set to MyISAM and not INNODB (which is > the default I think in Mysql 5.5+) $ mysql -h rivserver_ip_or_name -u root > -p $> use Rivendell; $> show create table SERVICES; You'll get a big mess > of SQL splurged out, scroll down to here: `CLOCK166` char(64) DEFAULT NULL, > `CLOCK167` char(64) DEFAULT NULL, PRIMARY KEY (`NAME`) ) ENGINE=MyISAM > DEFAULT CHARSET=latin1 | If its not MyISAM try this: $> alter table > SERVICES ENGINE=MyISAM; Then redo your grids and see if it sticks. * > *It worked!* > > Backup the DB prior doing anything!!! > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
