<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>> And does mythtv have any notification / alert options that could of been<br>
>> set to<br>
>> notify me about the failed recordings?<br>
<br>
> Well, the first lesson, the one I can help you with, is to always check your<br>
> system is functional each day.<br>
<br>
Really? Is it 1993 again?<br></blockquote><div><br></div></div><div>Hilarious! </div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Anyway, some previous discussion here:<br>
<br>
<a href="http://www.mythtv.org/pipermail/mythtv-users/2012-March/328923.html" target="_blank">http://www.mythtv.org/pipermail/mythtv-users/2012-March/328923.html</a></blockquote><div><br></div></div><div>Some great stuff there.</div>
<div><br></div><div>Really wish I were a developer, I think it would be relatively trivial to add support for error detection and reporting to mythtv.</div><div><br></div><div>My vision is that every check is an independent script... the community can supply the scripts for whatever they want to monitor and we would eventually get a large collection of scripts to monitor all kinds of things. For example, there might be a script to check on the status of your NFS share, another to check the status of an MD raid, another for a Dell PERC raid, another for Ext4 volume fragmentation, etc.</div>
<div><br></div><div>Each script can be triggered by one or more of a variety of events that the user could select. For example, some checks might only run when the backend starts, others daily, hourly, etc. Then you could select from a list of triggers that the backend can generate... recording complete, recording started, backend wakeup, etc.</div>
<div><br></div><div>Finally you can configure the reporting options for each script... have a popup on all your frontends, get an email, send the error to a syslog server, log it to a file, whatever.</div><div><br></div>
<div>
Maybe someday I'll try my hand at writing some code.</div></div></div></div>
</blockquote></div><br></div></div></div><div class="gmail_extra">Most of what you described is in Nagios. The MythTV specific stuff could be done fairly easily in Nagios as well. A bit heavy for this purpose, but definitely possible.</div>
</div></blockquote><div><br></div><div>Not sure if Nagios can be triggered by the backend, which would be a primary reason to do this. Perhaps some sort of interface to nagios could be used.. but I don't think that alerting is really that complicated a task.</div>
</div></div></div>