sniproxy icon indicating copy to clipboard operation
sniproxy copied to clipboard

FAIL: reload_test on ubuntu-trusty-14.04-amd64-server-20140927

Open virtualjj opened this issue 11 years ago • 8 comments

First, thank you for this awesome tool!

I have this working on an Amazon AWS instance but I noticed that I get the following error:

FAIL: reload_test

See tests/test-suite.log

make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory /home/ubuntu/sniproxy/sniproxy-master/tests' make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory/home/ubuntu/sniproxy/sniproxy-master/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/home/ubuntu/sniproxy/sniproxy-master/tests' make: *** [check-recursive] Error 1

sniproxy 0.3.5: tests/test-suite.log

TOTAL: 17

PASS: 16

SKIP: 0

XFAIL: 0

FAIL: 1

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: reload_test

Prototype mismatch: sub main::make_config ($$) vs ($$$) at ./reload_test line 74. Subroutine make_config redefined at ./reload_test line 38. 2014-12-27 14:37:53 Parsed localhost 127.0.0.1:8083 2014-12-27 14:37:55 failed to reopen log file /tmp/rZhTfx9vZz: Permission denied 2014-12-27 14:37:55 reloading configuration from /tmp/1DZSd1dmQS 2014-12-27 14:37:55 init_config: unable to open configuration file: /tmp/1DZSd1dmQS 2014-12-27 14:37:55 failed to reload /tmp/1DZSd1dmQS curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (7) Failed to connect to localhost port 8082: Connection refused 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (7) Failed to connect to localhost port 8082: Connection refused 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (7) Failed to connect to localhost port 8082: Connection refused curl: (52) Empty reply from server 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server curl: (52) Empty reply from server curl: (7) Failed to connect to localhost port 8082: Connection refused 2014-12-27 14:37:57 recv(): Connection refused, closing connection curl: (52) Empty reply from server curl: (7) Failed to connect to localhost port 8082: Connection refused Test failed. worker failed with exit code 7 worker failed with exit code 7 worker failed with exit code 7 worker failed with exit code 7 server died with signal 11, with coredump worker failed with exit code 7 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 7 worker failed with exit code 52 worker failed with exit code 52 worker failed with exit code 7 worker failed with exit code 7 worker failed with exit code 7 worker failed with exit code 52 worker failed with exit code 7 worker failed with exit code 52

virtualjj avatar Dec 27 '14 15:12 virtualjj

Having the same problem.

aaomidi avatar Apr 10 '15 18:04 aaomidi

aaomidi - which AMI are you using? I haven't looked at this for a while but I can say that the application was functioning correctly for ami-3d50120d but I don't remember if I was still getting those error messages. Are you having problems getting SNI Proxy to work properly?

virtualjj avatar Apr 11 '15 06:04 virtualjj

Are you able to reproduce this outside of EC2? Does sniproxy work outside of the test suite? From the test log it looks like something else is running on TCP port 8082.

dlundquist avatar Apr 11 '15 06:04 dlundquist

i have the same problem, no something on port 8082

zhfish avatar Dec 27 '15 05:12 zhfish

I have the same problem. May I know how to solve this? I'm using Digital Ocean ubuntu 14.04

ken-ywk avatar Jan 13 '16 09:01 ken-ywk

@ken-ywk install the deb, no compile https://launchpad.net/~dlundquist/+archive/ubuntu/sniproxy/+packages

zhfish avatar Jan 13 '16 09:01 zhfish

Same problem. Ubuntu 14.04, x86_64

wacky6 avatar May 06 '16 06:05 wacky6

exactly the same problem. Centos 7 x86_64

oakaigh avatar Nov 09 '17 00:11 oakaigh