Are you running a build of pound with debug symbols? If so, fire up gdb and attach it to the pound process and see where it is processing. That should give you a good place to start your diagnosis.
If you're not a programmer, then try this: > gdb /path/to/pound 3590 Using PID 3590 from your example below. "To stop your program while it is running, type "(ctrl) + c" (hold down the ctrl key and press c)." https://web.eecs.umich.edu/~sugih/pointers/gdbQS.html Now you should have an interruption in the pound exe, you can list and get a call stack. If you have the path/to/exe and the source, then you should be able to get actual C code listings of where the break occurred. -- jake -----Original Message----- From: pound <pound-boun...@apsis.ch> On Behalf Of Emanuel Loos via pound Sent: Thursday, August 19, 2021 10:34 AM To: pound@apsis.ch Cc: Emanuel Loos <m...@mailing-lists.emanuel-loos.eu> 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 > > Am 17.08.21 um 19:15 schrieb Emanuel Loos via pound: >> I am trying to use Pound as a reverse proxy on my server to serve >> multiple online services available on server intern local IP >> addresses through http on their different domains through https using >> only one public IP address. >> >> My configuration: >> >> Global: >> User: "root" >> Group: "root" >> Backends: >> - &nextcloud >> Address: 10.10.2.2 >> Port: 80 >> >> HTTPListeners: >> >> HTTPSListeners: >> - Address: 185.128.244.57 >> Port: 443 >> Services: >> - HeadRequire: "Host: nc.emanuel-loos.eu" >> Backends: >> - *nextcloud >> Certificates: >> "/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.pem" >> Client: 60 >> Ciphers: >> - TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384 >> - TLS-DHE-RSA-WITH-3DES-EDE-CBC-SHA >> - TLS-DHE-RSA-WITH-AES-128-CBC-SHA >> - TLS-RSA-WITH-CAMELLIA-128-CBC-SHA >> - TLS-RSA-WITH-AES-128-CCM >> - TLS-RSA-WITH-AES-256-GCM-SHA384 >> - TLS-RSA-WITH-RC4-128-MD5 >> - TLS-RSA-WITH-3DES-EDE-CBC-SHA >> >> >> However when trying to connect Firefox throws a PR_END_OF_FILE_ERROR >> and Pound crashes with a storage access error. However when I try to >> connect using lynx it works perfectly. >> >> >> root@Server:~# pound -d 1 >> start get_others /build/pound-hSCqfU/pound-3.0/src/config.c:564 >> start get_global /build/pound-hSCqfU/pound-3.0/src/config.c:74 >> start get_backends /build/pound-hSCqfU/pound-3.0/src/config.c:123 >> start get_https /build/pound-hSCqfU/pound-3.0/src/config.c:489 >> start get_services /build/pound-hSCqfU/pound-3.0/src/config.c:209 >> start get_certificates /build/pound-hSCqfU/pound-3.0/src/config.c:451 >> start >> get_one(/etc/letsencrypt/live/emanuel-loos.eu/fullchain-and-privkey.p >> em) >> /build/pound-hSCqfU/pound-3.0/src/config.c:376 >> start get_ciphers /build/pound-hSCqfU/pound-3.0/src/config.c:334 >> Starting resurrector thread >> /build/pound-hSCqfU/pound-3.0/src/util.c:80 >> 7F445B27F700 start service >> /build/pound-hSCqfU/pound-3.0/src/http.c:45 >> 7F445AA7E700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F445A27D700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4459A7C700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4458279700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4458A7A700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4457A78700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4457277700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F445927B700 thr_http start >> /build/pound-hSCqfU/pound-3.0/src/http.c:535 >> 7F4457277700 start sni /build/pound-hSCqfU/pound-3.0/src/util.c:157 >> Speicherzugriffsfehler >> >> >> root@Server:~# apt info pound >> Package: pound >> Version: 3.0-2 >> Priority: optional >> Section: net >> Maintainer: Carsten Leonhardt <l...@debian.org> >> Installed-Size: 156 kB >> Pre-Depends: init-system-helpers (>= 1.54~) >> Depends: lsb-base, sysuser-helper (<< 1.4), libc6 (>= 2.25), >> libmbedcrypto3 (>= 2.13), libmbedtls12 (>= 2.13), libmbedx509-0 (>= >> 2.0), libnanomsg5 (>= 1.1.5), libpcre3, libyaml-0-2 >> Homepage: https://www.apsis.ch/pound.html >> Tag: interface::daemon, network::load-balancing, network::server, >> protocol::http, protocol::ssl, role::program, use::proxying, >> web::server >> Download-Size: 62,6 kB >> APT-Manual-Installed: yes >> APT-Sources: http://deb.devuan.org/merged chimaera/main amd64 >> Packages >> >> >> Thank you very much in advance! >> >> Emanuel Loos >> >> > -- pound mailing list pound@apsis.ch https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch -- pound mailing list pound@apsis.ch https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
