-
Notifications
You must be signed in to change notification settings - Fork 869
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
Connection issue: goes up, accepts connections, but no forward #14
Comments
Are you 100%-sure that noone kills redsocks daemon with SIGINT or SIGTERM ? |
It should be fixed in master. release-0.2-4-gdcbdcae |
Closing due to inactivity. One of the possible reasons for the bug was already fixed. |
I am having exactly the same problem. I am using libevent-2.0-5 |
My problem is solved. Linux repo has an older version. I compiled from the sources and it worked. |
@pallavvasa what version caused troubles for you? |
The changelog shows the version 0.2-1 Changelog for redsocks (http://changelogs.ubuntu.com/changelogs/pool/universe/r/redsocks/redsocks_0.2-1/changelog) |
It looks like the connections are not being forwarded. This is the log that I get, any help is appreciated.
1305830541.173614 main.c:136 main(...) redsocks started
1305830541.182220 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:34235->127.0.0.1:8123]: accepted
1305830545.314117 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:40204->127.0.0.1:8123]: accepted
1305830545.567657 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:50745->127.0.0.1:8123]: accepted
1305830589.952484 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:51955->127.0.0.1:8123]: accepted
1305830642.700012 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:37212->127.0.0.1:8123]: accepted
1305830648.518951 main.c:142 main(...) redsocks goes down
1305830648.519439 redsocks.c:805 redsocks_fini_instance(...) There are connected clients during shutdown! Disconnecting them.
1305830648.520324 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:37212->127.0.0.1:8123]: dropping client
1305830648.521179 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:51955->127.0.0.1:8123]: dropping client
1305830648.521697 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:50745->127.0.0.1:8123]: dropping client
1305830648.522125 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:40204->127.0.0.1:8123]: dropping client
1305830648.522552 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:34235->127.0.0.1:8123]: dropping client
1305830649.680297 main.c:136 main(...) redsocks started
1305830649.683410 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:41455->127.0.0.1:8123]: accepted
1305830650.465576 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:42284->127.0.0.1:8123]: accepted
1305830684.795745 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:45418->127.0.0.1:8123]: accepted
1305830686.044189 redsocks.c:661 redsocks_accept_client(...) [127.0.0.1:60882->127.0.0.1:8123]: accepted
1305830686.594207 main.c:142 main(...) redsocks goes down
1305830686.594482 redsocks.c:805 redsocks_fini_instance(...) There are connected clients during shutdown! Disconnecting them.
1305830686.594665 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:60882->127.0.0.1:8123]: dropping client
1305830686.595642 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:45418->127.0.0.1:8123]: dropping client
1305830686.596221 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:42284->127.0.0.1:8123]: dropping client
1305830686.596740 redsocks.c:310 redsocks_drop_client(...) [127.0.0.1:41455->127.0.0.1:8123]: dropping client
The text was updated successfully, but these errors were encountered: