Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-25 Thread David Osborne
Thank you - working perfectly now. On Sun, 24 Jan 2021 at 18:23, Gustaf Neumann wrote: > Dear all, > > The 4.99 branch (bug-fix branch for the 4.99 family) is now updated > with the change of David. Additionally, i have added basic test cases via > introducing a new command "nscp users". > > al

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-24 Thread Gustaf Neumann
Dear all, The 4.99 branch (bug-fix branch for the 4.99 family) is now updated with the change of David. Additionally, i have added basic test cases via introducing  a new command "nscp users". all the best -g https://bitbucket.org/naviserver/naviserver/commits/782e8cbd4529d548a9667a2eb0f2e370b8

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-21 Thread Gustaf Neumann
Hi David, Many thanks for that details, this helps a lot. I will look into this, but probably, the weekend is the earliest time. Now, i understand the problem at least. all the best -g On 21.01.21 16:15, David Osborne wrote: I dug a bit more into why NaviServer at master might not be allo

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-21 Thread David Osborne
Hi again, I dug a bit more into why NaviServer at master might not be allowing us to configure any nscp users. I created a pull request to show you which changes got it working for us. At master, for us, LoadUsers ignores any nscp users defined in the "ns/server/default/module/nscp/users" section

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-19 Thread David Osborne
Hi again, One issue I'm noticing since these changes is that setting up users for the control port has changed. Using the default config of nsd-config.tcl from master (the same basic test case from the top of this thread): sudo /usr/local/ns/bin/nsd -u nsadmin -t /usr/local/ns/conf/nsd-config.tc

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-12 Thread David Osborne
Thank you for a very quick turnaround Gustaf! I'll do a build at rc4 and continue testing. Regards, On Tue, 12 Jan 2021 at 10:16, Gustaf Neumann wrote: > On 11.01.21 16:45, Gustaf Neumann wrote: > > Will go through these more carefully and produce a new rc when done. -gn > > The updated version

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-12 Thread Gustaf Neumann
On 11.01.21 16:45, Gustaf Neumann wrote: Will go through these more carefully and produce a new rc when done. -gn The updated version is running since yesterday on openacs.org (4 virtual servers [1]), i have tested also with macOS 10.14.6, Ubuntu 20.04, Fedora Core 32, OpenBSD 6.8 (LibreSSL 3

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-11 Thread Gustaf Neumann
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 ab

Re: [naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-11 Thread Gustaf Neumann
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

[naviserver-devel] ns_proxy segmentation fault under Debian Stretch

2021-01-11 Thread David Osborne
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 s