Olli, Usually segmenting and OCR failures are not due to database errors.
The first area to check is that all third party tools are properly installed and available to Matterhorn. Next, the workflow you use must match your file. If you are uploading a file as a presenter and segmentation is working on the presentation you will not get any results. Have you looked into the details of the workflow results? You haven't shown us what log errors you are getting. Hank On Fri, May 4, 2012 at 1:34 AM, Olli Salo <[email protected]> wrote: > > Hi Hank, > > that is the way we created our mysql database. We used the ddl script from > command line, not the autogen.dd-config (we set the ddl.generation=false). > And now we're wondering if that's indeed the right way to do it or if we > should use the autogen.dll=true instead. That is to say: we're not sure if > our mysql db schema is 100.00% what MH expects it to be and whether our > problems are related to the db or not. You see, in our newly-installed MH > 1.3 segmenting + OCR aren't working at all. > > This is quite a problem for us because we wouldn't want to delete our > production data in our mysql db but we still would like to have the > segmenting and text analysis work. So my question to everybody is: is > anyone else suffering from similar problems regarding segmenting / OCR with > MH 1.3? > > We did notice the discussion thread > > http://opencast.3480289.n2.**nabble.com/Error-segmenting-** > removing-file-in-Matterhorn-1-**3-td7389726.html<http://opencast.3480289.n2.nabble.com/Error-segmenting-removing-file-in-Matterhorn-1-3-td7389726.html> > > and my colleague says he has tried the mvn options mentioned in the thread. > > As always, any piece of advice truly appreciated! > > Yours, Olli S > > > > On 26.4.2012 16:29, Hank Magnuski wrote: > >> I would suggest the following sequence: >> >> 1. Create your database >> 2. Create all the tables using the ddl script "mysql5.sql" and the >> mysql tool. >> 3. Edit the properties file make ddl.generation FALSE >> 4. Start Matterhorn >> >> Hank >> >> On Thu, Apr 26, 2012 at 12:15 AM, Olli Salo <[email protected] >> <mailto:[email protected]>**> wrote: >> >> >> Hi, >> >> I decided to ask this question on this list because we're confused >> about the correct way of generating the sql tables. So the question: >> should we set the >> >> org.opencastproject.db.ddl.__**generation=VALUE >> >> in >> >> /opt/matterhorn/felix/conf/__**config.properties >> >> to TRUE or FALSE. >> >> We just recently installed our MH box again from scratch, and me + >> my colleague have this tiny feeling that we still might have some >> fishy table sets in our MySql tables. We used the FALSE-setting and >> created the tables manually, based on the manual db generation script >> in >> >> /opt/matterhorn/matterhorn_1._**_3.0/docs/scripts/ddl >> >> but we are facing some issues. We >> >> a) don't have statistics in our engage player videos >> b) segmenting doesn't seem to work. >> >> We're running MH 1.3.0 on our distributed installation (Redhat). >> >> Using MySql we can see (select * from user_action;) that there is >> some data of viewer statistics related tasks failing: we get the >> following message written in the type-field in the user_action table: >> >> ANNOTATION_INIT_AJAX_FAILED >> >> Moreover, we got an sql-related error message in our engage-servers >> /opt/matterhorn/felix/log/__**opencast.log. The error message can be >> found in: >> >> http://pastebin.com/E3yXUZZB >> >> Is anyone else suffering from similar symptoms? >> >> Any help will be greatly appreciated! >> >> >> >> Olli >> >>
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
