redir doesn't start

[stiv-yakovenko]

Built redir, but it doesn't start:

[troglobit]

Just tested the latest master, which is same as v3.3, and it works here. Both foreground and in the background like you run.

You'll have to tell me a bit more about your setup, the version of redir you're using etc.

[stiv-yakovenko]

Thank you for your feedback. I use Centos 7, built from lastest git sources. Any particular details?

[troglobit]

Well, how did you run the configure script; args, any special environment perhaps, the output from the configure script and the config.log file would be a start. I'll see if I can fire up a CentOS machine later today.

[troglobit]

It just hit me, do you have any SELinux, Apparmor or other policy/access control mechanism enabled? You can usually see the kernel denying application access in the dmesg or other kernel log file, dunno how/what CentOS/RedHat does here.

[stiv-yakovenko]

well, may be, but i'd expect error message if it fails to listen?

[stiv-yakovenko]

I can give you ssh for debugging purposes if you wish

[troglobit]

Have you tried running it in the foreground with debug messages enabled?

./redir -n -l debug 0.0.0.0:2222 127.0.0.0:2222

I agree, there should be an error message, could be the wrong log level is set, but -l debug should catch that.

Let's keep ssh login as a backup.

[stiv-yakovenko]

HI! Will check today's evening, busy right now.

[stiv-yakovenko]

ok, -n gives error message, but in bg mode it doesn't, which is a bit missleading in my opinion.

[troglobit]

Could you please tell me what the error message is? When redir runs in the background it cannot log to the terminal it starts from, only to syslog like other daemons. Maybe the error message is available in /var/log/syslog?

[stiv-yakovenko]

Well, it said port was busy. I think may be its not a bug at all...

[troglobit]

You can check open/used ports with netstat or ss. Maybe you already have an application listening to 2222?

[stiv-yakovenko]

yeah, the problem itself is solved, but no message was a bit missleading :)

[troglobit]

Like I said, when redir runs in the background (default) it has detached from the terminal (to protect itself from being killed if you close your terminal), so it cannot give you any feedback other than in the syslog. This goes for all UNIX daemons. I understand that can be a bit confusing, but I have not tried to mislead you our any other user in any way. I just want to make this clear.

OK so we can close this issue then?

[stiv-yakovenko]

yes, close it