Hello Lorne,I appreciate you took the time to respond to my question.
<<It sounds like your workstations are still mounting their /var/snd to the old
server.>> Yes, that was the problem. I guess my CORE question then is how to
be sure that the file mount for /var/snd on my workstations points to the new
server, since fstab uses UUID, and that line in fstab doesn't show whether is
pointing to the new or the old server, because it uses the universal ID number
for the /sda for /var, mounted in the workstation, with absolutly no reference
to the server. The old way to mount a file in fstab required to specify the IP
of the machine where we wanted to mount a file, like IP_ADRESS:/var/snd
/var/snd ...etc.
I checked the HTTP Xport and core engine boxes and it is what always has been:
localhost.
I will check the .SQL again, although I almost sure that the .SQL is ok since
the system is working flawlessly now after reinstalling Rivendell 3 in each
workstation.
All I want is to be prepared if this happens again, so I can have a smoother
transition. I guess I have been trying to avoid the hot standby option that
usually stops working after an update.
In all, I still need help with my CORE question above.Thank you very much Lorne.
On Thursday, October 1, 2020, 08:10:16 AM MST, Lorne Tyndale
<[email protected]> wrote:
Hi, It sounds like your workstations are still mounting their /var/snd to the
old server. Double check that the file mount for /var/snd on your
workstations points to your new server (and ensure all the needed permissions
are correct). Regarding the rdxport stuff, that can be changed in rdadmin.
Launch rdadmin --> manage Hosts --> select the needed workstation host --> HTTP
Xport. Give this a check / try, but given the way you set up the new server
you might have other issues. After making these changes in rdadmin you might
have to restart the daemons on the workstations. I suspect that by editing the
.SQL file like you did, the entry for your server in rdadmin may have the wrong
host name, especially if you gave your new server a different host name then
your old one. This can also be the cause of issues with rdxport not working as
expected. Rather then manually editing IP's in the SQL file it probably would
have been a better approach to import the database on your new server and
either: a) create a new host entry in Rivendell for the new server, when
creating base it off the entry for the old server, *or* b) give the new server
the sane exact host name and IP address as the old server, then when switching
make sure the old is shut off (or disconnected from the network). You'd have
to remount the file share / restart daemons on the workstations. Lorne Tyndale
The system started working apparently fine, until we shutdown the old server.
Problem: The Rivendell work stations were receiving the information from the
new server’s sql data base, but playing the audio files from the old server
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
