Restarting Faspex and Common Aspera Services

Faspex Services

Restart Faspex services using the asctl command:

# asctl faspex:restart

Restarting Aspera Services

If configuration changes you have made are not taking effect, or Faspexis otherwise not working as expected, the problem may stem from Aspera services not having been started or restarted. Examples:

  • If you did not choose to start services such as Aspera Node Service (also known as Aspera NodeD) when prompted to do so during the Faspexsetup process, you may need to start them manually.
  • Changes to aspera.conf may require you to restart Aspera Central (asperacentral) or Aspera NodeD (asperanoded). For example, any changes to the <central_server> section of aspera.conf (such as enabling <persistent_store>) require you to restart Aspera Central.
  • If you see a notice about transfer server errors on the login page for Faspex, you need to install or update your IBM Aspera High-Speed Transfer Server license.
To check whether the Aspera node service or Aspera Central is running, you can use the ps command and grep for aspera, then look for asperanoded or asperacentral; for example: 
# ps -e | grep aspera
To restart asperanoded or asperacentral: 
# service asperacentral restart
# service asperanoded restart