8.5

Edit

Installation troubleshooting

Many installation issues can be addressed with some basic steps:

  • Make sure that you have already properly configured firewall on all servers. This can be cause of errors during installation of some components. For more details please see the Configure open ports section.
  • Make sure that you have performed all steps from the Initial Linux Server configuration section. Selinux in running state or incorrect limits can be cause of errors during starting and running some components.
  • Make sure there is enough disk space on each server. Limited disk space can cause a failure to install, a failure to upgrade, or problems with running some components. See disk requirements in the system requirements.
  • Make sure that you have correct DNS configuration. This can be cause of errors for access to WF Web UI and S3 Emulator. For more details, see the Configure DNS server section.
  • In case of installation from non-privileged (non root) user all settings described in the Non root server prerequisites section (see above) should be applied. This can cause a failure to install, a failure to upgrade, or problems with running some components.

Ansible installer logs

If something goes wrong you can find installation logs in the log directory with the ansible installer.

Logs named in next format:

install_flat:{ operation }_%year%month%day%hour%minute
For example:

ls -1 <dir>/logs

install_flat:precheck_1801311305
install_flat:preinstall_1801311306
install_flat:check_1801311327
install_flat:install_1801311307

Using wfmanager to Control Services

There is a small utility called wfmanager that is aimed to facilitate management of WorkFusion applications. Login as <wf_user> and run the wfmanager command to use the utility:

# Will show status of all applications
wfmanager status

# Start, stop, restart individual services
wfmanager start nginx
wfmanager restart nginx
wfmanager stop nginx

# Show log tail of an application
wfmanager tail nginx

# Start, stop, restart all at once
wfmanager start all
wfmanager restart all
wfmanager stop all

# Show status and start an interactive console. 
# The console enables the user to run all the same commands without typing `wfmanager` every time.
wfmanager

There is a special "fake service" named start-all, used purely for autostart applications after (re)boot. There is no need to control it manually.

Checking logs

The logs for each individual application are stored for the application's stdout and stderr messages respectively as:

  • <wf_home>/supervisord/log/<app_name>.out.log
  • <wf_home>/supervisord/log/<app_name>.err.log
← PreviousNext →