Hi Pawel Thanks for your quick reply. I hope I specified the endpoint.url's correct in my config?! Both variables are pointing to the core server ...
But that was only the half of my concerns. What I would like to know much more is: How can I fix the capabilities filtering on the core-server?! I guess that capabilites are: CA IP-address, capture.devices etc. At the moment the server don't know where the CA is and what it is able to do. So sometimes the ingest of an scheduled recording fails, because the CA updates his state not at the right time. It seems as if the interaction between server and CA is one-sided. And this I want to fix!! I think I posted everything you need to know about my problem: .conf, log-snippets ... or is something missing? No one ever had this problem? Again: Server log: 2011-09-15 10:27:01 WARN (AgentImpl:271) - Null friendly name list for agent unibasMatterhorn. Capabilities filtering aborted. CA log: 11:32:55 INFO (AgentStateJob:194) - #6 - State push org.opencastproject.capture.impl.jobs.AgentStateJob@3849ca75 to http://matterhorn.cs.unibas.ch/capture-admin/agents/unibasMatterhorn was successful. 11:32:55 INFO (AgentCapabilitiesJob:115) - #6 - Capabilities push to http://matterhorn.cs.unibas.ch/capture-admin/agents/unibasMatterhorn/capabilities failed with code 405. Thanks for your help stefan Am Donnerstag, den 15.09.2011, 02:29 -0700 schrieb Pawel Fic: > > > > Furthermore I send here the > > org.opencastproject.capture.impl.ConfigurationManager.properties > > file of > > the CA. What is the difference between > > capture.agent.state.remote.endpoint.url and > > capture.recording.state.remote.endpoint.url? > > > > > > Hi Stefan. > > capture.agent.state.remote.endpoint.url is used to report capture agent's > state - what the Capture Agent is doing. The states are: "idle", "capturing", > "powering off" and "unknown" > > > capture.recording.state.remote.endpoint.url is used to report what the > capture agent is doing to the recording. > Recordings states are: "capturing", "capture_finished", "uploading", > "upload_finished", "compressing", .... any few other. > > So - stuff reported with: "capture.agent.state.remote.endpoint.url" is by > design reflected on Admin Tools / Capture Agents > > And stuff reported with "capture.recording.state.remote.endpoint.url" is > reflected on "Recordings" tab. > > > Is this what you asked for? > > > Have you seen the SPEC for those endpoints: > http://nway.ncast.com:8080/docs.html?path=/capture-admin > > [look for "Set the status of a given capture agent" and "Set the status of a > given recording, registering it if it is new"] > > > --------------------------------- > Other than this - I head serious problem reporting CA capabilities, and I > think documenting the endpoints requires some work. Would you agree with this > (posts on mailing lists are "Matterhorn's design" and "Capture Agent API") > > > -Pawel > > _______________________________________________ > 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
