You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried for the first time to configure the EventForwarder via the CB Response WebUI.
I was previously configuring the Event Forwarder via the config file and using the "tcpout=<fqdn/ip>:port" configuration.
The WebUI doesn't provide the option for a TCP output under "Type" and the new destination format (://[:]) has failed for me when I tried the following:
Type: syslog
tcp://syslog.localdomain:5514
tcp://10.10.10.10:5514
Error message: level=fatal msg="Error connecting to 'tcp://10.10.10.10:5514': dial tcp: lookup //10.10.10.10: no such host"
From my Event Forwarder / CB Response server I'm able to ping my syslog server without any issues via the IP or FQDN, I've even disabled my syslog server firewall just to make sure.
The only method I found for the process to start was by omitting the "" and using only this "://syslog.localdomain:5514". However, I believe it's a bug as the process starts but nothing is forwarded (no network comms observed via tcpdump) nor does it write anything to an outfile.
The text was updated successfully, but these errors were encountered:
Tried for the first time to configure the EventForwarder via the CB Response WebUI.
I was previously configuring the Event Forwarder via the config file and using the "tcpout=<fqdn/ip>:port" configuration.
The WebUI doesn't provide the option for a TCP output under "Type" and the new destination format (://[:]) has failed for me when I tried the following:
Type: syslog
tcp://syslog.localdomain:5514
tcp://10.10.10.10:5514
Error message: level=fatal msg="Error connecting to 'tcp://10.10.10.10:5514': dial tcp: lookup //10.10.10.10: no such host"
From my Event Forwarder / CB Response server I'm able to ping my syslog server without any issues via the IP or FQDN, I've even disabled my syslog server firewall just to make sure.
The only method I found for the process to start was by omitting the "" and using only this "://syslog.localdomain:5514". However, I believe it's a bug as the process starts but nothing is forwarded (no network comms observed via tcpdump) nor does it write anything to an outfile.
The text was updated successfully, but these errors were encountered: