Restarting the Access Service or Content Service

Problem

There is an issue with the content or access service on a particular customer system.

One or more nodes are believed to be having problems.

Solution

Restart the Access Service or Content Service node.

In order to restart a node, command line access (e.g., Terminal or Console) is required to the access service or content service node/s.

This example assumes there are multiple nodes within this example setup

  • If users cannot login, or access the login page, the issue is with the access service
  • If users can login, but cannot upload or list data, the issue is with the content service

After determining if the issue is with the access or content service, command line access is required to manually check the application service status (and/or restart nodes).

If you have no command line access to the environment, the below instructions can be copied and sent to the operations or infrastructure team of the customer.

  1. Note: Public key or username/password credentials will be required for the node

  2. ssh 'content-service-node-url.com' or ssh 'access-service-node-url.com'
    1. Confirm 'yes' if prompted

    2. (known hosts)
  3. sudo su
  4. service access-service status or service content-service status
  5. service access-service restart or service content-service restart
  6. after 30 seconds, ensure the access service or content service is running by typing

    1. service access-service status or service content-service status
    2. Curl http://localhost:8080/status 8081(content)
  7. If the service status is running, a restart has been successful
  8. If the service will not restart, capture the acess-service.log or content-service.log see Accessing and copying log files
  9. Escalate with the log to support personnel for further diagnosis