Hi,
I've been experiencing issues fetching the sources of nginx 1.27.0 (deb) from
the nginx.org mainline package repository. We have a job that collect sources
for clearing and the latest nginx runs have been blocked with the following
error:
E: Failed to fetch
http://nginx.org/packages/mainl
Hi all,
About 2 months ago the CPU usage on 1 of our servers started going crazy. All
of a sudden, Nginx itself started using about 6x the CPU power to serve
requests with no increase in traffic at all. It's a dramatic difference and
it's directly attributed to Nginx, not PHP, Mariadb, or any
I wouldn't trust a build if the hash doesn't match. I'd use the version
before it which does match. Was there an issue with the earlier version?
On Mon, Aug 12, 2024, 3:21 AM FERRON, BENJAMIN via nginx
wrote:
> Hi,
>
>
>
> I’ve been experiencing issues fetching the sources of nginx 1.27.0 (deb
Hi Benjamin,
Are you by any chance fetching the 1.27.0-1/1.26.1-1 versions of the
packages and their corresponding sources?
Indeed, we had a bit of a mishap when publishing them leading to the
errors you're seeing:
ubuntu22:~/src$ apt-get source nginx=1.27.0-1~jammy
Reading package lists...
Hi Konstantin,
That was it :)
The internal build process was version locked on 1.27.0~1bookworm, with
1.27.0~2bookworm the issue is solved.
Thanks for you help!
Kind regards,
Benjamin
De : Konstantin Pavlov
Envoyé : lundi 12 août 2024 19:25
À : nginx@nginx.org
Cc : FERRON, BENJAMIN (IT IPS SE
If your Nginx is compiled with debug symbols you may see some useful info
`perf top`
On Mon, Aug 12, 2024, 6:24 PM Brad Patton wrote:
> Hi all,
>
> About 2 months ago the CPU usage on 1 of our servers started going crazy.
> All of a sudden, Nginx itself started using about 6x the CPU power to se
