Re: tracker does not want to send mail
"John P. Rouillard" <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Ed:
Thanks for the details.
In message
<PH7PR12MB5656F1FEB4EFE2E27C6C632E844C9@PH7PR12MB5656.namprd12.prod.
outlook.com>,
Ed Trumbull writes:
>And here we go again.
>
>My company has chosen to use Linux Mint 21 for our new installs, so
>that's where I'm starting with this install.
>
>Mint has been patched up to current levels.
>Roundup 2.2.0 was installed via pip3. Location is
> /usr/local/lib/python3.10/roundup
>Tracker was installed by user "roundup", and is installed in
> /local/data/roundup/as2it. Roundup-admin install was used for the
>installation:
>
>[code]
>roundup@admin-00:/local/data/roundup/as2it$ roundup-admin install
>Enter tracker home: /local/data/roundup/as2it/
>Templates:: devel, classic, jinja2, responsive, minimal
>Select template [classic]:
>Back ends:: anydbm, sqlite
>Select backend [anydbm]:
>[/code]
>
>(There's a discrepancy between the documentation on the web and the
>output of roundup-admin install:
>The web says I should modify the config file and set "at a minimum"
> “main :: admin_email”, “mail :: host”,
>“tracker :: web” and “mail :: domain”. The install command only tells
>me to set the last three -- tracker::web, mail::host, and mail::domain.
>Since there's a default value for admin_email, I left it alone.)
That should work. I'll have to check on the admin_email setting.
>Initial startup using roundup-server as2it=/local/data/roundup/as2it gives:
>Roundup server started on localhost:8080
Correct this maps the tracker's /as2it/ URL path to the tracker
directory.
>I don't have a browser running on the local host, so I used curl to
>see if things are running:
>
>curl from the local host gave:
>[code]
>edt@admin-00:~$ curl -v localhost:8080/as2it
>* Trying 127.0.0.1:8080...
> [...]
>< HTTP/1.1 301 Moved Permanently [...]
>< Location: http://localhost:8080/as2it/
> [...]
>Which at least looks promising
Agreed. The URL was missing a trailing /. So it generated a redirect
to add one.
>I then ran nmap from the localhost. When I did so, I saw an error
>in the server's stdout:
>
>[code]
>Exception occurred during processing of request from ('127.0.0.1', 38016)
>[...]
>ConnectionResetError: [Errno 104] Connection reset by peer
>[/code]
>
>I don't know if that traceback is anything to be concerned about or not.
It is not a problem. This is caused by the client (nmap) closing the
connection before Roundup has processed and finished responding. There
is an open ticket to fix this cosmetic (but scary) traceback with
newer Pythons.
>I restarted the tracker with the following command:
>roundup-server -p 8917 -n 0.0.0.0 as2it=/local/data/roundup/as2it
>
>I can connect to the tracker!
>But, if I try to log in as the admin user, I get a 404 error.
>[code]
>Error code: 404
>
>Message: /local/data/roundup/as2it/.
>
>Error code explanation: 404 - Nothing matches the given URI.
>[/code]
What is your web setting? It should be something like:
http://real_host_name:8080/as2it/
>Stdout from the server shows:
>Server side shows:
>[code]
>Roundup server started on 0.0.0.0:8917
>
>
>192.168.170.6 - - [20/Sep/2022 13:36:51] "GET /as2it/index HTTP/1.1" 200 -
This is correct. It is using /as2it/ as you typed into the browser.
>192.168.170.6 - - [20/Sep/2022 09:37:12] code 404, message /local/data/roundup/as2it/
>192.168.170.6 - - [20/Sep/2022 09:37:12] "POST /local/data/roundup/as2it/ HTTP/1.1" 404 -
This is wrong. /local/data/roundup/as2it/ is not a URL path, it's the
location on disk. The only way I know this can happen is for the web
setting to be something like:
http://localhost:8080/local/data/roundup/as2it/
>192.168.170.6 - - [20/Sep/2022 09:37:51] Request timed out: TimeoutError('timed out')
>192.168.170.6 - - [20/Sep/2022 13:37:51] Request timed out: TimeoutError('timed out')
>192.168.170.6 - - [20/Sep/2022 09:38:12] Request timed out: TimeoutError('timed out')
>[/code]
Not sure what to make of these timeouts. Also these seems to be some
sort of timezone issue as you have 9:37:51 and 13:37:51 which is the
difference expected between UTC and EST5EDT. But it has nothing to do
with the errors you are seeing.
Hope this helps.
--
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users