Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to configure syslog with tcp protocol via WebUI #191

Open
r-nd03 opened this issue Jul 23, 2020 · 0 comments
Open

Unable to configure syslog with tcp protocol via WebUI #191

r-nd03 opened this issue Jul 23, 2020 · 0 comments

Comments

@r-nd03
Copy link

r-nd03 commented Jul 23, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant