Could not authenticate. Invalid token given.

This support forum board is for support questions relating to Nagios Log Server, our solution for managing and monitoring critical log data.
jolson
Attack Rabbit
Posts: 2560
Joined: Thu Feb 12, 2015 12:40 pm

Re: Could not authenticate. Invalid token given.

Post by jolson »

Could you please send an email to [email protected] referencing this thread? I have some free time this afternoon if you want to get this session in soon - otherwise, we can come up with a date this week. Thanks!
Twits Blog
Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
User avatar
mike4vr
Posts: 89
Joined: Wed Feb 04, 2015 2:23 pm

Re: Could not authenticate. Invalid token given.

Post by mike4vr »

jolson wrote:Could you please send an email to [email protected] referencing this thread? I have some free time this afternoon if you want to get this session in soon - otherwise, we can come up with a date this week. Thanks!
Email sent. I'm definitely available this afternoon.
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Could not authenticate. Invalid token given.

Post by tmcdonald »

Going to lock this for now since we have received your ticket.
Former Nagios employee
jolson
Attack Rabbit
Posts: 2560
Joined: Thu Feb 12, 2015 12:40 pm

Re: Could not authenticate. Invalid token given.

Post by jolson »

The end result of this thread was that there were duplicate entries in /etc/sudoers. If anyone else is experiencing this problem, please run a following tail on poller.log:

Code: Select all

tail -f /usr/local/nagioslogserver/var/poller.log
While this tail is occuring, try to initiate a command from 'System Status'.
The error that we saw was very explicit - it mentioned sudoers line 167. In our case, there was a duplicate sudo file at /etc/sudoers.d/nagioslogserver - which we deleted:

Code: Select all

rm /etc/sudoers.d/nagioslogserver
After that removal, we uncommented the 'User_Alias' parameters in /etc/sudoers and saved the configuration - elasticsearch was able to be started properly from the Web GUI.

Best,


Jesse
Twits Blog
Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
Locked