FileWave Server Repair Permissions
What
When migrating a server or simply moving files around or trying to restore from a backup you can inadvertently set the ownership or permissions incorrectly on the FileWave Server. This can lead to services not starting or the database being inaccessible until it is corrected.
When/Why
You would use the included script when doing any migration or restore process or any time you think you may have changed the permissions.
How
For the moment there are 2 versions of this script that are current. Over time we will be updating this script and will ideally have a single script to make things more simple.
When you run this script you must stop the FileWave Server so that none of the files are locked. This is easily done with "sudo fwcontrol server stop" to make sure it is stopped.
You can copy the link to the file from below and do "wget https://kb.filewave.com/attachments/283" for instance for the Debian script and then just unzip it. "unzip ./283" to unzip the script. Planned for a release in 2024 there will be a simple management command included with FileWave Server that has this a built in function.
Fix Permissions FileWave 15+ (Debian) | Fix Permissions FileWave 14+ (macOS/CentOS)
If you are on an older version of FileWave use of these instead:
Fix Permissions v13.1.5+ | Fix Permissions v13.1.4 or older
You can use wget to download the correct script and then rename it to anything.zip if it didn't get a .zip name and unzip it. You will need to give the script 755 permissions to run it. You will run the command to the path to the script. For the example it is in the current folder we are in so we use ./ before the name.
sudo chmod 755 ./fixfwxserverPermissions15.sh
Then you will need to run the script.
sudo ./fixfwxserverPermissions15Debian.sh
After it fixes permissions you will want to restart your FileWave Server.
fwcontrol server restart