Dear All Thanks for your answers.
I discovered an other WARN in the server log, during the service start of matterhorn: 2011-09-16 10:41:59 WARN (TrustedHttpClientImpl:246) - URI http://matterhorn.cs.unibas.ch/capture-admin/agents/demo_capture_agent does not support digest authentication So I think to solve my "cannot-push-capabilities"-problem I should fix this "does-not-support-digest-authentication"-problem. Is this an known problem with a common solution? Any one an idea? And btw: I am using matterhron 1.1 g stefan Am Donnerstag, den 15.09.2011, 09:03 -0600 schrieb Greg Logan: > On 11-09-15 04:45 AM, Pawel Fic wrote: > > Matterhorn version number would be useful. I really do not want to access > > matterhorn.cs.unibas.ch. I am also "a newbie" to Matterhorn. > > > > Yes, your CA is trying to push CA tries to push capabilities and state and > > .. here is where I think you are wrong: is is you CA who wants to ingest > > recordings. > > I do not want you to accept it. Rather: correct me if I am wrong, or it is > > a clue for you to figure out what actually happens there. This information > > was very useful for me to understand how CA works. > > You are quite correct. The CA is in charge of pushing any relevant data > to the core, which includes its various state information as well as the > captured media. > > > > > I really think this is not related to your configuration file. > > I also do not want to access "matterhorn.cs.unibas.ch". I just asked for > > version number. Some REST endpoint has changed between 1.2 and 1.1. Pushing > > agent's capabilities is one of those. > > In regards to the error you are experiencing, you are missing a required > key in the configuration data called capture.device.names which must > have the system names of the input devices. Take a look at the mock > capture agent for an example: > > capture.device.names=MOCK_SCREEN,MOCK_PRESENTER,MOCK_MICROPHONE > > This tells us that there should be keys called > capture.device.MOCK_SCREEN.*, capture.device.MOCK_PRESENTER.* and > capture.device.MOCK_MICROPHONE.* > > G > > > > > But really I am also new to this project. I cannot see the two-sided > > communication. I do not know what version of Matterhorn you are using, and > > I find it important (this is why I asked about it). This is why I tried > > accessing your server. There no way I can check this. I will be following > > this thread since I also have problems with pushing capabilities from CA to > > core server. > > Sorry, just wanted to help, but w/o getting some information I will not be > > useful. > > > > Best Regards > > -Pawel > > > > --- On Thu, 9/15/11, stefan braun <[email protected]> wrote: > > > >> From: stefan braun <[email protected]> > >> Subject: Re: [Matterhorn-users] cannot push capabilities from CA to core > >> server > >> To: "Matterhorn Users" <[email protected]> > >> Date: Thursday, September 15, 2011, 12:22 PM > >> 1) The reason why you can't reach > >> matterhorn.cs.unibas.ch is because it > >> is in a closed environment of the university. > >> > >> 2) I'm a matterhorn newbie, so if you tell me that a > >> one-sided > >> communication is preferred for matterhorn, I accept this. > >> But when I see > >> that my CA tries to push capabilities and state and the > >> Core server > >> ingests recordings: Then for me this is looking like a > >> two-sided > >> communication set-up. But perhaps I totally misunderstand > >> this concept?! > >> > >> However: I just want a correct working matterhorn > >> configuration. I just > >> thought that you have an Idea how to fix this or a hint > >> what I could do. > >> > >> Thanks > >> stefan > >> > >> Am Donnerstag, den 15.09.2011, 03:00 -0700 schrieb Pawel > >> Fic: > >>> First - that is important: what version of Matterhorn > >> are you using. > >>> I cannot connect to "http://matterhorn.cs.unibas.ch";. > >>> > >>> > >>> Second: why do you think communication between CA and > >> core server not supposed to be one-sided. It is very good > >> that it is one-sided. I only see the pros of this solution. > >> > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > _______________________________________________ > 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
