Open gianluca-valentini opened 2 years ago
Hi, any update? This strange behaviour che i submit also the last year, is blocking the graylog SAAS scenarios as I cannot be sure that a standard installation with a valid input and content pack is correctly installed
Can you tell me if there should be a workaround?
Is there any update about this issue?
Hi all, is there any update about this issue? So, how did you create an input installation that have to be the same in different client environments? Did you use content pack or exist something different that can be used?
Hi, I’m using Graylog 4.1.6 I created a rule for text matching and I export it with it’s pipeline, stream and new input, using contentpack. After that I upload and install it on a new enviroment without problems, but when I looked the input it was in a not started status. If I try to start it Graylog give me an error message. Looking the Graylog log I see this error:
The input is present on the port 5044 that is not used in other input.
using sudo netstat -tunlp I see this port mapping
It seems that graylog could have problems on input creation by contentpack.