License Violation Issues

jan · March 1, 2018, 8:05am

Did you have http_proxy set in your Graylog configuration?

Graylog2/graylog2-server/blob/2.4.3/misc/graylog.conf#L529


# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_read_timeout = 10s


# The default write timeout for outgoing HTTP connections.
# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
# Default: 10s
#http_write_timeout = 10s


# HTTP proxy for outgoing HTTP connections
#http_proxy_uri =


# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
# cycled indices.
#
# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these
#            to your previous settings so they will be migrated to the database!
#disable_index_optimization = true


# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch

Other option would be to raise the http_read_timeout - maybe the connection to the API isn’t the fastest…

Topic		Replies	Views
License violation message Graylog Central (peer support)	6	3556	July 23, 2018
Enterprise License Violation Graylog Central (peer support)	2	1825	March 26, 2018
Enterprise license error still occure Graylog Central (peer support)	11	1642	March 10, 2020
License violation problem Graylog Central (peer support)	4	1200	August 16, 2021
New License, Violation Too Much Traffic Graylog Central (peer support)	6	984	May 22, 2020

License Violation Issues

Related topics