On 12-01-16 01:54 PM, Steven M Lichti wrote: > Greg, > > It should have finished it's scheduled recording by now. I did a five > minute recording, and it did change to Capturing, but then never finished > and uploaded the recording. I remember something back about others > sometimes needing to restart the device a couple of times to complete the > upload. > > Should I use a button on the side (if so, which one?), or use the Reboot > Now button on the Maintenance page?
The reboot button in the maintenance page works. Looking at the logs, it captured and then ingested so please also check that the core received the ingest: Jan 16 14:00:40 MTH92130 user.notice MH.ingest: Ingesting recording 22832 succeeded G > --Steven. > > On 1/16/12 1:22 PM, "Steven M Lichti" <[email protected]> wrote: > > >> I'm not sure whether I restarted it then or not. I know I've used the >> "Reboot Now" button, but not necessarily when I changed the polling. >> >> I'll go ahead and schedule a recording to occur in a few minutes and see >> what happens. Thanks Greg! >> >> --Steven. >> >> -- >> Steven Lichti >> Academic Technologies >> Northwestern University >> [email protected] >> (847) 467-7805 >> >> On 1/16/12 1:12 PM, "Greg Logan" <[email protected]> wrote: >> >> >>> On 12-01-16 01:02 PM, Steven M Lichti wrote: >>>> Sure, I'll send it to you directly... >>> >>> I'm in. The schedule the agent had was a 401 page which explains why >>> nothing captured. When you changed the calendar polling time did you >>> restart the agent? The update scripts checks for new calendar data, >>> then sleeps for the update interval. If you changed the interval while >>> it was sleeping it would not check until the *end* of the interval (eg, >>> an hour from when it slept). This would explain why when I restarted >>> the service an empty calendar downloaded as expected. >>> >>> G >>> >>>> --Steven. >>>> >>>> >>>> >>>> On 1/16/12 12:57 PM, "Greg Logan" <[email protected]> wrote: >>>> >>>>> On 12-01-16 12:32 PM, Steven M Lichti wrote: >>>>>> Greg, >>>>>> >>>>>> Can we try hooking this appliance up to one of your servers and see >>>>>> what >>>>>> happens? >>>>> >>>>> We can certainly try. If I can get at it remotely I can also login >>>>> and >>>>> check what it's doing internally, that's usually fastest in terms of >>>>> diagnosis. Can you email me the device's public IP? >>>>> >>>>> G >>>>> >>>>>> --Steven. >>>>>> >>>>>> On 1/16/12 12:15 PM, "Steven M Lichti" <[email protected]> >>>>>> wrote: >>>>>> >>>>>> >>>>>>> The calendar polling interval is already set for 1 minute... >>>>>>> >>>>>>> --Steven. >>>>>>> >>>>>>> >>>>>>> On 1/16/12 12:05 PM, "VISIONAIRE-Reza Toghraee" >>>>>>> <[email protected]> wrote: >>>>>>> >>>>>>>> Make sure you have reduced the calendar reading interval in MCA to >>>>>>>> 1 >>>>>>>> minute. >>>>>>>> >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: [email protected] >>>>>>>> [mailto:[email protected]] On Behalf Of >>>>>>>> Steven >>>>>>>> M >>>>>>>> Lichti >>>>>>>> Sent: Monday, January 16, 2012 10:03 PM >>>>>>>> To: Matterhorn Users; Greg Logan >>>>>>>> Subject: Re: [Matterhorn-users] Recording with MCA? >>>>>>>> >>>>>>>> Greg, >>>>>>>> >>>>>>>> The core still says that the appliance failed to start the >>>>>>>> recording. >>>>>>>> Is >>>>>>>> it >>>>>>>> possible that it is recording, and we'll simply find out later? If >>>>>>>> that >>>>>>>> is >>>>>>>> not the case, then is there any way we can figure out what's going >>>>>>>> on? >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> --Steven. >>>>>>>> >>>>>>>> On 1/16/12 11:50 AM, "Steven M Lichti" <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>>> Okay. We're using the 2.2.3 firmware from a couple of weeks ago. >>>>>>>>> >>>>>>>>> --Steven. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 1/16/12 11:33 AM, "Greg Logan" <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> On 12-01-16 11:03 AM, Steven M Lichti wrote: >>>>>>>>>>> No luck. We've just scheduled another recording for an hour away >>>>>>>>>>> to >>>>>>>>>>> see if that works. Am I going to need to change to DEBUG >>>>>>>>>>> logging >>>>>>>>>>> to >>>>>>>>>>> see what's going on here? >>>>>>>>>> >>>>>>>>>> That would tell you if the agent is actually hitting the >>>>>>>>>> calendaring >>>>>>>>>> endpoints, but won't be helpful beyond that. Which firmware >>>>>>>>>> version >>>>>>>>>> are you using? >>>>>>>>>> >>>>>>>>>> G >>>>>>>>>> >>>>>>>>>>> --Steven. >>>>>>>>>>> >>>>>>>>>>> On 1/16/12 10:53 AM, "Steven M Lichti" >>>>>>>>>>> <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Alright, we'll see what happens shortly. We set the polling to >>>>>>>>>>>> two >>>>>>>>>>>> minutes... >>>>>>>>>>>> >>>>>>>>>>>> --Steven. >>>>>>>>>>>> >>>>>>>>>>>> On 1/16/12 10:51 AM, "Greg Logan" <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On 12-01-16 10:47 AM, Steven M Lichti wrote: >>>>>>>>>>>>>> Greg, >>>>>>>>>>>>>> >>>>>>>>>>>>>> It turns out the latest culprit was the password. I pasted in >>>>>>>>>>>>>> the >>>>>>>>>>>>>> wrong one. Now, with that solved, I've just scheduled a >>>>>>>>>>>>>> recording >>>>>>>>>>>>>> to begin in >>>>>>>>>>>>>> 20 >>>>>>>>>>>>>> minutes. Is there any way to see any sort of log file for the >>>>>>>>>>>>>> capture appliance? >>>>>>>>>>>>> >>>>>>>>>>>>> Not as of yet; that feature is still in development >>>>>>>>>>>>> unfortunately. >>>>>>>>>>>>> If >>>>>>>>>>>>> your schedule polling interval is less than 20 minutes it >>>>>>>>>>>>> should >>>>>>>>>>>>> capture. Ingest can take a while after that depending on >>>>>>>>>>>>> settings >>>>>>>>>>>>> as well. >>>>>>>>>>>>> >>>>>>>>>>>>> G >>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>> >>>>>>>>>>>>>> --Steven. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
