When your RMS installation is updated or the access.dat file is modified, you'll need to restart the server for the changes to take effect. This isn't hard, but does require SSH access to perform the necessary actions.
First, switch to the directory where RMS is installed on your server:
# cd /opt/rms
Now find and kill the current RMS process. To do this, run:
# ps aux | grep red5
This will output a list of processes mentioning "red5". Look for an entry like this:
root 39515 0.1 0.7 8567580 114236 ? Sl Mar25 22:17 /usr/local/jdk/bin/java -Dpython.home=li b -Dred5.root=/opt/rms - Dlogback.ContextSelector=org.red5.logging.LoggingContextSelector -Dcatalina.useNami ng=true -Djava.security.debug=failure -cp /opt/rms/boot.jar:/ opt/rms/conf:.:/usr/local/jdk/lib/classes.zip org.red5.server.Bootstrap
To kill the process, you'll need its unique identification number (NUM). This is the first batch of numbers after the user that spawned the process (root). Run:
# kill NUM
Where NUM is the number of the process.
Now restart the RMS server daemon. To do this, run:
It will take a few moments for the server to start up. Verify that the server has successfully started by navigating your browser to:
Where IP is the IP address of the server running RMS.
If you see the default Red5 message, the server was successfully restarted. If not, repeat the process above (kill and restart) until successful. Sometimes the RMS server will need a few subsequent restarts to capture the necessary ports to work properly.