Hmm, OK, it seems that any time a "Search" includes anything found on the 
remote server it generates a null pointer. As long as all results exist in 
the local index it works. So either it's a bug or I have something 
configured wrong. Or something got screwed up during the update.

I see statistics about the remote index values. I see details about the 
remote index size in Indices. Nodes mentions only the local index. Sources 
shows me info about all sources in the remote index. 

On Thursday, June 4, 2015 at 8:42:08 PM UTC-7, Mark Moorcroft wrote:
>
> I yum updated both of my CentOS6 graylog servers to 1.1. The primary 
> server where all the ES indexes reside seemed to have worked no problem. 
> The second one that connects to the 1st seems to work perfectly in every 
> way, BUT any attempt to Search results in the Oops message. I see no errors 
> in the logs or the System Overview. Even my Dashboard with statistics on 
> source message qty values works.
>

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to