On 4/12/12 1:12 PM, Christopher Brooks wrote:
1. They hang requiring a full reboot with no indication of why they
hung in any log anywhere.

Check out dmesg.  If they hang it's usually not an MH problem, but of
course it could be.


There is nothing in any log. Nothing in dmesg, the messages log, the matterhorn log, etc. I agree that it's likely not a MH problem, it's most likely a driver problem. I just want to know if anyone else is seeing this.

2.  The JVM crashes.  This does leave the standard java crash log.
There is no information in the matterhorn logs.

This usually happens when gstreamer dies.  Can you post a configuration
file somewhere?


Which config file would you like?

3.  Matterhorn hangs becoming unresponsive to http requests, stops
logging, stops processing, etc...requiring a restart of matterhorn.
Again with nothing out of the ordinary in the logs.

Load average on these times?


This actually happened this morning. It started at about 4am or so and continued until I restarted matterhorn around 10am. I monitor load average and cpu utilization via snmp at 5 minute intervals. The average utilization for this entire period was 1%. The graph is in fact mostly flat. The load average for this period was less than 0.1.

4.  The load average on the machine creeps up inexplicably (see
attached image).  The peaks are when it is recording.  The plateaus
indicate the weird increased load average.  The machine is running
nothing else but matterhorn.  This also has nothing out of the
ordinary in the logs. Restarting matterhorn brings the load average

Not an awesome load average.  Which devices are installed, a vga2usb
and a bluecherry card?


I know it isn't an awesome load average, but it's odd and it grows. It's also considerably higher than normal for the agent when it is not recording. Typically the load average is almost 0. It is the vga2usb and the bluecherry card. We are using the -exact- reference hardware that has been on the wiki for the last year.

How often do these errors happen, and how repeatable?

Across the 4 agents, when scheduling recordings throughout the day, one does one of these things on average daily. The individual errors are hard to repeat on specific agents at specific times.


Chris
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users

Reply via email to