On 2011-07-24 12:23 PM, Lovemore Nalube wrote: > Hi Kevin > > 2.2.0rc1 seems to be the latest firmware version available according to > Epiphan. They also said that the capture agent only works with 1.2 and > not 1.1.
It's only going to work properly with a 1.2 or newer core. The 1.1 series improperly processed media which led to the loss of the video camera stream. I *did* have it working with that limitation, so there's no reason it won't work for you (unless I've introduced a regression bug :)). The 2.2.0 series is the latest I have as well, so it looks like you're running the latest firmware. Do you have access to the console on the device? I seem to remember Epiphan offering a developer version which might allow you a closer look at what's actually going wrong. Unfortunately without access to the device it can be difficult to understand what's going wrong. G > Please Greg help us out here :) > > Cheers > > > -- > Lovemore Nalube > OLE Developer (Vula) > University of Cape Town > http://www.cet.uct.ac.za/LovemoreN > >>>> On 7/23/2011 at 2:19 AM, in message > <[email protected]>, Kevin Chan > <[email protected]> wrote: > Hi Greg, > > FYI, we at UC Berkeley also just got our hands on an Epiphan MH capture > device and are having similar issues (even after restarting the device) > getting it to connect to our MH core (1.1.x, running on port 80 forwards > to port 8080). > > Firstly, can you tell us where we can go to grab the latest firmware? (I > think our device has an older version 2.2.0rc1.) > > Secondly, one thing I noticed is that in the "Web content" config > section, there is a "matterhorn" entry under "Other files". If I click > on the link, it goes to a 404 error page and if I try to remove it, it > gives me a "Warning: unlink..." error. > > Kevin Chan > > Operations Team > Educational Technology Services > UC Berkeley > > > On 7/21/11 9:33 AM, Greg Logan wrote: >> On 11-07-21 10:11 AM, Lovemore Nalube wrote: >>> Hi Greg Logan >>> >>> I see from a different post you just made that you are the man behind >>> the new Epiphan >>> Matterhorn Capture Appliances! We have one here but it is not showing up >>> on the 1.2 rc6 server we have running. >>> >>> We've enabled its Matterhorn capabilities and set the proper URL to the >>> server plus the username/password yet it does not come up on the list of >>> capture agents in the server end. >>> >>> Is there something special that has to be done for this to communicate >>> with the server? We got the latest firmware update from Epiphan. >> Unfortunately that config page is most definitely a work in progress. >> There's no validation currently (no type checks, no range checks, etc), >> and the services are not restarted when changes are made. Have you >> tried restarting the box, either through the UI or by removing power for >> a minute or two? Also remember that the Core URL field needs to include >> the port as well (eg: http://192.168.0.1:8080). >> >> G >> >>> Thanks >>> >>> >>> -- >>> Lovemore Nalube >>> OLE Developer (Vula) >>> University of Cape Town >>> http://www.cet.uct.ac.za/LovemoreN >>> >>>>>> On 7/21/2011 at 5:42 PM, in message <[email protected]>, >>> Greg Logan <[email protected]> wrote: >>> Hi Folks, >>> >>> Cross posting to ensure everyone hears this, sorry about the spam! >>> >>> I'm the guy doing the Matterhorn integration work for the new Epiphan >>> Matterhorn Capture Appliances (MCAs), as well as a developer for the >>> normal Matterhorn capture agent (CA). We have about 10 CAs deployed on >>> our campus currently, and one of our concerns was monitoring their >>> status outside of Matterhorn itself. To do this we use Nagios to check >>> if they're up by sshing into them, and we're working on the next step of >>> checking the system health (smart, disk space, etc) as well as making >>> sure they capture when they should. >>> >>> Does anyone else monitor their CAs in a similar way? Are you using >>> Nagios as well? Munin? I ask, because we are at a stage in the MCA >>> development where adding something like Nagios would be easy (memory >>> space permitting!), so I'd like some community feedback in terms of what >>> people are looking for in an SNMP monitor. >>> >>> Thanks, >>> G >>> >>> >>> ### >>> >>> UNIVERSITY OF CAPE TOWN >>> >>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer >>> published on our website at >>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from >>> +27 21 650 9111. This e-mail is intended only for the person(s) to whom >>> it is addressed. If the e-mail has reached you in error, please notify >>> the author. If you are not the intended recipient of the e-mail you may >>> not use, disclose, copy, redirect or print the content. If this e-mail >>> is not related to the business of UCT it is sent by the sender in the >>> sender's individual capacity. >>> >>> ### >>> >>> >>> >>> _______________________________________________ >>> 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 > > > ### > > UNIVERSITY OF CAPE TOWN > > This e-mail is subject to the UCT ICT policies and e-mail disclaimer > published on our website at > http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from > +27 21 650 9111. This e-mail is intended only for the person(s) to whom > it is addressed. If the e-mail has reached you in error, please notify > the author. If you are not the intended recipient of the e-mail you may > not use, disclose, copy, redirect or print the content. If this e-mail > is not related to the business of UCT it is sent by the sender in the > sender's individual capacity. > > ### >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
