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.
Could not authenticate. Invalid Token after Nagios Log upgra
-
lunabrasivi
- Posts: 1
- Joined: Thu Jan 18, 2018 4:09 am
Could not authenticate. Invalid Token after Nagios Log upgra
You do not have the required permissions to view the files attached to this post.
Re: Could not authenticate. Invalid Token after Nagios Log u
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:
Send me a private message with the /tmp/nagioslogserver.tar.gz file attached.
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.gzAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.