Page History

Problem

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:

...

...
[11649] 21 Jun 04:26:41 * Server started, HubRing version 1.0.0
[11649] 21 Jun 04:26:41 * Mixed Persistence: SUCCESS on loading dump_2014-06-20.13.44.24_8.rdb
[11649] 21 Jun 04:26:41 # Bad file format reading the append only file: make a backup of your AOF file, then use ./hr-check-aof --fix <filename>
...

Solution

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 folder was out of free space.  ThusThus, the cache system was unable to update cache files and corrupted them.

To fix this you'll need to clear 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 damaged .aof file by following file by following these steps:

STEP 1:  After you receive the log message again,  find 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-20.13.44.24_8.rdb), increment the number before .rdb with 1 and and and and change the extension to to .aof.  The result is the corrupted file.  For For our example the damaged damaged .aof will will be:

dump_2014-06-20.13.44.24_9.aof

STEP 2:  Run the following command to fix the damaged file:

#> hr-check-aof --fix <damaged aof filename>

Replace <damaged Replace <damaged aof filename> with the name of the .aof file.

...

#> hr-check-aof --fix dump<dump_2014-06-20.13.44.24_9.aofaof>

The result should be something like this:

...

After that you'll be able to log in again and also to have calls.

Related

...

articles

...

...