-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Death of the wwsympa process bug #876
Comments
Hi @bruncsak ,
|
I applied the patch, we will see is the problem still there, or not any more, thanks. Concerning wwsympa_url: I am using non-standard configuration relative to the rpm package from the EPEL repo, due to the double components of the wwsympa_url local path. I use mod_fcgid instead of mod_proxy_fcgi. For additional detail please visit: |
There is one more information. I just realized that the configuration is incorrect on our side. The reverse proxy actually unloads the SSL tunnel, so the correct value for wwsympa_url should have been: |
Thanks!
If possible, please show us the access log of httpd, including path and host name of accessed URI, from when the browser accessed help page to when wwsympa crashes.
With such situation you may have to add the "real" URL to Sympa configuration.
In this figure, user recognizes Sympa service as
|
Unfortunately the combined apache log is not enabled (that is the default on CentOS). What I have in the access log is the following: |
I understand. Then, are you sure that the reverse proxy passes |
Our sympa installation in general works correctly with the outside URL, no big issue just some small ones like this. Concerning your recommended configuration:
So I avoid using the |
Then, could you please check if the reverse proxy always passes |
That is really tricky to answer. At least all access I see has |
Anyways could you please add a line " |
In fact, I have two robots, with different wwsympa_url parameters. I will put a third version of |
OK. Please let us know the result. BTW, If you run two or more domains, it would be better to choose one as the default and to include its mail domain and URL in
|
Could web1 equal to web2, or is it invalidating your proposed configuration? |
mail1 (web1) and mail2 (web2) are different each other. sympa.conf and one of robot settings share mail1 (web1). |
@bruncsak , does the bug reproduce? If it does, please show us following things:
Thanks. |
Yes, I am able to reproduce the problem. I already set-up a test installation, but its configuration is still complex much out of a vanilla baseline. For example, it still has a reverse-proxy in front (I started the work out from the production).
|
Could you please show us also these things?
|
On each program output, configuration file, log file I made the following transformations:
Hoping that it is helpful. |
Sorry for repeating the same requests. Could you please show us log of HTTP server and Sympa, from when you sent the initial request to when wwsympa.fcgi dies. Additionally, please describe how you reproduced step-by-step (e.g. Launch browser, open the address xxxx://...., click xxxx, ...). |
I am sorry. I forgot about the log of Sympa, here it comes. And sorry, I thought it is better to reproduce with the program curl. One simple HTTP connection with the program curl, and the perl process dies. One access_log entry only. So here it is the same with an internet explorer browser:
|
No need for reverse proxy in front, I managed to reproduce the bug with direct http connection. |
|
1.The problem disappeared with this patch. Thanks! |
@bruncsak , thanks for patience. At last we can fix the bug. BTW I haven't answered one question:
No. Sympa cannot determine protocol used between client and server, and relative references including "network-path reference" (URL omitting scheme) cannot be used in its configuration. |
This prevents confusion seen at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929157#15 sympa-community#876 (comment) Even better to have a format that checks whether it is a valid URL. E.g. by feeding it to the URI module and verify that all vital parts are present.
Version
sympa-6.2.52-2.el7.x86_64
Installation method
via yum on CentOS 7 from the epel repository
I got regularly the following error message:
I have in the apache error log the following in addition too:
The text was updated successfully, but these errors were encountered: