[mythtv-users] find_orphans and error?

[paul]

On 21/01/15 21:22, Bill Meek wrote:
> On 01/21/2015 02:23 PM, paul wrote:
> ...
>>
>> Here is the paste you wanted.
>>
>> <String>MicroServer</String>
>>
>> Which is the correct name. However the printout from the other mysql 
>> command probably explains a lot.
>> +-------------------+------+-------------+
>> | value             | data | hostname    |
>> +-------------------+------+-------------+
>> | BackendServerPort | 6543 | NULL        |
>> | BackendServerPort | 6543 | microserver |
>> | BackendServerPort | 6543 | server      |
>> | BackendServerPort | 6543 | vs          |
>> | BackendServerPort | 6543 | vs server   |
>> +-------------------+------+-------------+
>>
>>
>> This Mythbox was about 5 years ago called vs server, lack of 
>> knowledge called it vs , later "server" after a crash and did not 
>> read about how to
>> properly restore to another name server. Latest incarceration is 
>> microserver. I have been having problems with video storage groups 
>> complaining
>> about "unable to scan sg vs server" and I tried the trick of firing 
>> up a VM as a secondary backend, then removing it. Did not work for 
>> me, and
>> as we can see the name is still in the DB.
>>
>> I really wished I could wipe this machine, but I have so many rules, 
>> and recorded programs that it is not something I would want to do 
>> lightly.
>
> Since there is a valid entry for hostname microserver, that blows my 
> theory.
> I thought there was only a single entry with a NULL hostname.
>
> Maybe trying a really simple python script will point to the problem. 
> What does
> this (saved as test.py, chmod 755 test.py and then ./test.py) print:
> #!/usr/bin/env python
> from MythTV import MythDB
> db = MythDB()
> print 'Connected to DB OK using hostname: {}'.format(db.gethostname())
>
Hi Bill

Thank you for your help, here is the output of your script:-

paul at MicroServer:~$ ./test.py
Connected to DB OK using hostname: server


Regards Paul