<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Times New Roman'; font-size:11pt; font-weight:400; font-style:normal;">On Tuesday 01 September 2009 15:03:04 Eric A. Boney wrote:<br>
> So since I haven't been able to figure out the cause of my tuner going "off<br>
> line" on my slave server I was hoping for a quicker fix for now. Seems that<br>
> once this tuner goes unconnected, the only way to fix it is to reboot the<br>
> server entirely. Even restarting the backend or stopping and then starting<br>
> it again still won't bring the tuner back to a connected status on the<br>
> master backend.<br>
><br>
> So is there anyway I can test the status of this tuner from the command<br>
> line so that I can setup a simple script to to reboot the system if the<br>
> tuner is in a non-connected status?<br>
><br>
> Does anyone else have any other ideas that could be causing the tuner to go<br>
> from connected to unconnected status every single day? There are no<br>
> messages in either the master or slave logs either.<br>
><br>
> Thanks,<br>
> -Eric<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Just wanted to update the thread just incase someone does a search in the future.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I sort of solved this by created a script to perform the following:<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>1. Pull down the status page via wget and check the status of the specific tuner.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>2. If the tuner status shows not connected then I have the script restart portmap, nfs-kernel-server and then the master backend. Not really sure if all three of these need to be performed yet as I haven't had a chance to really test it out piece by piece to see if only certain ones need to be done.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I am going to have this script run every couple of hours, maybe every hour not sure yet. I need to also set some more checking in the script to make sure that nothing is currently being recorded, transcoded or commercials being flagged before any of the services are reset.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>This at least resolved the issue of having to reboot the slave machine each time. I am still not sure why NFS is causing this OR why restarting the NFS on the master backend makes everything ok, but for now it is an automated fix that keeps all my tuners available.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-Eric<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>