We had a variation of this problem after about a month of running the ECD successfully on MH 1.3.0. The warning would appear for increasing amounts of time in the admin panel, then go away, with the recording completing successfully. It turned out that our ECD's clock was losing time.
Our solution was to adjust the Real Time Clock (RTC) calibration in ECD -> Date & Time menu. Charlie UC Davis On May 23, 2012, at 1:06 AM, Olav Bringedal wrote: > On 2012-05-23 04:28, zengshan wrote: >> >> when I schedule a record, I failed, and error message is as follows: >> WARNING : Recording may have failed to start or ingest! >> It seems the core system did not receive proper status updates from the >> Capture Agent that should have conducted this recording. >> my configuration of MCD is: >> Calendar Polling Interval (in minutes)Calendar data cache length (in >> weeks)Agent State Push Interval (in seconds)Skip Conflicting CapturesMaximum >> Capture Duration (in hours)Ingest Interval (in minutes) >> >> >> and the logs in MCD is : >> May 6 09:53:32 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:53:32 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:54:36 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:54:36 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:55:40 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:55:40 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:55:40 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:55:48 MTH92512 user.info MH.sendCaps: Capabilities sent to >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT/configuration >> May 6 09:56:50 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> May 6 09:56:50 MTH92512 user.info MH.sendState: Agent set to idle at >> http://202.38.128.13:8080/capture-admin/agents/MCD_AGENT >> 2012-05-23 >> >> >> >> ZENG SHAN >> Tel,861088236837 >> E-mail,[email protected] >> Computing Center >> Institute of High Energy Physics,CAS >> >> >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > I think we had this problem. The device runs a script called mh.scheduler > that dies sometimes if the load is too high/the memory runs too low or > something. > > you should look for: > > > user.debug MH.Scheduler[894]: Fetching calendar from > > http://matterhorn_server/recordings/calendars?agentid=agent&cutoff=something > > > > this script fetches the scheduled recordings from the matterhorn server (as a > calender feed) > > If it isn't in the log, you need to reboot the device. Ive heard a rumour > that the device has an option to have a scheduled reboot , but i cant find it > in the web interface. When the source is open sourced, you can probably > enable it manually. > > > > > -- > > Olav Bringedal > > Seksjon for integrasjon og applikasjonsutvikling > IT-Avdelingen UIB > _______________________________________________ > 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
