Nagios Support Forum

We are on the latest 1.3.0
This is the version we installed, not an upgrade from a earlier version.

I reran the following commands at 11:30 local time on each server: python /usr/lib/python2.7/site-packages/curator/curator.py show --show-snapshots --repository 'backup' python /usr/lib/python2.7/site-packages/curator/curator.py snapshot --older-than 1 --repository 'backup' Then I ran on each server...

We are on version 1.3 python /usr/lib/python2.7/site-packages/curator/curator.py show --show-snapshots --repository 'backup' This out puts the following: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/curator/curator.py", line 736, in <module> main() File "/...

I have reverted the HEAP changes back to default. Information requested below: md5sum /usr/lib/python2.7/site-packages/curator/curator.py 9d19626b8486f05156c77a0dacc93343 /usr/lib/python2.7/site-packages/curator/curator.py curl localhost:9200/_snapshot/_all {"backup":{"type":&quo...

I increased each server to 32GB. Still getting the same error: 2015-11-25 15:29:29,804 INFO Beginning SNAPSHOT operations... Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/curator/curator.py", line 736, in <module> main() File "/usr/lib/python2.7/site-packag...

I changed the heap size to 8g and this was ok but still received the same issue.

Currently it is set to ES_HEAP_SIZE=$(expr $(free -m|awk '/^Mem:/{print $2}') / 2 )m If I set this to ES_HEAP_SIZE=4g I believe this would give ES less memory than is already being allocated. I tried it as 4g and now there is 65% free memory out of 16GB when it was 36% free so ES doesn't have as muc...

I have two servers in a cluster each with a backup share mounted locally. It managed to backup the first days backup then stopped working. No "backup snapshots" are present in Backup and Maintenance. Both servers can access the share. I have reset all jobs and rerun but still doesn't work....

Great thanks for that, sometimes we need to double check things just to be sure. After I installed I added another drive and moved the directory and data to the new drive. Was this on the new or existing server? Did you follow any documented procedure for this? What is the permissions of: ll /mnt/s...

Reverted the move of the data directory and can now add to the cluster. Moved the data back to the new drive and all is well. I guess shouldn't be changing data around until the cluster is setup... How this would work when you have large amounts of data already to replicate and the drive you initial...