On 12-04-05 08:31 AM, Jack Vant wrote: > Applied the firmware and reset the device to factory defaults. > Reconfigured the matterhorn bit and now it talks to the core, but alas > it starts the capture and never seems to finish. I've run two test > captures and they still show as capturing. Any ideas as to what might > be going on.
Can we get a look at the logs the device is generating? If it's getting to the capturing state then it should (eventually) ingest things one way or another. G > On Thu, Mar 29, 2012 at 10:48 AM, Greg Logan <[email protected]> wrote: >> On 12-03-29 09:02 AM, Jack Vant wrote: >>> I have upgraded my epiphan appliance to 2.3.0e and reset it to factory >>> defaults. I have reconfigured the matterhorn setup, but the device >>> doesn't report into the core. Any ideas? I see where there's a >>> traceroute function, but alas our network engineers have disabled ping >>> and traces on our university network -- security concerns. >> >> Hi Jack, >> >> My appologies, the beta firmware from Epiphan contains an issue which >> prevents the Matterhorn scripts from functioning correctly. For the >> moment, I have posted a working (and tested) build at >> http://aries.usask.ca/epiphan/frm-2-3-0e-Matterhorn-15977_1067-VGA2CPU_DM365.bfrm-CUSTOM.bfrm. >> The very latest beta is also available at >> http://aries.usask.ca/epiphan/frm-2-3-0e-Matterhorn-16051_1068-VGA2CPU_DM365.bfrm-CUSTOM.bfrm, >> but I'm still testing that one (although it appears stable). >> >> G >> >> >> >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> > > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
