<https://lh3.googleusercontent.com/-1sW8Wn_W8qc/WFAmtzmNe2I/AAAAAAAAtUk/SYghaYB-1z4Taz6IjVmjUZLNh1lUhbMWgCLcB/s1600/Screen%2BShot%2B2016-12-13%2Bat%2B10.44.30%2BAM.png>
I can see that this is being ingested on a 'deleted_input'.  See attached 
screenshot.

Any clue on why this is happening and how I can move out of a 
'deleted_input'?




On Tuesday, December 13, 2016 at 10:16:37 AM UTC-6, Jason Close wrote:
>
> I'm trying to play around with some of the marketplace stuff, and I've 
> found a problem.
>
> I have created a Syslog UDP input on a particular port, and have named it 
> 'IIS'.
>
> I let it run, and it was working great.
>
> I then deleted it, and later came back and recreated that same input.
>
> Now, I cannot get data to show up when I query the received messages for 
> that input, no matter the time range.
>
> Is it possible that something is not getting properly updated or deleted 
> within the config of Graylog that tells it which input buffer to look in?
>
> I looked at the old 'gl2_source_input' identifier, as well as the new one, 
> and they are indeed different.  But with 1k EPS coming in for that input, I 
> should definitely see immediate data.
>
> How can we determine what kind of bug this is?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/aaa637e9-ecbf-4568-87d3-a12681c3015b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to