Repair FileWave Server Permissions and Ownership
What
WhenA migratingFileWave aServer servermigration, manual file move, or simplybackup movingrestore can leave server files aroundwith the wrong owner or tryingpermissions. Services may then fail to restore from a backup you can inadvertently set the ownership or permissions incorrectly on the FileWave Server. This can lead to services not startingstart, or the database beingmay inaccessiblebecome until it is corrected.inaccessible.
When/WhyWhen to use it
You would useRun the includedbuilt-in scriptrepair whencommand doingafter anya migration or restore processwhen logs or anyservice timebehavior youpoint thinkto youincorrect mayFileWave haveServer changedownership theor permissions. Do not use it as a substitute for diagnosing unrelated startup failures.
HowRepair current FileWave Server releases
FromFileWave FileWaveServer 15.5.0 onward this is accomplished by a simple command and youlater doinclude notthe needfollowing tomanagement followcommand. any other steps. The command is below and you can pasteRun it in to an SSH or Terminal session;session:
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc set_fwxserver_permissions_and_ownershipAfter thisthe youcommand shouldcompletes successfully, restart the FileWave nowServer that the permissions are correct.services:
sudo fwcontrol server restartForUse olderthe versionslegacy ofscripts below only for a FileWave Server older than 15.5.00. theThey followingare legacyretained documentationfor andmigration scriptor isrecovery maintained:work involving unsupported releases.
Pre FileWave 15.5.0
ThereSelect are multiple versions of thisthe script fromthat changesmatches overthe time.server Asplatform mentionedand earlierFileWave inrelease. this article, fromFileWave 15.5.0 and beyondlater should use the scripts below are not needed because a built built-in command wasabove added. instead.
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 runRun the script.selected script from its downloaded location:
sudo ./fixfwxserverPermissions15Debian.sh
After itthe fixesscript permissions you will want tocompletes, restart yourthe FileWave Server.Server:
fwcontrol server restart