Changes to options on one system, result in changes to another system

[Lone_Stranger]

It seems when I update config.xml on system-B, the same changes are made without my permission to system-A.

I changed system-B's recording directory back to C:\Public\Videos during some maintenance. That change was also reflected, automatically, on system-A, resulting in an out-of-space condition.

Today, my config.xml was changed automatically, removing my userID and password for schedules direct. I'm apparently goin' looney.

I have three systems that each record programs, as well as multiple other client systems that do not record.

Can anyone shed some light?

Dale...

[Lone_Stranger]

Bump

[JavaWiz]

Hmm... Doesn't sound right. I think you are leaving out some pertinent information....

Are any of these systems setup as clients, or are they sharing a location for the config.xml file? Maybe you've installed NextPVR in a shared location, so all three systems are pointing to the same physical file?

[Lone_Stranger]

Thanks for the response.

No, the "other" systems are not clients. They are servers doing their own independent recording, each with their own ceton-PCI. However, each system has full access to all disks in the network, and I routinely play recordings from other systems.

I update something on "system-B", and it gets reflected on "system-A", almost like it gets synced. But, it doesn't do it all the time. The first time I noticed it, was when I ran out of space on the SSD for system-A (because the recording directory was magically changed). I thought that I must have done it by mistake, but on the next couple of occurrences, I verified it. Maybe I'm getting senile...

The most recent episode, was a change to UpdateEPG on system-C, which resulted in a reset of my SD credentials on system-A (Userid and password were reset, as well as EPG-days, in config.xml on system-A).

I know it sounds crazy, but, I swear...

Each different system also displays the tuners for "all" systems, and all systems also process (or attempt to process) all of them when recording. It seems eerie to see 15 tuners active in each NPVR on isolated systems. How is that done?

[martint123]

I have multiple servers and haven't seen anything like this (even with my constant tinkering).

I'd post a complete set of logs and config.xml from both server A and server B

[cncb]

Are you sure you didn't accidentally set the "DataDirectory" in the Registry to be a network shared directory? I did this at first and got similar unexpected results.

[Graham]

It seems when I update config.xml on system-B, the same changes are made without my permission to system-A.

NextPVR running on computer A will look in the registry of computer A to find the name of the folder that contains config.xml. NextPVR running on computer B will look in the registry of computer B to find the name of the folder that contains config.xml. This is the fourth law of thermodynamics and always applies in all circumstances and at all times and applies equally to NextPVR servers and NextPVR clients.

http://www.nextpvr.com/nwiki/pmwiki.php?...alledParts

[ACTCMS]

Are you sure you didn't accidentally set the "DataDirectory" in the Registry to be a network shared directory? I did this at first and got similar unexpected results.

NextPVR running on computer A will look in the registry of computer A to find the name of the folder that contains config.xml. NextPVR running on computer B will look in the registry of computer B to find the name of the folder that contains config.xml. This is the fourth law of thermodynamics and always applies in all circumstances and at all times and applies equally to NextPVR servers and NextPVR clients.

Perfectly true Graham... however cncb is suggesting that if the Registry entries of computer A and/or computer B have been changed such that both computers are pointing at the same physical DataDirectory then "unexpected" results are to be expected...

Alex

[Lone_Stranger]

I can assure you all that something changed System-A's config, multiple times, and I didn't do it.

I was afraid of posting this question, because I was worried about this kind of doubt. I guess I should have listened to me.

I suppose that it's also my imagination that all of the tuners on each system show up under System-A? (see pic)

I dunno..... Just forget it....

[sub]

I suppose that it's also my imagination that all of the tuners on each system show up under System-A? (see pic)

The Ceton device is in essence a network tuner, located using UDP broadcasts, even the internal PCI versions. I don't know what version you're using. If you're using a PCI/USB version, I wouldn't have thought the UDP discovery broadcasts from another machine would have found these, but if it is, then I can see it might be possible (since the device effectively adds a network bridge).

Regarding config changes being made on another independent machine, I can't really see this as being possible. There is nothing that'll broadcast settings changes to multiple machines. They're just reading and saving settings to a local config.xml file. There is the possibly it can happen when you're using a client/server setup (where 'act as client PC' is ticked), since the clients use the config.xml in the database share you specify for a subset of settings.

I'm sure there is a logical explanation. If you're sure it's happening, do some tests. Find a scenario that reproduces the problem, I'm happy to take a closer look for you. ie, change a setting one machine, and check that setting on the other machines.