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)
--
________________________________________________
Rüdiger Rolf, M.A.
Universität Osnabrück - Zentrum virtUOS
Heger-Tor-Wall 12, 49069 Osnabrück
Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
E-Mail: [email protected]
Internet: www.virtuos.uni-osnabrueck.de
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
