[mythtv-users] Storage groups: How to set 'SGweightLocalStarting' to 0?

[Michael T. Dean]

On 10/08/2008 04:50 PM, Jonathan Larson wrote:
>> On 10/08/2008 01:24 PM, Kevin Kuphal wrote:
>>     
>>> Try running the backend with extra verbosity turned on for VB_FILE and/or
>>> VB_SCHEDULE and you should see a bunch of stuff printed out about the
>>> weighting used.
>>>       
>> And note that you'll need to restart Myth (master backend, meaning all
>> other stuff, too) when hand-editing the database.
>>
>> Still, though, you should fix the settings so it's one with NULL
>> hostname.
>>     
> Based on Mike's advice, I reduced my three SQL entries to 1:
>
> mysql> select * from settings where value = "SGweightLocalStarting";
> +-----------------------+------+----------+
> | value                 | data | hostname |
> +-----------------------+------+----------+
> | SGweightLocalStarting | 0    |          |
> +-----------------------+------+----------+
> 1 row in set (0.00 sec)
>   

And you're sure that hostname is actually NULL and not the empty string?

SELECT * FROM settings WHERE value IS NULL;

Some (esp GUI) clients don't handle NULL well.

> I also turned on verbose logging for file and schedule events and found this:
>
> 2008-10-08 13:30:41.043 Scheduler: FillRecordingDir: Calculating initial FS Weights.
> 2008-10-08 13:30:41.044   AVPC1:/mnt/AVPC1-rec1/recordings is local (-19). initial dir weight = -19
> 2008-10-08 13:30:41.045   AVPC1:/mnt/AVPC1-rec2/recordings is local (-19). initial dir weight = -19
> 2008-10-08 13:30:41.047   AVPC1:/mnt/AVPC2-rec1/recordings is remote (+0). initial dir weight = 0
> 2008-10-08 13:30:41.048   AVPC1:/mnt/AVPC2-rec2/recordings is remote (+0). initial dir weight = 0
> 2008-10-08 13:30:41.050   AVPC1:/mnt/AVPC3-rec1/recordings is remote (+0). initial dir weight = 0
> 2008-10-08 13:30:41.051   AVPC1:/mnt/AVPC3-rec2/recordings is remote (+0). initial dir weight = 0
>
> Notice that the local drives are still set at -19 even with the "SGweightLocalStarting" entry in place....
>
> Any advice would be appreciated. I can include more of the log as an attachment if that would be useful.

If you've got the hostname set right, something is causing it to not 
pick up the value.  Typically that will only be an issue when updating 
the DB while Myth is running.  Did you shut down all Myth frontends and 
backends, then update the DB, then restart and test?

Mike