sniproxy icon indicating copy to clipboard operation
sniproxy copied to clipboard

error with make check

Open nexusofdoom opened this issue 8 years ago • 7 comments

ubuntu server 16.04

make[2]: Entering directory '/home/travus/Downloads/sniproxy/tests' make[3]: Entering directory '/home/travus/Downloads/sniproxy/tests' PASS: http_test PASS: tls_test PASS: buffer_test PASS: table_test PASS: address_test PASS: cfg_tokenizer_test PASS: binder_test PASS: functional_test PASS: bad_request_test PASS: slow_client_test PASS: fallback_test PASS: reload_test PASS: connection_reset_test PASS: bind_source_test PASS: fd_limit_test PASS: reuseport_test PASS: ipv6_v6only_test FAIL: config_test PASS: resolv_test FAIL: bad_dns_request_test

Testsuite summary for sniproxy 0.5.0+git.19.g7cbd992

TOTAL: 20

PASS: 18

SKIP: 0

XFAIL: 0

FAIL: 2

XPASS: 0

ERROR: 0

============================================================================ See tests/test-suite.log

Makefile:823: recipe for target 'test-suite.log' failed make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory '/home/travus/Downloads/sniproxy/tests' Makefile:929: recipe for target 'check-TESTS' failed make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory '/home/travus/Downloads/sniproxy/tests' Makefile:1135: recipe for target 'check-am' failed make[1]: *** [check-am] Error 2 make[1]: Leaving directory '/home/travus/Downloads/sniproxy/tests' Makefile:372: recipe for target 'check-recursive' failed make: *** [check-recursive] Error 1

nexusofdoom avatar Jan 06 '18 04:01 nexusofdoom

in dmesg I see this

sniproxy[22917]: segfault at 0 ip 00007f344fe73264 sp 00007ffe75d9f120 error 4 in libc-2.23.so[7f344fe06000+1c0000] [ 1543.076131] sniproxy[25358]: segfault at 0 ip 00007efc96d03264 sp 00007ffd879adcb0 error 4 in libc-2.23.so[7efc96c96000+1c0000]

nexusofdoom avatar Jan 06 '18 04:01 nexusofdoom

========================================================== sniproxy 0.5.0+git.19.g7cbd992: tests/test-suite.log

TOTAL: 20

PASS: 18

SKIP: 0

XFAIL: 0

FAIL: 2

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: config_test

Failed to parse config FAIL config_test (exit status: 1)

FAIL: bad_dns_request_test

2018-01-05 22:35:24 Only socket address backends are permitted when compiled without libudns 2018-01-05 22:35:24 error parsing /tmp/6FrC5qpuCG at 269 near: 2018-01-05 22:35:24 250

2018-01-05 22:35:24 258 table {

2018-01-05 22:35:24 270 .* *:80

2018-01-05 22:35:24 272 }

2018-01-05 22:35:24 272 (null) Unable to load /tmp/6FrC5qpuCG Usage: sniproxy [-c ] [-f] [-n ] [-V] couldn't connect Connection refused at ./bad_dns_request_test line 49. couldn't connect Connection refused at ./bad_dns_request_test line 49. couldn't connect Connection refused at ./bad_dns_request_test line 49. Test failed. worker failed with exit code 111 worker failed with exit code 111 server failed with exit code 1 worker failed with exit code 111 FAIL bad_dns_request_test (exit status: 1)

nexusofdoom avatar Jan 06 '18 04:01 nexusofdoom

but if I do this

Build a Debian package

./autogen.sh && dpkg-buildpackage Install the resulting package

sudo dpkg -i ../sniproxy__.deb

I can run

sudo service sniproxy and it shows it is running no issues

nexusofdoom avatar Jan 06 '18 04:01 nexusofdoom

Only socket address backends are permitted when compiled without libudns

It looks like you don't have libudns-dev installed on your system so DNS related features are disabled and the tests related to these are failing. If you intend to proxy to anything besides an IP address or UNIX socket you will need to install libudns and re-run the configure script.

If you are intending to build sniproxy with DNS run ./configure --disable-dns to exclude these features and tests.

dlundquist avatar Jan 06 '18 05:01 dlundquist

shows that its already installed

sudo apt-get install libudns-dev Reading package lists... Done Building dependency tree Reading state information... Done libudns-dev is already the newest version (0.4-1).

nexusofdoom avatar Jan 06 '18 05:01 nexusofdoom

Could you try building it with the --disable-dns flag and telling us what happens?

Given that it's suspected, this could confirm if it's a problem with libudns. It could be some sort of reference issue where it's looking in the wrong place for libudns, this would confirm and would dramatically narrow the search for the cause.

shiribailem avatar Jan 07 '18 02:01 shiribailem

ok will try I will be out tell the 12th so some time end of next week will keep you posted.

nexusofdoom avatar Jan 07 '18 04:01 nexusofdoom