Dear Rüdiger Am Mittwoch, den 31.08.2011, 09:45 +0200 schrieb Ruediger Rolf: > Dear Stefan, > > Is you core server running on port 80 or port 8080 as it would be the > matterhorn default? > > If it is port 80 you have configured > org.opencastproject.capture.core.url in the CA config just fine, > otherwise you will have to add port 8080.
My core server is running on port 80. I did the following things: 1) i set a new rule for the port 8080 in the /etc/sysconfig/iptables: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT 2) and I uses ProxyPass ProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/ > > Otherwise you could check that you have set > org.opencastproject.capture.serviceregistry.url to your core server too > in the general config.properties (the default value does not work for > CAs, but this is usually set by the install script). The org.opencastproject.capture.serviceregistry.url of the CA is set to http://matterhorn.cs.unibas.ch/services now. Is the ending .../services correct? > > And last but not least you can check if the capture admin services are > working on the core server, if you use the Rest-docs on the welcome page. > Ok I will check the rest-doc-tests ... Until now the same failure still appears: 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. 405 is the code for method not allowed. Perhaps one should allow the PUT or/and DELETE methods of the httpd serve for a special directory?! Where is the capability-information stored? Additionally it is not possible to schedule recordings from the core server: 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. Weirdly the Unscheduled-unibasMatterhon-123456789 test Captures started form the CA are pushed, processed and published correct to the core server. But the other way round it dont works and capabilities cant be pushed. g stefan > Rüdiger > > Am 30.08.2011 22:18, schrieb stefan braun: > > Dear Rüdiger > > > > Thank you very much for the hint with the 3dr party-tools!!! This was > > exactly the missing part. I did not realized that to install 3dr party > > tools is mandatory to install. I thought that it is optional and only > > needed if one would like to do special video processing things. However, > > it is working now and the streaming server as well. > > > > > > Now there is only one more issue to be solved: The thing about > > “capabilities can not be pushed”... I stay tuned! > > > > > > regards > > matt > > > > > > > > Am Dienstag, den 30.08.2011, 16:54 +0200 schrieb Ruediger Rolf: > >> Dear Sefan, > >> > >> The CA config file is strange: > >> you configured two devices to read from /dev/video0 > >> capture.device.DV_1394.src=/dev/video0 > >> capture.device.VGA.src=/dev/video0 > >> > >> This cannot work. You intended to use Firewire as it seems to me. But > >> you commented this out. > >> Please check the capture agent configuration information > >> http://opencast.jira.com/wiki/display/MHDOC/Capture+Agent+Configuration+V1.2 > >> > >> You will need to execute docs/scripts/3rd-party/do-all otherwise you > >> will not have mediainfo, tesseract, ocropus and many more libraries > >> installed. > >> > >> Rüdiger > >> > >> Am 30.08.2011 16:33, schrieb stefan braun: > >>> Dear Rüdinger > >>> > >>> Thanks for the reply. > >>> > >>> Am Montag, den 29.08.2011, 17:29 +0200 schrieb Ruediger Rolf: > >>>> Your pipelines do not work. Please sent the last section of your Capture > >>>> agent Config file > >>>> (org.opencastproject.capture.ConfigurationManager.properties). I think > >>>> the configuration ist broken. > >>> I attached the CA config file to the email. Here I have to mention that > >>> for a test capture on the CA everything works fine. > >>> > >>> In the CA log there appears an ERROR when the agents tries to push his > >>> capabilities to the core server. Perhaps this is the issue?! It is > >>> strange that the status can be pushed but the capabilities not: > >>> > >>> 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. > >>> > >>> > >>>> I'm still confused that mediainspection the zip workflow fails... Do > >>>> you have installed the 3rd party tools successful? Can you call > >>>> mediainfo from the command line on the server? > >>>> > >>> I did not install anything with 3rd party tools on the centOS, but gzip, > >>> bzip2 and java was pre installed. The only thing I did was installing > >>> gstreamer and ffmpeg (is this 3rd party?). Is this enough or should > >>> there be more 3rd party tools? Unfortunately I have no idea what a top > >>> level scrip is and where I can find ./menu3p mentioned in this readme > >>> file: > >>> http://opencast.jira.com/svn/MH/tags/1.1.0/docs/scripts/3rd_party/README.txt > >>> Is it necessary to execute it?! > >>> > >>> > >>> > >>>> Why don't you change the working directory to a permanent directory > >>>> (/tmp/opencast will be deleted with every restart of the server) and > >>>> make sure that your matterhorn user has the right to write in the new > >>>> content directory. > >>> I changed the working directory variable on the core server from > >>> org.opencastproject.storage.dir=${java.io.tmpdir}/opencast > >>> to /opt/matterhorn/cache/opencast now and gave all rights for the > >>> matterhorn user. > >>> > >>> > >>> g > >>> matt > >>> > >>> > >>>> Rüdiger > >>>> > >>>> > >>>> > >>>> > >>>> Am 29.08.2011 13:13, schrieb stefan braun: > >>>>> Dear Rolf > >>>>> > >>>>> Thanks for your reply. > >>>>> > >>>>> I use a core server running on centOS (the all-in-one Linux server) and > >>>>> a CA running on ubuntu 10.10. Both server and CA are version 1.1. What > >>>>> do you mean with the content directory? The /tmp/opencast directory > >>>>> where the media-files are stored? > >>>>> > >>>>> I found out now that if I try to schedule a new recording job on the > >>>>> server for the capture agent, then there is a pipeline error. That is > >>>>> why my media files have zero size and perhaps the reason why the files > >>>>> can not be inspected?! The test on the CA works fine: vga, dv and alsa > >>>>> audio can be recorded and listened/watched later. How could I fix a > >>>>> pipeline error? > >>>>> > >>>>> Here the log of my last recording schedule (attached to the email) > >> > > > > _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
