When logging in to the Web Interface, this error is displayed:
the HubRing service is not started. This can be checked in the command line with:
checking the HubRing's log file with
displays the following messages:
The cause for this behavior is the lack of disk space or a possible disk problem.
All the cache files are kept into the
/var/lib/hubring folder. At some point the volume that keeps the
/var folder was out of free space. Thus, the cache system was unable to update cache files and corrupted them.
To fix this you'll need to clear some space and to make sure that you will not end up in this situation again.
After you have done that, you have to fix the damaged
.aof file by following these steps:
STEP 1: After you receive the log message again, find out what
.aof file is damaged using this mental exercise: look at the
.rdb file from the message above (in our example
dump_2014-06-126.96.36.199_8.rdb), increment the number before .rdb with 1 and and change the extension to
.aof. The result is the corrupted file. For our example the damaged
.aof will be:
STEP 2: Run the following command to fix the damaged file:
Replace <damaged aof filename> with the name of the
e.g. For our example it would be:
The result should be something like this:
STEP 3: You are now able to start HubRing again, using this command:
STEP 4: Check HubRing's status:
You should see something like this:
After that you'll be able to log in again and also to have calls.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.