Re: Newly installed roundup 2.2.0. roundup-demo timeout errors

I should add the browser error:

"
The connection was reset

The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
"

I have verified that I can access other web sites with no problems from this browser within this VM.
________________________________
From: [email protected] <[email protected]> on behalf of John P. Rouillard <[email protected]>
Sent: Monday, August 8, 2022 6:59 PM
To: Ed Trumbull <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [Roundup-users] Newly installed roundup 2.2.0. roundup-demo timeout errors

Hi Ed:

In message <SJ0PR12MB56625AB750350945F9EA417984639@SJ0PR12MB5662.namprd12.prod.
outlook.com>,
Ed Trumbull writes:
>I have a new VM running ubuntu 22.04 MATE.
>Python 3.10.4
>
>I obtained roundup via pip3 install
>
>When I launch the demo, I see
>Demo Tracker Home: ./demo
[...]
>
>All looks kosher.

Agreed. What template did you choose?

>When I launch the browser from the same VM

Are you on the console of the vm, or running a local browser over X to
a remote display?

>and attempt to reach
>localhost:8917, the browser hangs and eventually times out.

How comfortable are you using the browser development tools to trace
the network traffic? Alternatively do you know how to use tcpdump?

>While nothing is happening from the browser, I see the following line
>on the console running roundup:
>127.0.0.1 - - [08/Aug/2022 21:10:14] Request timed out: TimeoutError('timed out')
>
>This error repeats every minute, updating the timestamp as it goes.

Hmm, this is strange. Sorry you are running into it.

Do the errors repeat even after the browser gives up? One minute IIRC
is the right timeout.

It sounds like a connection is being made, but the actual GET request
is either not sent or something is hanging in Roundup and it's not
logging the failure, which is strange.

Let's try running roundup-server directly. Kill roundup-demo. In
the same directory where you ran roundup-demo run:

  roundup-server -t debug -p 8917 demo=demo

and see if that exhibits the same issue. '-t debug' changes how it
handles connections, it doesn't add logging.

What happens when you browse to the server?

>Any idea what's not working right?

None. On my Ubuntu 22.04.1 system I just ran 'pip3 install roundup'.
Then ran roundup-demo choosing the classic tracker.

The http://localhost:8917/demo/ worked without an issue.

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