[users@httpd] Apache httpd 2.4.53 was installed successfully on CentOS 7.9 using rpm

[河本和彦]

Hi,

Platform:

 CentOS Linux release 7.9.2009 (Core)
 kernel version: kernel-3.10.0-1160.59.1.el7.x86_64

I have installed the newly released Apache httpd 2.4.53 on
the above  platform through rpmbuilding successfully without
problems.

Thank you all contributors to this project for this
excellent work.

Thank you.

Yours truly,
Kazuhiko Kohmoto

[users@httpd] "Size of Request header field exceeds limit" despite changed limits - how to debugg further?

[Alexander Reichle-Schmehl]

Hi!

* Alexander Reichle-Schmehl  [220315 14:34]:

> We initially tried to fix that by setting the LimitRequestFieldSize
> configuration setting and asking the users to clear their cookies and
> browser caches.  That seems to have solved the problem for some, but not
> for all of them.  So we increased the value several times, and have now
> reached LimitRequestFieldSize 33554432.  Looking at the documentation
> and the default value, that seems to be gigantic for me.

Okay, apparently I should have read the documentation more carefully.
We tried to set this in the global server configuration, and misread
this warning in the documentation [1]:

=
When name-based virtual hosting is used, the value for this directive
is taken from the default (first-listed) virtual host best matching the
current IP address and port combination.
=

We do use virtual hosts, hence the global setting was ignored.  The
"users" we seemed to have fixed by this, had probaly just some broken
cookies, and got access by cleaning them.

Moving the LimitRequestFieldSize setting to the virtual host solved the
problem.



Best regards,
  Alexander



Links:
  1: https://httpd.apache.org/docs/2.4/en/mod/core.html#limitrequestfieldsize


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] Re: Are this option

[Marc Serra]

I'm sorry to insist ... if this list is not the right place to ask that
question, could anyone tell me where to do it?

Thank's

Missatge de Marc Serra  del dia dc., 9 de març 2022 a les
18:01:

> Hi, I want to configure an apache server to support a high load site. Are
> these settings correct?
>
> /etc/apache2/mods-enabled/mpm_event.conf
>
> 
> StartServers 2
> MinSpareThreads  75
> MaxSpareThreads  250
> ThreadLimit  64
> ThreadsPerChild  25
> MaxRequestWorkers 1500
> MaxConnectionsPerChild   0
> ServerLimit 75
> 
>
> I used a combination of
> https://httpd.apache.org/docs/2.4/en/mod/mpm_common.html and
> https://support.plesk.com/hc/en-us/articles/214529205-Apache-keeps-going-down-on-a-Plesk-server-server-reached-MaxRequestWorkers-setting
> ...
>
> MaxRequestWorkers = (Total RAM - Memory used for Linux, DB, etc.) /
> average Apache process size
> =>
> 1500 = (64000 - 6) / 40
>
> The default ServerLimit value is 16. To increase it, you must also raise
> MaxRequestWorkers using the following formula: ServerLimit value x 25 =
> MaxRequestWorkers value. For example, if ServerLimit is set to 20, then
> MaxRequestWorkers will be 20 x 25 = 500.
> =>
> 75 x 25 = 1500
>
>
>
> The hardware includes 64GB of memory, AMD Ryzen 7 PRO 3700 8-Core
> Processor and NVME disks.
>
> I'm using Apache 2.4.41 with event MPM on ubuntu 20.04 ...
>
> Server version: Apache/2.4.41 (Ubuntu)
> Server built:   2022-01-05T14:49:56
> Server's Module Magic Number: 20120211:88
> Server loaded:  APR 1.6.5, APR-UTIL 1.6.1
> Compiled using: APR 1.6.5, APR-UTIL 1.6.1
> Architecture:   64-bit
> Server MPM: event
>   threaded: yes (fixed thread count)
> forked: yes (variable process count)
> Server compiled with
>  -D APR_HAS_SENDFILE
>  -D APR_HAS_MMAP
>  -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
>  -D APR_USE_SYSVSEM_SERIALIZE
>  -D APR_USE_PTHREAD_SERIALIZE
>  -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
>  -D APR_HAS_OTHER_CHILD
>  -D AP_HAVE_RELIABLE_PIPED_LOGS
>  -D DYNAMIC_MODULE_LIMIT=256
>  -D HTTPD_ROOT="/etc/apache2"
>  -D SUEXEC_BIN="/usr/lib/apache2/suexec"
>  -D DEFAULT_PIDLOG="/var/run/apache2.pid"
>  -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
>  -D DEFAULT_ERRORLOG="logs/error_log"
>  -D AP_TYPES_CONFIG_FILE="mime.types"
>  -D SERVER_CONFIG_FILE="apache2.conf"
>
> And this loaded Modules...
>  core_module (static)
>  so_module (static)
>  watchdog_module (static)
>  http_module (static)
>  log_config_module (static)
>  logio_module (static)
>  version_module (static)
>  unixd_module (static)
>  access_compat_module (shared)
>  aclr_module (shared)
>  actions_module (shared)
>  alias_module (shared)
>  auth_basic_module (shared)
>  authn_core_module (shared)
>  authn_file_module (shared)
>  authz_core_module (shared)
>  authz_host_module (shared)
>  authz_user_module (shared)
>  autoindex_module (shared)
>  cgid_module (shared)
>  deflate_module (shared)
>  dir_module (shared)
>  env_module (shared)
>  fcgid_module (shared)
>  filter_module (shared)
>  headers_module (shared)
>  include_module (shared)
>  mime_module (shared)
>  mpm_event_module (shared)
>  negotiation_module (shared)
>  proxy_module (shared)
>  proxy_fcgi_module (shared)
>  proxy_http_module (shared)
>  proxy_wstunnel_module (shared)
>  remoteip_module (shared)
>  reqtimeout_module (shared)
>  rewrite_module (shared)
>  setenvif_module (shared)
>  socache_shmcb_module (shared)
>  ssl_module (shared)
>  status_module (shared)
>  suexec_module (shared)
>  unique_id_module (shared)
>  userdir_module (shared)
>
>
> Thank's for your time.
>
>

