On 12-06-01 06:41 PM, Solomon Melchizedek wrote: >> Hello Greg, >> >> I have two capture agent, which show in the matterhorn >> webpage. You can find them in my attachment file. >> 1. real capture hardware --> "ubuntu-206 " I have used >> this device to capture video in test page of capture agent. It works well. >> I think this CA is ok. >> 2. demo_capture_agent >> >> I really used "ubuntu-206" to capture, Matterhorn Web page >> shows that " Warning: Recording may have failed to start or ingest! ". >> >> Now, I have restart core server, but it still have >> "............................failed with code 503". I think may be it >> likely a failure during the build process. But when I watch build log, it >> shows build successfully. Although there have a little errors when I build >> it, the result of build is successful. You can find this log in my >> attachement.
The end of a build has a fairly large banner indicating success or failure. Other success or failure messages earlier in the build are part of the unit tests, and can be ignored. Your attachment does not contain a log though, it's a screenshot of the scheduling UI. I would rebuild the Matterhorn modules on both the CA and the, and then restart both Matterhorn instances. If it still doesn't work then please send the log from both builds and a copy of the config files again. G >> >> Thanks >> >> >> On Fri, Jun 1, 2012 at 3:44 PM, Greg Logan [via Opencast] < >> [email protected]> wrote: >> >>> On 6/1/2012 1:25 PM, Solomon Melchizedek wrote: >>>> Hello Greg, >>>> >>>> Thank you for your help!!!! I have run them, matterhorn can >>> find >>>> CA. But when it run, CA can not capture. Matterhorn Web page shows >>> that >>>> Warning: Recording may have failed to start or ingest! >>> >>> Two issues. First and foremost, the CA does not appear to be >>> communicating with the core correctly. The error code 503 implies to me >>> that the core has not started successfully: that code means that the >>> service the CA is trying to talk to is not available. Try restarting >>> the core to fix this. >>> >>> The CA at this point is not successfully registering itself with the >>> core. This, I suspect, has led to some confusion on your part: the >>> 'demo_capture_agent' is actually a piece of example code that runs on >>> the *core* for people who do not have access to real CA hardware (eg: >>> setup a core for demonstration purposes). When you schedule a capture >>> with it it merely copies some static files and waits for the appropriate >>> length of time. You can see your demo_capture_agent try (and fail) to >>> start a capture where the StartCaptureJob.java:108 lines appear. If you >>> are to the point where you are testing with real capture hardware I >>> would just ignore the demo_capture_agent for now. Most production >>> systems would not have the demo CA code deployed, so this issue is not >>> terribly common. >>> >>> In short, your CA is configured correctly but you have misinterpreted >>> what the demo_capture_agent actually is. Restarting your core should >>> hopefully clear up the issue (the error messages on the CA will stop >>> appearing), but if not then there was likely a failure during the build >>> process. >>> >>> 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
