Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch
Dear alll, i found a couple of more places, where non-existing config sections might cause troubles. Will go through these more carefully and produce a new rc when done. -gn On 11.01.21 15:13, Gustaf Neumann wrote: Dear David, I could reproduce the behavior. The problem was due to a change about a year ago, which reduced code duplication in cases, where no section for nsproxy was provided in the configuration file. In reported case, it was looking for "ns/server/default/module/nsproxy". This explains as well, while this was not noted earlier. The version on bitbucket has this problem now fixed. I have extended the API slightly to reduce complexity. All the best and many thanks for the report. -gn ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch
Dear David, I could reproduce the behavior. The problem was due to a change about a year ago, which reduced code duplication in cases, where no section for nsproxy was provided in the configuration file. In reported case, it was looking for "ns/server/default/module/nsproxy". This explains as well, while this was not noted earlier. The version on bitbucket has this problem now fixed. I have extended the API slightly to reduce complexity. All the best and many thanks for the report. -gn ___ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
[naviserver-devel] ns_proxy segmentation fault under Debian Stretch
Hi,
I've done a build of NaviServer 4.99.20 rc1 and am hitting issues with the
ns_proxy command seg faulting.
I have a full backtrace of the seg fault here from our development
environment:
https://gist.github.com/davidqc/e41f7852de831de4b4b49f5d03f165b7
I can reproduce what looks like the same segfault from a basic build (at
the brand new rc2 level) also.
Fairly stumped at this - any ideas what's causing this?
The recreation steps are (from a fresh Debian Stretch install):
$ uname -a
Linux stretch 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64
GNU/Linux
$ sudo apt-cache policy tcl8.6
tcl8.6:
Installed: 8.6.6+dfsg-1+b1
Candidate: 8.6.6+dfsg-1+b1
Version table:
*** 8.6.6+dfsg-1+b1 500
500 http://cdn-aws.deb.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status
$ sudo apt-cache policy openssl
openssl:
Installed: 1.1.0l-1~deb9u2
Candidate: 1.1.0l-1~deb9u2
Version table:
*** 1.1.0l-1~deb9u2 500
500 http://security.debian.org/debian-security stretch/updates/main
amd64 Packages
100 /var/lib/dpkg/status
1.1.0l-1~deb9u1 500
500 http://cdn-aws.deb.debian.org/debian stretch/main amd64 Packages
# apt-get install build-essential git automake tcl8.6-dev libssl-dev
# git clone https://bitbucket.org/naviserver/naviserver.git
# cd naviserver
# ./autogen.sh --disable-ipv6 --with-tcl=/usr/lib/tcl8.6 --enable-rpath
--enable-threads --enable-symbols
# make
# sudo make install
# sudo useradd nsadmin
# sudo chown -R nsadmin:nsadmin /usr/local/ns/logs
Add nsproxy to /usr/local/ns/conf/nsd-config.tcl:
ns_section ns/server/default/modules {
ns_paramnscpnscp
ns_paramnslog nslog
ns_paramnscgi nscgi
ns_paramnsproxynsproxy.so
}
Then..
# sudo /usr/local/ns/bin/nsd -u nsadmin -t
/usr/local/ns/conf/nsd-config.tcl -c
% ns_proxy get test_pool
Segmentation fault
--
*David Osborne | Software Engineer*
Qcode Software, Castle House, Fairways Business Park, Inverness, IV2 6AA
*Email:* da...@qcode.co.uk | *Phone:* 01463 896 484
www.qcode.co.uk
___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
