Page 2 of 2
Re: Could not authenticate. Invalid token given.
Posted: Mon May 11, 2015 12:32 pm
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!
Re: Could not authenticate. Invalid token given.
Posted: Mon May 11, 2015 12:39 pm
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.
Re: Could not authenticate. Invalid token given.
Posted: Mon May 11, 2015 12:43 pm
by tmcdonald
Going to lock this for now since we have received your ticket.
Re: Could not authenticate. Invalid token given.
Posted: Mon May 11, 2015 4:59 pm
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:
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