search

graylog-labs / graylog2-web-interface

[DEPRECATED]
https://www.graylog.org/
611 stars 174 forks source link

Web interface notifications would not go away. #911

Closed sauliuspr closed 9 years ago

sauliuspr commented 10 years ago

Administrator users role gets system notifications like: "There was no master graylog2-server node detected in the cluster. 7 hours ago". "You are running an outdated Graylog2 version. 10 hours ago"

These message will not go away. Since only option for users to have search ability is to assign them administrator rights everyones sees those messages and are wondering is everything is ok with graylog.

edmundoa commented 10 years ago

Hi,

Thank you for reporting this issue!

It would really help us if you could specify the Graylog2 version you are using, and attach any logs from the server and web interface that appear when you try to remove the notification (there should be a button for that in the upper-right corner of the notification).

sauliuspr commented 10 years ago

Graylog Server and Graylog Webserver is ver. 0.20.6. Also I've tried removing notification from mongo by executing db.notifications.remove({}) messages comes back. /etc/graylog.conf DOES have "is_master = true"

screen shot 2014-09-25 at 5 58 08 pm

Here is an interesting fragment from server log: 2014-08-27 19:56:53,384 ERROR: org.graylog2.periodical.ClusterHealthCheckThread - Unable to find own node: org.graylog2.cluster.NodeNotFoundException: Did not find our own node. This should never happen. at org.graylog2.cluster.Node.thisNode(Node.java:95) at org.graylog2.periodical.ClusterHealthCheckThread.getNotification(ClusterHealthCheckThread.java:34) at org.graylog2.periodical.ClusterHealthCheckThread.run(ClusterHealthCheckThread.java:23) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

sauliuspr commented 10 years ago

I turns out there was a typo in /etc/graylog.conf elasticsearch nodename - after changing and restarting master server, notification went away... I wounded if it won't come back.

edmundoa commented 10 years ago

Ah, good to know. I'll keep the ticket open for a while, please let us know if that happens again!

sauliuspr commented 10 years ago

Well, "no master" error message went away. However "outdated Graylog version" message pops up every thime admin user logs in.

edmundoa commented 9 years ago

Good to hear that the notification went away for good! Regarding the update notification, the message appears constantly mainly because notifications are not tied to a user at the moment, so we can't hide the notification for a single user. I created #1147 to think about how to improve that.