Re: tracker does not want to send mail

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.)

Initial startup using roundup-server as2it=/local/data/roundup/as2it gives:
Roundup server started on localhost:8080

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...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> GET /as2it HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: BaseHTTP/0.6 Python/3.10.4
< Date: Tue, 20 Sep 2022 12:52:47 GMT
< Location: http://localhost:8080/as2it/
* no chunk, no close, no size. Assume close to signal end
<
[/curl]

Which at least looks promising

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)
Traceback (most recent call last):
  File "/usr/lib/python3.10/socketserver.py", line 616, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib/python3.10/socketserver.py", line 360, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python3.10/socketserver.py", line 747, in __init__
    self.handle()
  File "/usr/lib/python3.10/http/server.py", line 425, in handle
    self.handle_one_request()
  File "/usr/lib/python3.10/http/server.py", line 393, in handle_one_request
    self.raw_requestline = self.rfile.readline(65537)
  File "/usr/lib/python3.10/socket.py", line 705, in readinto
    return self._sock.recv_into(b)
ConnectionResetError: [Errno 104] Connection reset by peer
[/code]

I don't know if that traceback is anything to be concerned about or not.

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]

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 -
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 -
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]

... And that's where we sit at the moment...

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users