On May 30, 2011, at 6:29 AM, Pawel Fic wrote:

> 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 
> <<<<<<<<<<<<<<<<<<<<
> 

The capture agent can merge settings defined in the local configuration manager 
properties file with one hosted remotely.  You have not configured a URL 
specifying the remote configuration, so you get this WARN in the logs.  This 
isn't a problem.  In fact, we should probably reduce that message from a WARN 
to an INFO, since putting all of the configuration values in the local 
configuration is perfectly legitimate, and this is the default configuration.

The fact that the matterhorn-capture-agent-impl bundle displays as "active" is 
a good sign, it means that it started successfully.

> 
> 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?

The logs on the capture agents should provide you with more details.  If you 
want to increase the logging level, you can do so by changing 
log4j.logger.org.opencastproject=INFO to log4j.logger.org.opencastproject=DEBUG 
in $FELIX/conf/services/org.ops4j.pax.logging.properties


> 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.

I definitely do not recommend taking this approach.  If the debug logging is 
still not sufficient to figure out what's happening, two tools come to mind to 
help: wireshark, and the eclipse debugger.  But I really think this is solvable 
without diving that deep.

Josh

> 
> 
> 
> 
>> 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

Reply via email to