On 2011-05-31 7:42 AM, Josh Holtzman wrote: > Please file a ticket for this. I'm not sure that this is actually the source > of your problem, but regardless there should not be any hard coded filesystem > paths in jars that can't be overridden via configuration.
This path is set at configure time. I'd love to use a variable but I haven't been able to get that working so we added it to the configuration script instead. G > Thanks, > Josh > > On May 31, 2011, at 6:28 AM, Pawel Fic wrote: > >> OK, I think I will give up on this one :-), A short summary: >> >> (1) >> I was unable to start only the capture profile w/o the rest of the server >> running. I think demo capture agent relies on something inside the server. >> >> (2) >> I think: >> /1.1.0/modules/matterhorn-capture-agent/src/main/resources/OSGI-INF/capture-files.xml >> has entry: >> <property name="filesystemDir" value="/tmp/opencast/cache/captures" /> >> and this causes that my multiple capture clients cannot run on the same PC - >> they fail to upload files. >> >> Actually if I am going to develop a capture agent - I don't really need >> multiple demo capture agents. I prepared a presentation with one demo >> capture agent, and I named it: "The Conference Room Camera", rather then >> "Classroom 1", "Classroom 2". >> >> I still think it would be a nice feature to start capture profile separate >> to the server (on different JVM). >> >> Thank you all, for your help - I appreciate it. >> >> >> >> --- On Mon, 5/30/11, Pawel Fic <[email protected]> wrote: >> >>> From: Pawel Fic <[email protected]> >>> Subject: Re: [Matterhorn-users] Matterhorn running with more than one Demo >>> Capture Agent >>> To: "Matterhorn Users" <[email protected]> >>> Date: Monday, May 30, 2011, 3:29 PM >>> Not quite. >>> On Matterhorn-list (that is for Developers) I ask about >>> specification of protocol between capture agent and the >>> server. >>> -Or some information about the architecture. >>> But your answer to "API Spec" was addressing this issue. >>> Thanks. >>> >>> However, I followed your instruction: >>> >>> 1. changed each instance to run on different ports and >>> directories >>> [start_matterhorn.sh, conf/config.properties, >>> conf/system.properties, >>> services/org.opencastproject.capture.impl.ConfigurationManager.properties >>> -- point to the server] >>> >>> 2. I compiled the 5 instences with "capture" profile (well >>> I compiled once, and then copied result), but they did not >>> started at all. >>> >>> [it never get's to CaptureAgentImpl::activate() ] >>> >>> "lb" shows a bundle: >>> <<<<<<<<<<<<<<<<<<<<<<<< >>> 84|Active | >>> 4|matterhorn-capture-agent-impl (1.1.0) >>> <<<<<<<<<<<<<<, >>> but "stop 84" "start 84" >>> results in: >>> <<<<<<<<<<<<<<<<<<<< >>> 15:10:58 WARN (ConfigurationManager:116) - Malformed >>> URL for capture.config.remote.endpoint.url, disabling >>> polling. >>> 15:10:58 INFO (ConfigurationManager:121) - No remote >>> configuration endpoint was found, relying on local config. >>> 15:10:58 INFO (StaticResource:102) - registering >>> classpath:/ui at /capture with welcome file index.html >>> <<<<<<<<<<<<<<<<<<<< >>> >>> >>> 3. I guessed that - something is missing in conf files, but >>> I have no clue what. So, instead of compiling only "capture" >>> profile, I compiled everyting and --- started 6 instances of >>> entire server with demo capture agents. >>> >>> I changed each server's demo capture agent's >>> org.opencastproject.capture.impl.ConfigurationManager.properties >>> to point to first server.. >>> >>> >>> And here I have 6 demo capture agents present on my server. >>> >>> I changed names and I thought I am ready to go with the >>> presentation - but then I decided to try it out. >>> >>> >>> 4. >>> I have ended up with: >>> >>> (a) Upcoming recordings (1) -- that supposed to be recorded >>> an hour ago. >>> (b) status: "WARNING : Recording may have failed to start >>> or ingest!" "It seems the core system did not recieve proper >>> status updates from the Capture Agent that should have >>> conducted this recording. " >>> >>> >>> Still no good for presentation :-) >>> >>> >>> >>> Any clue how to investigate it? >>> Right now I type in "logger.info("my message")" >>> then recompile - replace .jar - then try to run again and >>> figure out what is wrong. A lot of energy and time. >>> >>> >>> >>> >>>> From: Josh Holtzman <[email protected]> >>>> It looks like this conversation is >>>> happening on two lists. Please see my comments on >>> the >>>> matterhorn list. The archived version is >>>> http://opencast.3480289.n2.nabble.com/API-Spec-tp6410298p6411181.html >>>> >>>> Josh >>>> >>> >>> _______________________________________________ >>> Matterhorn-users mailing list >>> [email protected] >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
