Custom Query (2296 matches)
Results (40 - 42 of 2296)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2561 | fixed | Ubuntu 23.10: no stable or mainline packages on nginx.org repo | ||
Description |
Hello there! Ubuntu 23.10 with code name mantic was released 12.10.2023. There is only a stable version 1.24.0 in the basic OS repos: # apt list nginx* Listing... Done nginx-common/mantic 1.24.0-1ubuntu1 all nginx-confgen/mantic 2.1-1 amd64 nginx-core/mantic 1.24.0-1ubuntu1 all nginx-dev/mantic 1.24.0-1ubuntu1 all nginx-doc/mantic 1.24.0-1ubuntu1 all nginx-extras/mantic 1.24.0-1ubuntu1 amd64 nginx-full/mantic 1.24.0-1ubuntu1 all nginx-light/mantic 1.24.0-1ubuntu1 all nginx/mantic 1.24.0-1ubuntu1 amd64 Im trying to use as usual nginx packages repo for Linux nginx.org according to https://nginx.org/en/linux_packages.html#Ubuntu When trying to install a package: # apt update ... Ign:4 http://nginx.org/packages/ubuntu mantic InRelease Err:5 http://nginx.org/packages/ubuntu mantic Release ... Reading package lists... Done E: The repository 'http://nginx.org/packages/ubuntu mantic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. Then I used direct links to find out if the package was in the repo:
There are no packages with mantiс code in the *.deb filenames on repo. It is necessary to build stable and mainline versions of packages and place them in the nginx.org repo. Thank you) PS: a few technical details: # uname -a Linux vmx117 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux # dpkg --list 'linux-image*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-============-============-================================= un linux-image <none> <none> (no description available) ii linux-image-6.5.0-10-generic 6.5.0-10.10 amd64 Signed kernel image generic ii linux-image-6.5.0-9-generic 6.5.0-9.9 amd64 Signed kernel image generic ii linux-image-generic 6.5.0.10.12 amd64 Generic Linux kernel image un linux-image-unsigned-6.5.0-10-generic <none> <none> (no description available) un linux-image-unsigned-6.5.0-9-generic <none> <none> (no description available) # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic # cat /etc/os-release PRETTY_NAME="Ubuntu 23.10" NAME="Ubuntu" VERSION_ID="23.10" VERSION="23.10 (Mantic Minotaur)" VERSION_CODENAME=mantic ID=ubuntu |
|||
#2559 | invalid | K8S ingress rule fails to match Exact / | ||
Description |
Using: │app.kubernetes.io/name: rke2-ingress-nginx │app.kubernetes.io/version: 1.6.4 │helm.sh/chart: rke2-ingress-nginx-4.5.201 Having an ingress with: │ rules: │ - http: │ paths: │ - backend: │ service: │ name: powerflex-status-ui │ port: │ number: 80 │ path: / │ pathType: Exact When calling:
HTTP/2 404 It worked with an older version. We have a workaround, adding $ to the expression. │ rules: │ - http: │ paths: │ - backend: │ service: │ name: powerflex-status-ui │ port: │ number: 80 │ path: /$ │ pathType: Exact That one seems identical but it works - getting http 200 |
|||
#2558 | invalid | Memory Leak (maybe WebSocket) | ||
Description |
We use a little WebSocket. And sometimes we execute kill -USR1 $(cat /var/run/nginx-81.pid) to reopen logfiles and nginx creates many workers in shutdown mode. But it workers works for a long time and the next time we again reopen our logfiles (1200 file) and than nginx again creates shutdown worker by that some times later the server starts to consume a lot of RAM oТ the chart you can see the drops - it is OOM Killer. How to debug I this problem with memory? |