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.

Run these commands in a terminal on the macOS or Linux host where the affected FileWave component is installed, using an account authorized to run sudo. They are not commands for the FileWave Central application. If FileWave hosts your Server, contact FileWave Technical Support for Server service work; this is not a customer-side hosted-server procedure.

Stopping or restarting a service interrupts the work it handles. Coordinate the interruption with other administrators, and restart only the component required for the troubleshooting task.

macOS or Linux Server

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

Starting in FileWave 16.3 on macOS Server, fwcontrol uses supervisord under the hood for FileWave service control and status reporting. The commands below stay the same. The main change is that status and service detail output is clearer and no longer reflects the older LaunchDaemon-based behavior.

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. 

The following lines show command syntax for individual components. Replace start|stop|restart with exactly one action. For example, sudo fwcontrol apache restart restarts Apache. Do not paste the vertical bars into a shell: | creates a pipeline, not a choice between actions. Client and Booster commands apply on the host running that component.

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

Troubleshooting

If you find that the fwcontrol control command is not found, you re-create the alias by inputting this command and then try the fwcontrol commands again:

alias fwcontrol='/usr/local/bin/fwcontrol'