Page 3 of 4
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 11, 2016 8:06 am
by roddergreg
curl -XGET '127.0.0.1:9200/_snapshot/logserverbackups':
{"logserverbackups":{"type":"fs","settings":{"compress":"true","location":"/usr/
curl -XGET '127.0.0.1:9200/_snapshot/logserverbackups/_all':
{"error":"ElasticsearchParseException[Failed to derive xcontent from (offset=0, length=0): []]","status":400}
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 11, 2016 1:36 pm
by rkennedy
{"logserverbackups":{"type":"fs","settings":{"compress":"true","location":"/usr/
Was this the full output from the command?
I'm a bit concerned if so. It should show the full path, but it looks like yours is getting cutoff at /usr/ and not respecting the path you've set.
Code: Select all
[root@localhost US]# curl -XGET '127.0.0.1:9200/_snapshot/logserverbacurl -XGET '127.0.0.1:9200/_snapshot/nls'
{"nls":{"type":"fs","settings":{"compress":"true","location":"/usr/local/nagioslogserver/logserverbackups"}}}
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Tue Aug 16, 2016 8:34 am
by roddergreg
Code: Select all
gcooper@wmsyslog1-prd # curl -XGET '127.0.0.1:9200/_snapshot/logserverbackups'
{"logserverbackups":{"type":"fs","settings":{"compress":"true","location":"/usr/local/nagioslogserver/logserverbackups"}}}gcooper@wmsyslog1-prd #
Code: Select all
cooper@wmsyslog1-prd # curl -XGET '127.0.0.1:9200/_snapshot/logserverbackups/_all'
{"error":"ElasticsearchParseException[Failed to derive xcontent from (offset=0, length=0): []]","status":400}
This is the full output.
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Tue Aug 16, 2016 2:27 pm
by rkennedy
Is submitting a ticket in an option for you? This might be better handled over a remote at this point.
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Wed Aug 17, 2016 8:16 am
by roddergreg
I believe our support plan only covers planned maintenance (upgrades etc.) We do not have customer support in our contract agreement.
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Wed Aug 17, 2016 12:12 pm
by mcapra
It looks like one of your snapshots is corrupted. Not quite sure how that happened (this can result from a lack of disk space), but I think the best course of action is to clear out the repository completely. There doesn't exist an easy way to identify which individual snapshot is corrupted.
Before we fully commit to that, can you share the output of:
Code: Select all
curator --dry-run delete snapshots --repository logserverbackups --all-snapshots
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 18, 2016 9:04 am
by roddergreg
uid=44371(nagios) gid=100(users) groups=100(users),48(apache),1000(nagios)
[nagios@wmsyslog1-prd ~]$ curator --dry-run delete snapshots --repository logserverbackups --all-snapshots
2016-08-18 10:04:30,387 INFO Job starting: delete snapshots
2016-08-18 10:04:30,387 INFO DRY RUN MODE. No changes will be made.
2016-08-18 10:04:30,608 ERROR Unable to find all snapshots in repository: logserverbackups
2016-08-18 10:04:30,608 ERROR No snapshots found in Elasticsearch.
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 18, 2016 9:52 am
by mcapra
Very strange behavior. Can you share the output of:
Code: Select all
ls -al /usr/local/nagioslogserver/logserverbackups/
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 18, 2016 10:33 am
by roddergreg
I deleted all the files in /usr/local/nagioslogserver/logserverbackups since you spoke of corruption. We have tape backups anyway. Can you post the default config file for eleasticsearch.yml? I think i might have changed this file when the problems started.
/usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yaml.
Please add as attachment and I'll replace what i currently have in place.
Greg
Re: NLS Backups not showing in Web UI Since upgrade to NLS 1
Posted: Thu Aug 18, 2016 1:49 pm
by mcapra
Here's my elasticsearch.yml, not sure if the yaml was a typo. Had to upload as txt due to forum restrictions; Make sure you change the extension!