Re: tracker does not want to send mail

Hi Ed:

In message <PH7PR12MB56564B8BF419D430481C3455844C9@PH7PR12MB5656.namprd12.prod.
outlook.com>,
Ed Trumbull writes:
>Great strides forward!
>
>Emails are now sent.

Woo hoo!!! Great news.

>One thing I have had to do is specify the n= p= and d= options on the
>invoking command line instead of within the config.ini file. I'm not
>sure why that's the case, but I'll take it.

The config.ini file in the tracker home directory configures the
tracker, not the method used to run the tracker (or trackers). E.G. if
you use wsgi, the role of roundup-server is done by another program
(gunicorn, uwsgi) that have their own configurations. Some examples
are given in the installation documentation.

If you are asking why we need to be able to run the server at a
different address/port from the web setting in config.ini, I can
explain that.

Suppose you have an external (exposed to the internet) web server
listening at port 443 e.g. apache. Also running on the same host is
the roundup-server. Apache (for example) is configured to take any
request to:

   https://www.mycompany.com/as2it/

and proxy it to http://localhost:9090/as2it/.

Your web setting in config.ini will be:

   web = https://www.mycompany.com/as2it/

as that is used in creating URL's in the web pages. However your
roundup-server is actually listening at:

   host: 127.0.0.1 (i.e. localhost)
   port: 9090

started with:

   roundup-server -n 127.0.0.1 -p 9090 as2it=/local/...

Note that there is a mismatch between the URL used to access the
Roundup tracker (https://www.mycompany.com/as2it/) and where that
tracker is actually running (which would have the URL
http://localhost:9090/as2it/).

The n= (name), p= (port) assign the location where roundup-server
actually is listening/running -- the rendezvous point with apache if
you will.

Usually people will run the external server on an internet accessible
host.  Then run roundup-server on a different internal host (not
exposed to the internet). In this case, you could just run
roundup-server without -n or -p and it would listen on every interface
of the internal host at port 8080. In this case, you would configure
apache to proxy to:

   http://internal_host:8080/as2it/

As I mentioned a while ago, you usually don't want to have Roundup
exposed to the internet. So you do that by binding to 127.0.0.1 or
running it on an internal host.

The d= option just makes roundup-server daemonize. With -d it will
automatically go into the background. This supports the standard
system V init scheme where programs are started by shell scripts.

If you are running roundup-server from systemd (using systemctl) or
other active supervisory software (e.g. runit) you usually don't want
it to daemonize, but that's a different discussion.

Note that roundup-server can use a config file, but most people just
use the command line options as you have done.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.