Could not authenticate. Invalid Token after Nagios Log upgra

This support forum board is for support questions relating to Nagios Log Server, our solution for managing and monitoring critical log data.
Locked
lunabrasivi
Posts: 1
Joined: Thu Jan 18, 2018 4:09 am

Could not authenticate. Invalid Token after Nagios Log upgra

Post by lunabrasivi »

Hi we are experiencing in the "Could not authenticate. Invalid Token" issue after upgrade to the new version of Nagios LogServer

We try to regenerate api keys for the current nagiosadmin user but nothing happened.
The status of the server is green, and the same result from the configuration check tool.
No warnings from the logstash and elasticsearch logs.
Here attached the screenshots.
You do not have the required permissions to view the files attached to this post.
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Could not authenticate. Invalid Token after Nagios Log u

Post by cdienger »

When you say 'nothing happened' when you try to regenerate the api key for nagiosadmin, does that mean that the api key is staying the same?

Run "tail -f /var/log/elasticsearch/*" on the NLS command line and then try generating a new key for the nagiosadmin user and see if any messages are generated.

I'd like to see that as well as a copy of the settings database. You can get this from the command line as well:

Code: Select all

curl -XPOST http://localhost:9200/nagioslogserver/_export?path=/tmp/nagioslogserver.tar.gz
Send me a private message with the /tmp/nagioslogserver.tar.gz file attached.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked