Forum OpenACS Development: Re: Bind Variables in Log

2: Re: Bind Variables in Log (response to 1)

Posted by Gustaf Neumann on 09/15/18 11:41 AM

Setting Tcl variables in the server's config file does not affect the configuration, only when these variables are used in configuration settings (e.g. ns_param).

furthermore, the config file of NaviServer is different from AOLserver, so when when you take an only config file, don't expect it to work (rather look at the openacs-config.tcl in the naviserver repository for a sample config file).

have you seen [1]?
all the best.
-gn

[1] https://openacs.org/forums/message-view?message_id=5374519

3: Re: Bind Variables in Log (response to 2)

Posted by Raul Rodriguez on 09/17/18 04:17 AM

When I installed naviserver and openacs I used the installation scripts (https://openacs.org/xowiki/naviserver-openacs). On Debian 9 I followed these instructions:

cd /usr/local/src
git clone https://github.com/gustafn/install-ns
cd install-ns

sudo bash

bash install-ns.sh
bash install-ns.sh build

bash install-oacs.sh
bash install-oacs.sh build

After this, openacs started with the config.tcl file from the naviserver directory and /lib/systemd/system/example.service also used it:

/usr/local/ns/config-example.tcl

On openacs I ran letsencrypt (/var/www/example/packages/acs-subsite/www/admin/letsencrypt.tcl) from http://example.com/admin/letsencrypt. On successful completion, /usr/local/ns/config-example.tcl was automatically updated to point to the new certificate.

Since then, I have been using /user/local/ns/config-example.tcl. Based on your reply I updated this file and am now able to see the values of the bind variables. Next I will move everything over to use /var/www/example/etc/config.tcl.

Thank you for your help