Custom Query (2297 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 2297)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#1352 invalid error when starting 118masterman@…
Description

I deleted the files relating towards it but it still is giving the error

nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/mail.mastercraft.cc/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/mail.mastercraft.cc/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx: configuration file /etc/nginx/nginx.conf test failed

#1636 invalid CPU 100% with njs on simple base64 decode (2.3.1) 131@…
Description

I'm using a simple js_set to base64 decode (via String.bytesFrom) as proxy_pass destination, and CPU goes too high (100%) under heavy load.

I can reproduce this using ab -c 200 -n 10000

ab -c 200 -n 10000 "http://127.0.0.1/ping" => 0% CPU, all good

ab -c 200 -n 10000 "http://127.0.0.1/proxy/string => 35% CPU, all good

ab -c 200 -n 10000 "http://127.0.0.1/proxy/js_set => 100%CPU, no good.

I'm guessing the resolver also use CPU cycle, but i'm unhappy with current performances, is there something i can tweak ?

(switching to worker_processes auto helped a bit, but 'im still looking for something faster)

Thank you for your kind help

js_include "./conf.d/njs/x_proxypass.js";
js_set $x_proxypass x_proxypass;


server {
    listen       80 default_server;

    gzip off;

    location /ping {
      return 200 "pong";
    }

    location /proxy/string {
      aio threads;
      proxy_buffering off;
      proxy_pass 'https://131.github.io/ping';

    }

    location /proxy/js_set {
      aio threads;
      proxy_buffering off;
      proxy_pass $x_proxypass;
    }
   access_log  /dev/null;
}



function x_proxypass(r) {
  var src = 'aHR0cHM6Ly8xMzEuZ2l0aHViLmlvL3Bpbmc=';
  return String.bytesFrom(src, 'base64');
}
#1996 wontfix Why is there no Restart=on-failure in systemd unit 131@…
Description

So, nginx failed to start as an upstream DNS provider was not available. That's fine, it might append on boot.

Is it possible, instead of entering failed state, that nginx try to restart whenever it crash using the "Restart=always" or "Restart=on-failure" systemd directive ?

Is there a reason for this directive NOT to be configured in nginx default packages ?

Thank you for your response Francois

1 2 3 4 5 6 7 8 9 10 11 12
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.