-- 
Marc Serra
Organització i Sistemes

-- 


   
  
  
  
 Manxa 1876, S.L.
Ctra. Les 
Tries, 85.17800 Olot (Girona)
*Tel. 972 27 45 30 www.manxa.com 
* 
  *Manxa 
Industrial *
 
  *Manxa Ferros *
   *Manxa Ferreteria i Parament de la Llar 
*
  

  



-- 


El contingut d’aquest correu electrònic i els seus annexos és 
estrictament confidencial. En el cas que no siguis el destinatari i hagis 
rebut aquest missatge per error, preguem que ho comuniquis al remitent i 
procedeixis a la seva eliminació, sense difondre, emmagatzemar o copiar el 
seu contingut. Imprimeix aquest correu només si és necessari.

El contenido 
de este correo electrónico y sus anexos es estrictamente confidencial. En 
el caso de que no seas el destinatario y hayas recibido este mensaje por 
error, rogamos lo comuniques al remitente y procedas a su eliminación, sin 
difundir, almacenar o copiar su contenido. Imprimir este correo solo si es 
necesario.

The content of this email and its attachments is strictly 
confidential. If you are not the 

[users@httpd] Request is sitting in Listen queue and causing the delay

[Shilpa Choudhary]

Hi folks,

Running httpd.2.4.43 version with mpm_event module.  There is an auth module 
loaded in HTTPD process which sends internal request to forward to 
authentication server .
Internal requests are being routed to localhost: . Module which is 
routing the request expects response from auth server within 5 sec, if the 
response is not coming within 5 seconds, auth module closes internal connection.

When stress test is being run, some of the internal request are taking more 
then 5sec to get processed. There are enough number of worker threads.
Checked the TCP dump which shows that module has sent request to 
localhost:  and TCP ACK appears in TCPDUMP after receiving the 
request.

event Listener thread is picking up the request  after 4+ sec and httpd server 
is able to process the request less the one sec but by the time http server has 
responded with response, internal module which is sending the request already 
has closed the connection due to timeout.

Listener thread of each process calls apr_pollset_poll api to get list of 
socket which are ready to be processed. apr_pollset_poll API has returned fd 
for httpd port after 4+ sec.
apr_pollset_poll function is provided by APR which is wrapper over epoll APIs.  
There is no issue in increasing the timeout value, but looking for the proper 
reason for this delay.

Why socket fd correspond to httpd port not has not been returned by 
apr_pollset_poll API as soon as internal request has been sent ? How to debug 
this delay issue ?  Is there any setting, I have to check at OS level/HTTPD 
server level.


Thanks,
Shilpa