Thank you for the kind words!
Looks like pound really wasn't running when you checked. It should when
and after you receive this email.
Here is what Pound writes when trying to access a page with Firefox:
700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157
7FD71E405700 start do_request /build/pound-hSCqfU/pound-3.0/src/http.c:257
7FD71E405700 start do_http2 /build/pound-hSCqfU/pound-3.0/src/http2.c:296
7FD71E405700 start get_be /build/pound-hSCqfU/pound-3.0/src/http.c:143
7FD724C12700 start backend_2 /build/pound-hSCqfU/pound-3.0/src/backend.c:213
100.64.250.47 - - [Fri Aug 20 01:00:12 2021] "GET /index.php/login
HTTP/1.1" 200 8985
Surprisingly it didn't crash this time. Looks like the crashes where
independent from this and caused due to restarting it to fast. However,
even though Pound says everything goes as it should it doesn't: Firefox
reports a Network Protocol Error (see attached screenshots). Lynx (a
command line webbrowser), however, is able to access the service without
problems. Putting this together with the error curl gives I have an idea
what the issue could be: I think, since Pound is writing about HTTP1.1
and curl is writing about HTTP2 the HTTP versions might be somehow mixed
up or wrongly identified. I don't know how to check and/or fix this,
however.
Emanuel Loos
Am 20.08.21 um 00:01 schrieb Todd Fleisher via pound:
FWIW - right now I can connect to the public IPv4 address for
nc.emanuel-loos.eu <http://nc.emanuel-loos.eu> (185.128.244.57), only
the onion service @
http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion/index.php/login> is
responding. The public IPv4 address refuses connections.
Assuming the onion service points to the same apache2 backend and it
actually works beyond just loading the login page, this would seem to
point to an issue with your pound instance - maybe it is no longer
running due to a crash or you stopped it deliberately. Once you verify
it is running, you could also try to attach an strace to pound's PID
to see what is happening when you make a request to it and/or when it
is hammering your CPU like you mentioned below.
-T
P.S. Kudos to you for being aware of the power of self-hosting and
trying to learn more about it. It feels like an overlooked concept
with younger generations so it’s refreshing to see sentiments like yours
On Aug 19, 2021, at 13:34, Emanuel Loos via pound <[email protected]
<mailto:[email protected]>> wrote:
Am 19.08.21 um 21:39 schrieb Emanuel Loos via pound:
If it helps: The backend is an apache2 web server with a lot of PHP
(Nextcloud) and also available on this Tor Onion Service:
http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion
<http://jlw3fkl2xecpqarvz3qavyl7d7m43j5swxjskofhtdgb6f2cfp2cccid.onion>
Thanks in advance!
Emanuel Loos
Am 19.08.21 um 21:02 schrieb Emanuel Loos via pound:
-----Original Message-----
From: pound <[email protected]> On Behalf Of Emanuel Loos via
pound
Sent: Thursday, August 19, 2021 10:34 AM
To: [email protected]
Cc: Emanuel Loos <[email protected]>
Subject: Re: [pound] PR_END_OF_FILE_ERROR in Firefox and
ERR_CONNECTION refused in Chromium but lynx works
Hello the third time,
just reporting that for some reason Pound just started using the
full CPU power on one core:
PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+
BEFEHL
3590 root 20 0 1274244 16664 3144 R 99,3 0,1
37:35.29 pound
it is not a problem for me right now as it is a small private
server doing not much else (except sending this email) right now
but I don't thing that is how it should be. Anyway I think I'll
still keep Pound running (or maybe restart it) for now so if
anyone wants to help me with my problem Pound is online and the
problem can investigated easier.
Thanks in advance!
Emanuel Loos
Am 19.08.21 um 17:00 schrieb Emanuel Loos via pound:
Hello again,
just wanted to add that with curl this happens:
emanuel@devuan-emanuel:~$ curl
https://nc.emanuel-loos.eu/index.php/login
curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR
(err
1)
I left Pound running on my server so as long as there is no crash
(like when trying to connect using Firefox or Chromium but not
lynx or
curl) it should stay online. You are welcome to test it yourself
if it
helps.
Anyone got an idea what the problem could be or how to debug it
further?
Thanks in advance!
Emanuel Loos
--
pound mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
