Skip to main content

How to Restart FileWave Components

There may be times where you will need to restart all components within the FileWave server, or just a single component (postgres or apache). From your macOS or Linux server you can type "fwcontrol", which should give examples of fwcontrol usage.

macOS or Linux Server

You need to prefix commands with sudo to run them with elevated privileges.

At a command prompt:

sudo fwcontrol server stop
sudo fwcontrol server start

You can also accomplish the same end goal by performing a single command:

sudo fwcontrol server restart

It is a matter of preference, but some admins will prefer to execute a stop, then a manual start so that they can see all processes are indeed stopped. 

Subcomponents can be individually stopped as follows:

sudo fwcontrol apache start|stop|restart

sudo fwcontrol postgres start|stop|restart

sudo fwcontrol scheduler start|stop|restart



sudo fwcontrol client start|stop|restart

sudo fwcontrol booster start|stop|restart

Windows Server (Legacy)

Please note that FileWave Server on Windows is End of Life and you need to reach out to Customer Technical Support to ask about help from Professional Services to migrate over to Linux as soon as possible.

Make sure to start the command prompt with admin rights (Windows → cmd → r-click → Run as administrator)

"C:\Program Files (x86)\FileWave\bin\fwcontrol" server stop
"C:\Program Files (x86)\FileWave\bin\fwcontrol" server start
"C:\Program Files (x86)\FileWave\bin\fwcontrol" server restart
"C:\Program Files (x86)\FileWave\bin\fwcontrol" apache start|stop|restart

"C:\Program Files (x86)\FileWave\bin\fwcontrol" postgres start|stop|restart

"C:\Program Files (x86)\FileWave\bin\fwcontrol" scheduler start|stop|restart
Back to top