I just realized... The table is generated when creating the log with RDLogManager, so I can't really attempt to repair a table that does not yet exists. I have an event in the clock that has a pre- and post-import carts that imports from group traffic with schedule-code COMMERCIAL when generating, since I don't use an external traffic-system. It may be stupid, but I'm just running a webbased station. :p It's the post-import cart in that event that makes mysql go wild on me.
- Marius On ons, mars 13, 2013 21:15, Fred Gleason wrote: > On Mar 11, 2013, at 01:06 09, Marius Radiokæll Qtronix wrote: > >> The pre-import cart and the actual imported cart gets inserted to the >> log, >> but when it reaches the post-import, it stops and begins on the next >> hour. >> Looking at the table in mysql, the pre-import cart has the id 6 and >> imported cart 7. Funny thing is rdlogmanager also tries to give the >> post-import cart the id 6 in the table aswell. > > Sounds like the '2013_03_11_LOG' table in MySQL is corrupt. Doing a > REPAIR TABLE on it would likely fix it (but don't assume -- always backup > the DB first!) > > Cheers! > > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer > | > | | Paravel Systems > | > |-------------------------------------------------------------------------| > | A room without books is like a body without a soul. > | > | -- Cicero > | > |-------------------------------------------------------------------------| > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
