--syslog doesn't seem to work about ghostunnel

[alokmenghrajani]

It's possible you are running into the condition commented here: https://github.com/square/ghostunnel/blob/master/main.go#L120

We should investigate and/or log a message when this condition happens.

[rickw]

This is on an Ubuntu 17.04 cloud instance. The main issues I was having was starting ghostunnel from Python with dynamic parameters so I tried the —syslog option.

The log messages seemed the same when I was starting with —syslog by hand from the terminal.

[csstaub]

If ghostunnel fails to setup syslog (with --syslog set) it should print an error to stderr and exit.

@rickw I am unable to reproduce your problem on macOS (on latest master). Can you confirm which version/revision of ghostunnel you are using, post the exact invocation you started the binary with, and maybe also provide us with the log output? I will setup a Ubuntu box to see if I can reproduce the problem there.

[csstaub]

Here's how I started ghostunnel:

❯❯❯ ./ghostunnel server --listen localhost:8443 --target localhost:8080 --keystore test-keys/server.p12 --cacert test-keys/root.crt --allow-cn client --syslog

And the corresponding syslog output:

❯❯❯ grep ghostunnel /var/log/system.log                                                          ✘ 130
Jan  2 10:34:30 comet ./ghostunnel[3657]: [3657] 2018/01/02 10:34:30.604197 starting ghostunnel in server mode
Jan  2 10:34:30 comet ./ghostunnel[3657]: [3657] 2018/01/02 10:34:30.608360 loaded certificate with common name 'server'
Jan  2 10:34:30 comet ./ghostunnel[3657]: [3657] 2018/01/02 10:34:30.609017 using target address localhost:8080
Jan  2 10:34:30 comet ./ghostunnel[3657]: [3657] 2018/01/02 10:34:30.609266 listening for connections on 127.0.0.1:8443