Start a conversation

Cache Server Not Starting After Configuration Changes (On-Prem)

Overview

Jive system is completely down after attempting to integrate (or remove) multiple Cache servers.
Cache services do not start anymore. The following error message is received from either of the Cache servers after adding the hostnames:

  • Starting cache.....no process found. See logs: /usr/local/jive/var/logs/cache-service.out.

The error suggests checking the logs related with Cache Service for more details. This article provides instructions for clearing the Cache related configuration files to fix the issue.

Environment

Jive Interactive Intranet-Jive Core Jive On-Prem

Resolution

This issue can occur when adding or removing Cache servers. Some configuration files might be out of sync. In order to force-clean the configuration files, follow the instructions provided below:

  1. Navigate to the folder /usr/local/jive/voldemort/config.
  2. Delete the following hidden folders on each cache node:
    • .temp
    • .version
  3. Stop and Start the Cache Service on each Cache node

Confirmation

The Cache Service should start up fine after the forced cleaning of the configuration files.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments