[mythtv-users] Historical SG now long gone but still try's to scan?

[Hika van den Hoven]

Hoi paul,

Tuesday, December 16, 2014, 12:02:23 PM, you wrote:

> Thank you all for the help, really appreciated, bit out of my depth with
> this one.

> Now I know I should probably know this, but I have a number of config.xml

> /etc/mythtv/config.xml
> /home/mythtv/.mythtv/config.xml
> /home/paul/.mythtv/config.xml  (me when I login to desktop)
> /usr/share/doc/mythtv-backend/contrib/config_files/config.xml
> /usr/share/mythtv/config.xml

> So which one exactly? And is there anyway to take a peek at what the DB
> thinks the hosts are? The new servers hostname is MicroServer, and I 
> assume that myth got the previous names from the DB when I restored it.
> Now to be fair to myth, I found out after the event that restoring to a
> new machine there were procedures I should have taken when the original
> server died. However the orginal machine was called just server, later
> when I was recovering the DB I restored it to VS (Yep virtual server) 
> Think I am paying the price for a botched recovery. Oddly enough all the
> recordings are there, as well as all the schedules and rules?

> Paul


> On 15/12/14 20:04, Andre Newman wrote:
>> On 15 Dec 2014, at 20:17, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>>
>>> On 12/15/2014 11:43 AM, Andre Newman wrote:
>>>> On 15 Dec 2014, at 17:32, paul wrote:
>>>>
>>>>> Thanks for the reply.
>>>>>
>>>>> Not sure myself what part solved your problem? Only one I understood was setting up another server with the missing name and creating a slave backend? Wonder how that works when your Storage Group actually says when being scanned "Server VS" Now the current server is called "Server" Yeah I know :-) was suffering from lack of originality! And the old one was called "vs"
>>>>>
>>>>> Did I assume correctly that setting up another server was the answer?
>>>> That’s what I did to fix it on my system. In my case it was a long retired experimental slave backend but I believe it would have the same effect for a long gone regular backend.
>>>>
>>>> I installed mythbackend on a spare pc (or a vm would probably suffice) edited config.xml to use the exact hostname of the retired server and configured it as a slave backend. Then I did scan videos and all the old data was cleared out, just removed the slave backend after that and all was well.
>>> You don't need a separate PC--just edit config.xml to specify a LocalHostName override on some existing system (even a frontend-only system).  Just make sure that the directories specified in the Videos Storage Group aren't accessible (unmounted/parent directory renamed/...).
>>>
>>>> If you had a different storage group on the old backend you’d need to configure that on the slave but if it was the same as you have now it will follow across from the master backend.
>>> If you're trying to clear all the videos from that host, you don't need (want) any SG directories, so no need to configure any.  Just make sure that no directory in any host's Videos SG is accessible on this system when you run the scan.
>>>
>>>> Bit of a faff just to delete a few (non existent) videos but it does work.
>>> Yes, you have to go through a "bit of a faff" is you want it to "automatically" remove them for you with a scan.  The alternative is to use the Video Manager to delete the few (non existent) videos.
>> That didn’t work when I had the problem, I know you said it was planned to add this for parity with recordings but apologies I didn’t know it had been done.
>>
>> Andre
>>
>>
>>> Mike
>>> _______________________________________________

You best make them simlinks to each other. I think the one in /etc is
dominant.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens