From faskiri.devel at gmail.com Tue Jan 1 18:27:30 2013 From: faskiri.devel at gmail.com (Fasih) Date: Tue, 1 Jan 2013 23:57:30 +0530 Subject: Nginx mutli-threaded plugin Message-ID: Hi guys I need to write a plugin which does some CPU intensive work. I want to be able to create a thread which does some work and once done post an event into nginx thread via ngx_add_timer. I tried compiling my plugin with NGX_THREADS=pthread but that doesnt configure saying that the threading support is broken. I can obviously switch to a single threaded mode but that would be significantly difficult for me and would prefer to use only as the very last resort. Can you please advice how to go about doing this? I am considering pulling out the usage of 'ngx_event_timer_mutex' outside #if NGX_THREADS. Frankly I am surprised how no other plugin had this kind of requirement, the "broken support" commit has been there since quite some time now. One final question, if I do the CPU intensive work in the nginx thread and I have number of workers, how would the system behave? Will accept_mutex on/off change the behavior? Regards, +Fasih -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdounin at mdounin.ru Tue Jan 1 21:19:22 2013 From: mdounin at mdounin.ru (Maxim Dounin) Date: Wed, 2 Jan 2013 01:19:22 +0400 Subject: Nginx mutli-threaded plugin In-Reply-To: References: Message-ID: <20130101211922.GY40452@mdounin.ru> Hello! On Tue, Jan 01, 2013 at 11:57:30PM +0530, Fasih wrote: > Hi guys > > I need to write a plugin which does some CPU intensive work. I want to be > able to create a thread which does some work and once done post an event > into nginx thread via ngx_add_timer. I tried compiling my plugin with > NGX_THREADS=pthread but that doesnt configure saying that the threading > support is broken. I can obviously switch to a single threaded mode but > that would be significantly difficult for me and would prefer to use only > as the very last resort. > > Can you please advice how to go about doing this? I am considering pulling > out the usage of 'ngx_event_timer_mutex' outside #if NGX_THREADS. Frankly I > am surprised how no other plugin had this kind of requirement, the "broken > support" commit has been there since quite some time now. Threading support as currently present was an experiment, and it's broken for a long time (some very limited part of it is still used on win32, but it's different story). I wouldn't expect you'll be able to work with threads without problems. > One final question, if I do the CPU intensive work in the nginx thread and > I have number of workers, how would the system behave? Will > accept_mutex on/off change the behavior? Accept mutex only ensures no two processes try to accept new connections at the same time, and it doesn't care how do you handle requests. Obviously enough it will change the behaviour, much like in any other case. -- Maxim Dounin http://nginx.com/support.html From faskiri.devel at gmail.com Wed Jan 2 05:07:48 2013 From: faskiri.devel at gmail.com (Fasih) Date: Wed, 2 Jan 2013 10:37:48 +0530 Subject: Nginx mutli-threaded plugin In-Reply-To: <20130101211922.GY40452@mdounin.ru> References: <20130101211922.GY40452@mdounin.ru> Message-ID: Thank you Maxim. Will try to see if I can get to the single threaded model. Basically when I was talking about accept_mutex, what I meant was, if the worker thread is busy with my cpu-intensive work, I would obviously want the other workers to take over. IIUC, if I have the accept mutex I am the one who will take the requests, is it possible that my worker plugin is caught up doing the work *and* has not released the mutex? In other words, is it possible that my CPU intensive operation prevents other workers who are free from taking requests with any configuration option enabled/disabled. On Wed, Jan 2, 2013 at 2:49 AM, Maxim Dounin wrote: > Hello! > > On Tue, Jan 01, 2013 at 11:57:30PM +0530, Fasih wrote: > > > Hi guys > > > > I need to write a plugin which does some CPU intensive work. I want to be > > able to create a thread which does some work and once done post an event > > into nginx thread via ngx_add_timer. I tried compiling my plugin with > > NGX_THREADS=pthread but that doesnt configure saying that the threading > > support is broken. I can obviously switch to a single threaded mode but > > that would be significantly difficult for me and would prefer to use only > > as the very last resort. > > > > Can you please advice how to go about doing this? I am considering > pulling > > out the usage of 'ngx_event_timer_mutex' outside #if NGX_THREADS. > Frankly I > > am surprised how no other plugin had this kind of requirement, the > "broken > > support" commit has been there since quite some time now. > > Threading support as currently present was an experiment, and it's > broken for a long time (some very limited part of it is still used > on win32, but it's different story). I wouldn't expect you'll be > able to work with threads without problems. > > > One final question, if I do the CPU intensive work in the nginx thread > and > > I have number of workers, how would the system behave? Will > > accept_mutex on/off change the behavior? > > Accept mutex only ensures no two processes try to accept new > connections at the same time, and it doesn't care how do you > handle requests. Obviously enough it will change the behaviour, > much like in any other case. > > -- > Maxim Dounin > http://nginx.com/support.html > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sagar.sonawane at rediffmail.com Wed Jan 2 16:02:05 2013 From: sagar.sonawane at rediffmail.com (Sagar) Date: 2 Jan 2013 16:02:05 -0000 Subject: Book for module Development Message-ID: <20130102160205.19550.qmail@f4mail-235-163.rediffmail.com> Hi all, I am php developer having 6+ years of experience building websites,portals,applications etc. I need some guidance in developing 3rd party modules for nginx. But, i couldn't found any specific book for that. Please help me to walk on correct path, as i don't want to get messed/frustrated, by choosing wrong directions in early stage. Currently, i am having following article with me to start with: http://www.evanmiller.org/nginx-modules-guide-advanced.html Hoping for a favourable reply. Regards, Sagar Sonawane -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at gwynne.id.au Fri Jan 4 01:22:04 2013 From: david at gwynne.id.au (David Gwynne) Date: Fri, 4 Jan 2013 11:22:04 +1000 Subject: [PATCH] implement a $location variable In-Reply-To: References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> Message-ID: <20130104012204.GA26729@animata.net> here's a diff that provides $location for use in not regex location blocks. we're using it to provide easy to use mass hosting of drupals: xdlg at argon nginx$ cat drupal-controller.conf root /var/www/apps/drupal; try_files /index.php =404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param SCRIPT_NAME $location$fastcgi_script_name; fastcgi_intercept_errors on; fastcgi_pass localhost:9000; which is used in server blocks like this: server { listen 80; server_name www.example.com; location / { include drupal-controller.conf; } location /foo { include drupal-controller.conf; } location /bar { include drupal-controller.conf; } location /baz { include drupal-controller.conf; } } i cannot otherwise find a nice way to use the locations name as a parameter without specifying the value as a variable again within the location. --- src/http/ngx_http_variables.c.orig Tue Jul 3 03:41:52 2012 +++ src/http/ngx_http_variables.c Fri Jan 4 10:49:50 2013 @@ -65,6 +65,8 @@ static ngx_int_t ngx_http_variable_request_filename(ng ngx_http_variable_value_t *v, uintptr_t data); static ngx_int_t ngx_http_variable_server_name(ngx_http_request_t *r, ngx_http_variable_value_t *v, uintptr_t data); +static ngx_int_t ngx_http_variable_location(ngx_http_request_t *r, + ngx_http_variable_value_t *v, uintptr_t data); static ngx_int_t ngx_http_variable_request_method(ngx_http_request_t *r, ngx_http_variable_value_t *v, uintptr_t data); static ngx_int_t ngx_http_variable_remote_user(ngx_http_request_t *r, @@ -206,6 +208,10 @@ static ngx_http_variable_t ngx_http_core_variables[] { ngx_string("server_name"), NULL, ngx_http_variable_server_name, 0, 0, 0 }, + { ngx_string("location"), NULL, + ngx_http_variable_location, 0, + NGX_HTTP_VAR_NOCACHEABLE, 0 }, + { ngx_string("request_method"), NULL, ngx_http_variable_request_method, 0, NGX_HTTP_VAR_NOCACHEABLE, 0 }, @@ -1382,6 +1388,28 @@ ngx_http_variable_server_name(ngx_http_request_t *r, v->no_cacheable = 0; v->not_found = 0; v->data = cscf->server_name.data; + + return NGX_OK; +} + + +static ngx_int_t +ngx_http_variable_location(ngx_http_request_t *r, + ngx_http_variable_value_t *v, uintptr_t data) +{ + ngx_http_core_loc_conf_t *clcf; + + clcf = ngx_http_get_module_loc_conf(r, ngx_http_core_module); + + if (clcf->regex) { + v->not_found = 1; + } else { + v->len = clcf->name.len; + v->valid = 1; + v->no_cacheable = 0; + v->not_found = 0; + v->data = clcf->name.data; + } return NGX_OK; } From appa at perusio.net Fri Jan 4 01:58:43 2013 From: appa at perusio.net (=?UTF-8?B?QW50w7NuaW8=?= P. P. Almeida) Date: Fri, 04 Jan 2013 02:58:43 +0100 Subject: [PATCH] implement a $location variable In-Reply-To: <20130104012204.GA26729@animata.net> References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> Message-ID: <87zk0pn1yk.wl%appa@perusio.net> On 4 Jan 2013 02h22 CET, david at gwynne.id.au wrote: > here's a diff that provides $location for use in not regex location > blocks. > > we're using it to provide easy to use mass hosting of drupals: > > xdlg at argon nginx$ cat drupal-controller.conf > root /var/www/apps/drupal; > try_files /index.php =404; > include fastcgi_params; > fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; > fastcgi_param SCRIPT_NAME $location$fastcgi_script_name; > fastcgi_intercept_errors on; > fastcgi_pass localhost:9000; > > which is used in server blocks like this: > > server { > listen 80; > server_name www.example.com; > > location / { include drupal-controller.conf; } > location /foo { include drupal-controller.conf; } > location /bar { include drupal-controller.conf; } > location /baz { include drupal-controller.conf; } > } > > i cannot otherwise find a nice way to use the locations name as a > parameter without specifying the value as a variable again within > the location. I fail to see the need for a $location variable in a Drupal Nginx config. Can you elaborate why? The multiple inclusion is only needed if you redefine any of the fastcgi_param(s) in each location. Have you each site installed in a subdir? Is that the case? I think this will probably work in your case: location ~ ^([^/]*)/.*$ { include drupal-controller.conf; fastcgi_param SCRIPT_NAME $current_location_base/$fastcgi_script_name; } where drupal-controller.conf is: root /var/www/apps/drupal; try_files /index.php =404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_intercept_errors on; fastcgi_pass localhost:9000; Try it out. --- appa > --- src/http/ngx_http_variables.c.orig Tue Jul 3 03:41:52 2012 > +++ src/http/ngx_http_variables.c Fri Jan 4 10:49:50 2013 > @@ -65,6 +65,8 @@ static ngx_int_t ngx_http_variable_request_filename(ng > ngx_http_variable_value_t *v, uintptr_t data); > static ngx_int_t ngx_http_variable_server_name(ngx_http_request_t *r, > ngx_http_variable_value_t *v, uintptr_t data); > +static ngx_int_t ngx_http_variable_location(ngx_http_request_t *r, > + ngx_http_variable_value_t *v, uintptr_t data); > static ngx_int_t ngx_http_variable_request_method(ngx_http_request_t *r, > ngx_http_variable_value_t *v, uintptr_t data); > static ngx_int_t ngx_http_variable_remote_user(ngx_http_request_t *r, > @@ -206,6 +208,10 @@ static ngx_http_variable_t ngx_http_core_variables[] > > { ngx_string("server_name"), NULL, ngx_http_variable_server_name, 0, > 0, 0 }, > > + { ngx_string("location"), NULL, > + ngx_http_variable_location, 0, > + NGX_HTTP_VAR_NOCACHEABLE, 0 }, > + { ngx_string("request_method"), NULL, > ngx_http_variable_request_method, 0, NGX_HTTP_VAR_NOCACHEABLE, 0 }, > @@ -1382,6 +1388,28 @@ > ngx_http_variable_server_name(ngx_http_request_t *r, > v->no_cacheable = 0; > v->not_found = 0; > v->data = cscf->server_name.data; > + > + return NGX_OK; > +} > + > + > +static ngx_int_t > +ngx_http_variable_location(ngx_http_request_t *r, > + ngx_http_variable_value_t *v, uintptr_t data) > +{ > + ngx_http_core_loc_conf_t *clcf; > + > + clcf = ngx_http_get_module_loc_conf(r, ngx_http_core_module); > + > + if (clcf->regex) { > + v->not_found = 1; > + } else { > + v->len = clcf->name.len; > + v->valid = 1; > + v->no_cacheable = 0; > + v->not_found = 0; > + v->data = clcf->name.data; > + } > > return NGX_OK; > } > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel From appa at perusio.net Fri Jan 4 02:10:38 2013 From: appa at perusio.net (=?UTF-8?B?QW50w7NuaW8=?= P. P. Almeida) Date: Fri, 04 Jan 2013 03:10:38 +0100 Subject: [PATCH] implement a $location variable In-Reply-To: <87zk0pn1yk.wl%appa@perusio.net> References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> <87zk0pn1yk.wl%appa@perusio.net> Message-ID: <87y5g9n1ep.wl%appa@perusio.net> On 4 Jan 2013 02h58 CET, appa at perusio.net wrote: > On 4 Jan 2013 02h22 CET, david at gwynne.id.au wrote: > >> here's a diff that provides $location for use in not regex location >> blocks. >> >> we're using it to provide easy to use mass hosting of drupals: >> >> xdlg at argon nginx$ cat drupal-controller.conf >> root /var/www/apps/drupal; >> try_files /index.php =404; >> include fastcgi_params; >> fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; >> fastcgi_param SCRIPT_NAME $location$fastcgi_script_name; >> fastcgi_intercept_errors on; >> fastcgi_pass localhost:9000; >> >> which is used in server blocks like this: >> >> server { >> listen 80; >> server_name www.example.com; >> >> location / { include drupal-controller.conf; } >> location /foo { include drupal-controller.conf; } >> location /bar { include drupal-controller.conf; } >> location /baz { include drupal-controller.conf; } >> } >> >> i cannot otherwise find a nice way to use the locations name as a >> parameter without specifying the value as a variable again within >> the location. > > I fail to see the need for a $location variable in a Drupal Nginx > config. Can you elaborate why? The multiple inclusion is only needed > if you redefine any of the fastcgi_param(s) in each location. > > Have you each site installed in a subdir? Is that the case? > > > I think this will probably work in your case: > > location ~ ^([^/]*)/.*$ { include > drupal-controller.conf; fastcgi_param SCRIPT_NAME > $current_location_base/$fastcgi_script_name; } Oops. Wrong regex. Rather: location / { include drupal-controller.conf; fastcgi_param SCRIPT_NAME $fastcgi_script_name; location ~ ^(/([^/]*).*$ { include drupal-controller.conf; fastcgi_param SCRIPT_NAME $current_location_base$fastcgi_script_name; } } --- appa From david at gwynne.id.au Fri Jan 4 02:18:58 2013 From: david at gwynne.id.au (David Gwynne) Date: Fri, 4 Jan 2013 12:18:58 +1000 Subject: [PATCH] implement a $location variable In-Reply-To: <87zk0pn1yk.wl%appa@perusio.net> References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> <87zk0pn1yk.wl%appa@perusio.net> Message-ID: On 04/01/2013, at 11:58 AM, Ant?nio P. P. Almeida wrote: > On 4 Jan 2013 02h22 CET, david at gwynne.id.au wrote: > >> here's a diff that provides $location for use in not regex location >> blocks. >> >> we're using it to provide easy to use mass hosting of drupals: >> >> xdlg at argon nginx$ cat drupal-controller.conf >> root /var/www/apps/drupal; >> try_files /index.php =404; >> include fastcgi_params; >> fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; >> fastcgi_param SCRIPT_NAME $location$fastcgi_script_name; >> fastcgi_intercept_errors on; >> fastcgi_pass localhost:9000; >> >> which is used in server blocks like this: >> >> server { >> listen 80; >> server_name www.example.com; >> >> location / { include drupal-controller.conf; } >> location /foo { include drupal-controller.conf; } >> location /bar { include drupal-controller.conf; } >> location /baz { include drupal-controller.conf; } >> } >> >> i cannot otherwise find a nice way to use the locations name as a >> parameter without specifying the value as a variable again within >> the location. > > I fail to see the need for a $location variable in a Drupal Nginx > config. Can you elaborate why? The multiple inclusion is only needed > if you redefine any of the fastcgi_param(s) in each location. need is a strong work, its just a lot nicer. > Have you each site installed in a subdir? Is that the case? no. it is a single copy of the drupal codebase which is shared by all the sites, they just have separate settings.php files. the way nginx tells drupal which settings to use is via SCRIPT_NAME based on $location. > > > I think this will probably work in your case: > > location ~ ^([^/]*)/.*$ { > include drupal-controller.conf; > fastcgi_param SCRIPT_NAME $current_location_base/$fastcgi_script_name; > } > > where drupal-controller.conf is: > > root /var/www/apps/drupal; > try_files /index.php =404; > include fastcgi_params; > fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; > fastcgi_param SCRIPT_NAME $fastcgi_script_name; > fastcgi_intercept_errors on; > fastcgi_pass localhost:9000; > > Try it out. im sure it would work, im just arguing that the configurations could be a lot more straightforward and readable using the patch below, and i wouldnt need to run pcre to get what is basically a copy of the value from the location block. > > --- appa > > > >> --- src/http/ngx_http_variables.c.orig Tue Jul 3 03:41:52 2012 >> +++ src/http/ngx_http_variables.c Fri Jan 4 10:49:50 2013 >> @@ -65,6 +65,8 @@ static ngx_int_t ngx_http_variable_request_filename(ng >> ngx_http_variable_value_t *v, uintptr_t data); >> static ngx_int_t ngx_http_variable_server_name(ngx_http_request_t *r, >> ngx_http_variable_value_t *v, uintptr_t data); >> +static ngx_int_t ngx_http_variable_location(ngx_http_request_t *r, >> + ngx_http_variable_value_t *v, uintptr_t data); >> static ngx_int_t ngx_http_variable_request_method(ngx_http_request_t *r, >> ngx_http_variable_value_t *v, uintptr_t data); >> static ngx_int_t ngx_http_variable_remote_user(ngx_http_request_t *r, >> @@ -206,6 +208,10 @@ static ngx_http_variable_t ngx_http_core_variables[] >> >> { ngx_string("server_name"), NULL, ngx_http_variable_server_name, 0, >> 0, 0 }, >> >> + { ngx_string("location"), NULL, >> + ngx_http_variable_location, 0, >> + NGX_HTTP_VAR_NOCACHEABLE, 0 }, >> + { ngx_string("request_method"), NULL, >> ngx_http_variable_request_method, 0, NGX_HTTP_VAR_NOCACHEABLE, 0 }, >> @@ -1382,6 +1388,28 @@ >> ngx_http_variable_server_name(ngx_http_request_t *r, >> v->no_cacheable = 0; >> v->not_found = 0; >> v->data = cscf->server_name.data; >> + >> + return NGX_OK; >> +} >> + >> + >> +static ngx_int_t >> +ngx_http_variable_location(ngx_http_request_t *r, >> + ngx_http_variable_value_t *v, uintptr_t data) >> +{ >> + ngx_http_core_loc_conf_t *clcf; >> + >> + clcf = ngx_http_get_module_loc_conf(r, ngx_http_core_module); >> + >> + if (clcf->regex) { >> + v->not_found = 1; >> + } else { >> + v->len = clcf->name.len; >> + v->valid = 1; >> + v->no_cacheable = 0; >> + v->not_found = 0; >> + v->data = clcf->name.data; >> + } >> >> return NGX_OK; >> } >> >> _______________________________________________ >> nginx-devel mailing list >> nginx-devel at nginx.org >> http://mailman.nginx.org/mailman/listinfo/nginx-devel > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel From mdounin at mdounin.ru Fri Jan 4 03:27:19 2013 From: mdounin at mdounin.ru (Maxim Dounin) Date: Fri, 4 Jan 2013 07:27:19 +0400 Subject: Nginx mutli-threaded plugin In-Reply-To: References: <20130101211922.GY40452@mdounin.ru> Message-ID: <20130104032719.GB12313@mdounin.ru> Hello! On Wed, Jan 02, 2013 at 10:37:48AM +0530, Fasih wrote: > Thank you Maxim. Will try to see if I can get to the single threaded model. > Basically when I was talking about accept_mutex, what I meant was, if the > worker thread is busy with my cpu-intensive work, I would obviously want > the other workers to take over. IIUC, if I have the accept mutex I am the > one who will take the requests, is it possible that my worker plugin is > caught up doing the work *and* has not released the mutex? In other words, > is it possible that my CPU intensive operation prevents other workers who > are free from taking requests with any configuration option > enabled/disabled. Accept mutex's job is to prevent multiple workers from accepting connections simulteneously, thus preventing unneded wakup of all worker processes for an accept() when new connection arrives. Accept mutex is released right after a wakup as soon as nginx reads list of events reported by kernel. It's not a load balancing mechanism. With a way things are normally done in nginx, busy workers are less likely to wait for kernel events and therefore less likely to get new connections (both with accept mutex enabled or accept mutex disabled), thus ensuring balancing between workers. > On Wed, Jan 2, 2013 at 2:49 AM, Maxim Dounin wrote: > > > Hello! > > > > On Tue, Jan 01, 2013 at 11:57:30PM +0530, Fasih wrote: > > > > > Hi guys > > > > > > I need to write a plugin which does some CPU intensive work. I want to be > > > able to create a thread which does some work and once done post an event > > > into nginx thread via ngx_add_timer. I tried compiling my plugin with > > > NGX_THREADS=pthread but that doesnt configure saying that the threading > > > support is broken. I can obviously switch to a single threaded mode but > > > that would be significantly difficult for me and would prefer to use only > > > as the very last resort. > > > > > > Can you please advice how to go about doing this? I am considering > > pulling > > > out the usage of 'ngx_event_timer_mutex' outside #if NGX_THREADS. > > Frankly I > > > am surprised how no other plugin had this kind of requirement, the > > "broken > > > support" commit has been there since quite some time now. > > > > Threading support as currently present was an experiment, and it's > > broken for a long time (some very limited part of it is still used > > on win32, but it's different story). I wouldn't expect you'll be > > able to work with threads without problems. > > > > > One final question, if I do the CPU intensive work in the nginx thread > > and > > > I have number of workers, how would the system behave? Will > > > accept_mutex on/off change the behavior? > > > > Accept mutex only ensures no two processes try to accept new > > connections at the same time, and it doesn't care how do you > > handle requests. Obviously enough it will change the behaviour, > > much like in any other case. > > > > -- > > Maxim Dounin > > http://nginx.com/support.html > > > > _______________________________________________ > > nginx-devel mailing list > > nginx-devel at nginx.org > > http://mailman.nginx.org/mailman/listinfo/nginx-devel > > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel -- Maxim Dounin http://nginx.com/support.html From mdounin at mdounin.ru Fri Jan 4 04:47:30 2013 From: mdounin at mdounin.ru (Maxim Dounin) Date: Fri, 4 Jan 2013 08:47:30 +0400 Subject: Book for module Development In-Reply-To: <20130102160205.19550.qmail@f4mail-235-163.rediffmail.com> References: <20130102160205.19550.qmail@f4mail-235-163.rediffmail.com> Message-ID: <20130104044729.GD12313@mdounin.ru> Hello! On Wed, Jan 02, 2013 at 04:02:05PM -0000, Sagar wrote: > Hi all, > > I am php developer having 6+ years of experience building > websites,portals,applications etc. > > I need some guidance in developing 3rd party modules for nginx. > But, i couldn't found any specific book for that. > > Please help me to walk on correct path, as i don't want to get > messed/frustrated, by choosing wrong directions in early stage. > > Currently, i am having following article with me to start with: > http://www.evanmiller.org/nginx-modules-guide-advanced.html > > Hoping for a favourable reply. Evan Miller's guide is good (although might be a bit outdated). I would recommend you to start with: http://www.evanmiller.org/nginx-modules-guide.html (Advanced guide you link to covers more advanced topics and assumes you are already familiar with basic things.) If in doubt, lots of module samples are available in nginx sources. -- Maxim Dounin http://nginx.com/support.html From yaoweibin at gmail.com Fri Jan 4 05:12:50 2013 From: yaoweibin at gmail.com (=?GB2312?B?0qbOsLHz?=) Date: Fri, 4 Jan 2013 13:12:50 +0800 Subject: nginx custom module thread local ctx In-Reply-To: References: Message-ID: see the config as an example: https://github.com/pagespeed/ngx_pagespeed/blob/master/config You should add the library std++ with gcc. 2012/12/29 Ruslan Mullakhmetov > Hi! > > I develop some module for nginx and need to use c++ source files in it. > > I found the way to compile it (extern c + compiler recognize .cpp files), > but know i need to specify some flags. > > Could you suggest a method to tell build system which compiler (CXX) and > which flags to use in module/config file? > > I saw in Makefile that it use $(CC) despite of there is unused definition > of $(CPP) which is actually preprocessor and no CXXFLAFS /CPPFLAGS. > > I will greatly appreciate your help. > > I could ?orrect Makefile myself but it get's irrating with each > reconfigure. > > -- > BR, Ruslan Mullakhmetov > > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel -- Weibin Yao Developer @ Server Platform Team of Taobao -------------- next part -------------- An HTML attachment was scrubbed... URL: From faskiri.devel at gmail.com Fri Jan 4 07:52:04 2013 From: faskiri.devel at gmail.com (Fasih) Date: Fri, 4 Jan 2013 13:22:04 +0530 Subject: Nginx mutli-threaded plugin In-Reply-To: <20130104032719.GB12313@mdounin.ru> References: <20130101211922.GY40452@mdounin.ru> <20130104032719.GB12313@mdounin.ru> Message-ID: Thank you again. Makes perfect sense On Fri, Jan 4, 2013 at 8:57 AM, Maxim Dounin wrote: > are normally done in nginx, busy workers are > less likely to wait for kernel events and therefore less likely to > get new connections (both with accept mutex enabled or accept > mutex disabled), thus ensuring balancing between workers. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From appa at perusio.net Fri Jan 4 09:04:44 2013 From: appa at perusio.net (=?UTF-8?B?QW50w7NuaW8=?= P. P. Almeida) Date: Fri, 04 Jan 2013 10:04:44 +0100 Subject: [PATCH] implement a $location variable In-Reply-To: References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> <87zk0pn1yk.wl%appa@perusio.net> Message-ID: <87vcbdmi8j.wl%appa@perusio.net> On 4 Jan 2013 03h18 CET, david at gwynne.id.au wrote: > need is a strong work, its just a lot nicer. > >> Have you each site installed in a subdir? Is that the case? > > no. it is a single copy of the drupal codebase which is shared by > all the sites, they just have separate settings.php files. the way > nginx tells drupal which settings to use is via SCRIPT_NAME based on > $location. Ok. If I understood correctly you have a typical multi-site setup. Why are you doing the host resolution at the server level? Drupal does it at the application level. It's capable of handling all hosts for which the vhost is configured to support. See: http://api.drupal.org/api/drupal/includes%21bootstrap.inc/function/conf_path/7 --- appa From david at gwynne.id.au Fri Jan 4 10:35:15 2013 From: david at gwynne.id.au (David Gwynne) Date: Fri, 4 Jan 2013 20:35:15 +1000 Subject: [PATCH] implement a $location variable In-Reply-To: <87vcbdmi8j.wl%appa@perusio.net> References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> <87zk0pn1yk.wl%appa@perusio.net> <87vcbdmi8j.wl%appa@perusio.net> Message-ID: <15ACD619-6E5B-4297-AFC3-BD3CD9A553D1@gwynne.id.au> On 04/01/2013, at 7:04 PM, Ant?nio P. P. Almeida wrote: > On 4 Jan 2013 03h18 CET, david at gwynne.id.au wrote: > >> need is a strong work, its just a lot nicer. >> >>> Have you each site installed in a subdir? Is that the case? >> >> no. it is a single copy of the drupal codebase which is shared by >> all the sites, they just have separate settings.php files. the way >> nginx tells drupal which settings to use is via SCRIPT_NAME based on >> $location. > > Ok. If I understood correctly you have a typical multi-site setup. Why > are you doing the host resolution at the server level? Drupal does it > at the application level. It's capable of handling all hosts for which > the vhost is configured to support. > > See: > http://api.drupal.org/api/drupal/includes%21bootstrap.inc/function/conf_path/7 that makes it look like i can pass $request_uri as SCRIPT_NAME. however, while drupal does get the right site settings.php file doing that, for some reason it cant figure out which page its on. it either generates a 404 or only shows the home page no matter what uri i give it in a web browser. while i do take the point that there are other ways of making drupal do what i want with and unpatched nginx, that doesnt mean other things couldnt make good use of a $location variable. dlg > > --- appa > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel From appa at perusio.net Fri Jan 4 11:06:56 2013 From: appa at perusio.net (=?UTF-8?B?QW50w7NuaW8=?= P. P. Almeida) Date: Fri, 04 Jan 2013 12:06:56 +0100 Subject: [PATCH] implement a $location variable In-Reply-To: <15ACD619-6E5B-4297-AFC3-BD3CD9A553D1@gwynne.id.au> References: <1B6DEF34-186D-4D03-B4BA-36B245EAA211@gwynne.id.au> <20121015145349.GG40452@mdounin.ru> <20121016144621.GT40452@mdounin.ru> <20130104012204.GA26729@animata.net> <87zk0pn1yk.wl%appa@perusio.net> <87vcbdmi8j.wl%appa@perusio.net> <15ACD619-6E5B-4297-AFC3-BD3CD9A553D1@gwynne.id.au> Message-ID: <87txqxmckv.wl%appa@perusio.net> On 4 Jan 2013 11h35 CET, david at gwynne.id.au wrote: > > On 04/01/2013, at 7:04 PM, Ant?nio P. P. Almeida > wrote: > >> On 4 Jan 2013 03h18 CET, david at gwynne.id.au wrote: >> >>> need is a strong work, its just a lot nicer. >>> >>>> Have you each site installed in a subdir? Is that the case? >>> >>> no. it is a single copy of the drupal codebase which is shared by >>> all the sites, they just have separate settings.php files. the way >>> nginx tells drupal which settings to use is via SCRIPT_NAME based >>> on $location. >> >> Ok. If I understood correctly you have a typical multi-site >> setup. Why are you doing the host resolution at the server level? >> Drupal does it at the application level. It's capable of handling >> all hosts for which the vhost is configured to support. >> >> See: >> http://api.drupal.org/api/drupal/includes%21bootstrap.inc/function/conf_path/7 > > that makes it look like i can pass $request_uri as > SCRIPT_NAME. however, while drupal does get the right site > settings.php file doing that, for some reason it cant figure out > which page its on. it either generates a 404 or only shows the home > page no matter what uri i give it in a web browser. That should work out of the box without any "tinkering". Here's a Drupal config that works with multisites as designed: https://github.com/perusio/drupal-with-nginx Also there's a Drupal group for Nginx: http://groups.drupal.org/nginx > while i do take the point that there are other ways of making drupal > do what i want with and unpatched nginx, that doesnt mean other > things couldnt make good use of a $location variable. Sure. You have to sell the idea to the Nginx devs. --- appa From kirilk at cloudxcel.com Fri Jan 4 13:41:18 2013 From: kirilk at cloudxcel.com (Kiril Kalchev) Date: Fri, 4 Jan 2013 15:41:18 +0200 Subject: Export all log specific variables Message-ID: Hi Guys, I made a patch for exporting all log only variable as common nginx variables. I am wandering how can I submit the patch to the official nginx devs. I am attaching the patch in this email. If I have to do something more please write me back. Patch was made for nginx 1.3.10 which is the newest development nginx release. -------------- next part -------------- A non-text attachment was scrubbed... Name: http_variables.patch Type: application/octet-stream Size: 4284 bytes Desc: not available URL: -------------- next part -------------- Regards, Kiril From orz at loli.my Fri Jan 4 15:29:08 2013 From: orz at loli.my (=?UTF-8?B?44OT44Oq44OT44Oq4oWk?=) Date: Fri, 4 Jan 2013 23:29:08 +0800 Subject: Nginx 1.3.10 Segfault Message-ID: #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 libselinux-2.0.94-5.3.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 zlib-1.2.3-27.el6.x86_64 (gdb) bt #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 #1 0x00000000004565c5 in ngx_http_log_variable (r=, buf=0xaf0fd08bab1b748d

, op=) at src/http/modules/ngx_http_log_module.c:901 #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at src/http/modules/ngx_http_log_module.c:308 #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc=) at src/http/ngx_http_request.c:3109 #4 ngx_http_free_request (r=0x1bf0070, rc=) at src/http/ngx_http_request.c:3064 #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at src/http/ngx_http_request.c:3017 #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at src/http/ngx_http_request.c:1214 #7 0x000000000044f890 in ngx_http_process_request_line (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, timer=, flags=) at src/event/modules/ngx_epoll_module.c:683 #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) at src/event/ngx_event.c:247 #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, data=) at src/os/unix/ngx_process_cycle.c:807 #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, proc=0x436180 , data=0x3, name=0x4e4875 "worker process", respawn=8) at src/os/unix/ngx_process.c:198 #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at src/os/unix/ngx_process_cycle.c:619 #13 ngx_master_process_cycle (cycle=0x15753e0) at src/os/unix/ngx_process_cycle.c:180 #14 0x0000000000414a0b in main (argc=, argv=) at src/core/nginx.c:412 (gdb) bt full #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 No symbol table info available. #1 0x00000000004565c5 in ngx_http_log_variable (r=, buf=0xaf0fd08bab1b748d

, op=) at src/http/modules/ngx_http_log_module.c:901 value = 0x1a82fe8 #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at src/http/modules/ngx_http_log_module.c:308 line = p = len = i = l = log = op = 0x1576bc0 buffer = 0x157e640 lcf = 0x1ae1868 #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc=) at src/http/ngx_http_request.c:3109 i = n = 1 log_handler = 0x1ca4cb8 #4 ngx_http_free_request (r=0x1bf0070, rc=) at src/http/ngx_http_request.c:3064 log = 0x1ba82b0 linger = {l_onoff = 28185920, l_linger = 0} cln = ctx = #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at src/http/ngx_http_request.c:3017 c = 0x7f39d3978610 #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at src/http/ngx_http_request.c:1214 n = rev = 0x7f39d37d4750 c = 0x7f39d3978610 #7 0x000000000044f890 in ngx_http_process_request_line (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 host = n = rc = -2 rv = c = 0x7f39d3978610 r = 0x1bf0070 #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, timer=, flags=) at src/event/modules/ngx_epoll_module.c:683 events = revents = instance = i = level = err = rev = 0x7f39d37d4750 wev = queue = c = 0x7f39d3978610 #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) at src/event/ngx_event.c:247 flags = timer = delta = 1357311866947 #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, data=) at src/os/unix/ngx_process_cycle.c:807 worker = i = c = #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, proc=0x436180 , data=0x3, name=0x4e4875 "worker process", respawn=8) at src/os/unix/ngx_process.c:198 on = 1 pid = 0 s = #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at src/os/unix/ngx_process_cycle.c:619 i = live = n = ch = {command = 2, pid = 22951, slot = 8, fd = -1} ccf = #13 ngx_master_process_cycle (cycle=0x15753e0) at src/os/unix/ngx_process_cycle.c:180 title = p = size = i = ---Type to continue, or q to quit--- n = sigio = 0 set = {__val = {0 }} itv = {it_interval = {tv_sec = 0, tv_usec = 21766488}, it_value = {tv_sec = 0, tv_usec = 0}} live = delay = 0 ls = ccf = 0x1575c78 #14 0x0000000000414a0b in main (argc=, argv=) at src/core/nginx.c:412 i = log = cycle = 0x14c2140 init_cycle = {conf_ctx = 0x0, pool = 0x14c1360, log = 0x728f80, new_log = {log_level = 0, file = 0x0, connection = 0, handler = 0, data = 0x0, action = 0x0}, files = 0x0, free_connections = 0x0, free_connection_n = 0, reusable_connections_queue = {prev = 0x0, next = 0x0}, listening = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, pool = 0x0}, paths = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, pool = 0x0}, open_files = {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, shared_memory = {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, connection_n = 0, files_n = 0, connections = 0x0, read_events = 0x0, write_events = 0x0, old_cycle = 0x0, conf_file = {len = 21, data = 0x4e0370 "/etc/nginx/nginx.conf"}, conf_param = {len = 0, data = 0x0}, conf_prefix = {len = 11, data = 0x4e0370 "/etc/nginx/nginx.conf"}, prefix = {len = 11, data = 0x4e0364 "/usr/local/"}, lock_file = {len = 0, data = 0x0}, hostname = { len = 0, data = 0x0}} ccf = 0x14c3058 (gdb) -------------- next part -------------- An HTML attachment was scrubbed... URL: From vbart at nginx.com Fri Jan 4 15:55:51 2013 From: vbart at nginx.com (Valentin V. Bartenev) Date: Fri, 4 Jan 2013 19:55:51 +0400 Subject: Nginx 1.3.10 Segfault In-Reply-To: References: Message-ID: <201301041955.51844.vbart@nginx.com> Please, try the patch from ticket 268: http://trac.nginx.org/nginx/ticket/268 wbr, Valentin V. Bartenev -- http://nginx.com/support.html http://nginx.org/en/donation.html On Friday 04 January 2013 19:29:08 ????? wrote: > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > Missing separate debuginfos, use: debuginfo-install > glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 > krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 > libselinux-2.0.94-5.3.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 > zlib-1.2.3-27.el6.x86_64 > (gdb) bt > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > buf=0xaf0fd08bab1b748d

, > op=) at src/http/modules/ngx_http_log_module.c:901 > #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at > src/http/modules/ngx_http_log_module.c:308 > #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc= optimized out>) at src/http/ngx_http_request.c:3109 > #4 ngx_http_free_request (r=0x1bf0070, rc=) at > src/http/ngx_http_request.c:3064 > #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at > src/http/ngx_http_request.c:3017 > #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at > src/http/ngx_http_request.c:1214 > #7 0x000000000044f890 in ngx_http_process_request_line > (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 > #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, > timer=, flags=) at > src/event/modules/ngx_epoll_module.c:683 > #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) > at src/event/ngx_event.c:247 > #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, > data=) at src/os/unix/ngx_process_cycle.c:807 > #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, proc=0x436180 > , data=0x3, name=0x4e4875 "worker process", > respawn=8) at src/os/unix/ngx_process.c:198 > #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at > src/os/unix/ngx_process_cycle.c:619 > #13 ngx_master_process_cycle (cycle=0x15753e0) at > src/os/unix/ngx_process_cycle.c:180 > #14 0x0000000000414a0b in main (argc=, argv= optimized out>) at src/core/nginx.c:412 > (gdb) bt full > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > No symbol table info available. > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > buf=0xaf0fd08bab1b748d

, > op=) at src/http/modules/ngx_http_log_module.c:901 > value = 0x1a82fe8 > #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at > src/http/modules/ngx_http_log_module.c:308 > line = > p = > len = > i = > l = > log = > op = 0x1576bc0 > buffer = 0x157e640 > lcf = 0x1ae1868 > #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc= optimized out>) at src/http/ngx_http_request.c:3109 > i = > n = 1 > log_handler = 0x1ca4cb8 > #4 ngx_http_free_request (r=0x1bf0070, rc=) at > src/http/ngx_http_request.c:3064 > log = 0x1ba82b0 > linger = {l_onoff = 28185920, l_linger = 0} > cln = > ctx = > #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at > src/http/ngx_http_request.c:3017 > c = 0x7f39d3978610 > #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at > src/http/ngx_http_request.c:1214 > n = > rev = 0x7f39d37d4750 > c = 0x7f39d3978610 > #7 0x000000000044f890 in ngx_http_process_request_line > (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 > host = > n = > rc = -2 > rv = > c = 0x7f39d3978610 > r = 0x1bf0070 > #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, > timer=, flags=) at > src/event/modules/ngx_epoll_module.c:683 > events = > revents = > instance = > i = > level = > err = > rev = 0x7f39d37d4750 > wev = > queue = > c = 0x7f39d3978610 > #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) > at src/event/ngx_event.c:247 > flags = > timer = > delta = 1357311866947 > #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, > data=) at src/os/unix/ngx_process_cycle.c:807 > worker = > i = > c = > #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, proc=0x436180 > , data=0x3, name=0x4e4875 "worker process", > respawn=8) at src/os/unix/ngx_process.c:198 > on = 1 > pid = 0 > s = > #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at > src/os/unix/ngx_process_cycle.c:619 > i = > live = > n = > ch = {command = 2, pid = 22951, slot = 8, fd = -1} > ccf = > #13 ngx_master_process_cycle (cycle=0x15753e0) at > src/os/unix/ngx_process_cycle.c:180 > title = > p = > size = > i = > ---Type to continue, or q to quit--- > n = > sigio = 0 > set = {__val = {0 }} > itv = {it_interval = {tv_sec = 0, tv_usec = 21766488}, it_value = > {tv_sec = 0, tv_usec = 0}} > live = > delay = 0 > ls = > ccf = 0x1575c78 > #14 0x0000000000414a0b in main (argc=, argv= optimized out>) at src/core/nginx.c:412 > i = > log = > cycle = 0x14c2140 > init_cycle = {conf_ctx = 0x0, pool = 0x14c1360, log = 0x728f80, > new_log = {log_level = 0, file = 0x0, connection = 0, handler = 0, data = > 0x0, action = 0x0}, files = 0x0, free_connections = 0x0, > free_connection_n = 0, reusable_connections_queue = {prev = 0x0, > next = 0x0}, listening = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, pool > = 0x0}, paths = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, > pool = 0x0}, open_files = {last = 0x0, part = {elts = 0x0, > nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, shared_memory = > {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, > nalloc = 0, pool = 0x0}, connection_n = 0, files_n = 0, > connections = 0x0, read_events = 0x0, write_events = 0x0, old_cycle = 0x0, > conf_file = {len = 21, data = 0x4e0370 "/etc/nginx/nginx.conf"}, > conf_param = {len = 0, data = 0x0}, conf_prefix = {len = 11, data > = 0x4e0370 "/etc/nginx/nginx.conf"}, prefix = {len = 11, data = 0x4e0364 > "/usr/local/"}, lock_file = {len = 0, data = 0x0}, hostname = { > len = 0, data = 0x0}} > ccf = 0x14c3058 > (gdb) From orz at loli.my Fri Jan 4 16:14:56 2013 From: orz at loli.my (=?UTF-8?B?44OT44Oq44OT44Oq4oWk?=) Date: Sat, 5 Jan 2013 00:14:56 +0800 Subject: Nginx 1.3.10 Segfault In-Reply-To: <201301041955.51844.vbart@nginx.com> References: <201301041955.51844.vbart@nginx.com> Message-ID: ok, I will try that. 2013/1/4 Valentin V. Bartenev > Please, try the patch from ticket 268: > http://trac.nginx.org/nginx/ticket/268 > > wbr, Valentin V. Bartenev > > -- > http://nginx.com/support.html > http://nginx.org/en/donation.html > > > On Friday 04 January 2013 19:29:08 ????? wrote: > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > Missing separate debuginfos, use: debuginfo-install > > glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 > > krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 > > libselinux-2.0.94-5.3.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 > > zlib-1.2.3-27.el6.x86_64 > > (gdb) bt > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > > buf=0xaf0fd08bab1b748d

, > > op=) at src/http/modules/ngx_http_log_module.c:901 > > #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at > > src/http/modules/ngx_http_log_module.c:308 > > #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc= > optimized out>) at src/http/ngx_http_request.c:3109 > > #4 ngx_http_free_request (r=0x1bf0070, rc=) at > > src/http/ngx_http_request.c:3064 > > #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at > > src/http/ngx_http_request.c:3017 > > #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at > > src/http/ngx_http_request.c:1214 > > #7 0x000000000044f890 in ngx_http_process_request_line > > (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 > > #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, > > timer=, flags=) at > > src/event/modules/ngx_epoll_module.c:683 > > #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) > > at src/event/ngx_event.c:247 > > #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, > > data=) at src/os/unix/ngx_process_cycle.c:807 > > #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, > proc=0x436180 > > , data=0x3, name=0x4e4875 "worker process", > > respawn=8) at src/os/unix/ngx_process.c:198 > > #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:619 > > #13 ngx_master_process_cycle (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:180 > > #14 0x0000000000414a0b in main (argc=, argv= > optimized out>) at src/core/nginx.c:412 > > (gdb) bt full > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > No symbol table info available. > > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > > buf=0xaf0fd08bab1b748d

, > > op=) at src/http/modules/ngx_http_log_module.c:901 > > value = 0x1a82fe8 > > #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at > > src/http/modules/ngx_http_log_module.c:308 > > line = > > p = > > len = > > i = > > l = > > log = > > op = 0x1576bc0 > > buffer = 0x157e640 > > lcf = 0x1ae1868 > > #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc= > optimized out>) at src/http/ngx_http_request.c:3109 > > i = > > n = 1 > > log_handler = 0x1ca4cb8 > > #4 ngx_http_free_request (r=0x1bf0070, rc=) at > > src/http/ngx_http_request.c:3064 > > log = 0x1ba82b0 > > linger = {l_onoff = 28185920, l_linger = 0} > > cln = > > ctx = > > #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at > > src/http/ngx_http_request.c:3017 > > c = 0x7f39d3978610 > > #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at > > src/http/ngx_http_request.c:1214 > > n = > > rev = 0x7f39d37d4750 > > c = 0x7f39d3978610 > > #7 0x000000000044f890 in ngx_http_process_request_line > > (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 > > host = > > n = > > rc = -2 > > rv = > > c = 0x7f39d3978610 > > r = 0x1bf0070 > > #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, > > timer=, flags=) at > > src/event/modules/ngx_epoll_module.c:683 > > events = > > revents = > > instance = > > i = > > level = > > err = > > rev = 0x7f39d37d4750 > > wev = > > queue = > > c = 0x7f39d3978610 > > #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) > > at src/event/ngx_event.c:247 > > flags = > > timer = > > delta = 1357311866947 > > #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, > > data=) at src/os/unix/ngx_process_cycle.c:807 > > worker = > > i = > > c = > > #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, > proc=0x436180 > > , data=0x3, name=0x4e4875 "worker process", > > respawn=8) at src/os/unix/ngx_process.c:198 > > on = 1 > > pid = 0 > > s = > > #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:619 > > i = > > live = > > n = > > ch = {command = 2, pid = 22951, slot = 8, fd = -1} > > ccf = > > #13 ngx_master_process_cycle (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:180 > > title = > > p = > > size = > > i = > > ---Type to continue, or q to quit--- > > n = > > sigio = 0 > > set = {__val = {0 }} > > itv = {it_interval = {tv_sec = 0, tv_usec = 21766488}, it_value = > > {tv_sec = 0, tv_usec = 0}} > > live = > > delay = 0 > > ls = > > ccf = 0x1575c78 > > #14 0x0000000000414a0b in main (argc=, argv= > optimized out>) at src/core/nginx.c:412 > > i = > > log = > > cycle = 0x14c2140 > > init_cycle = {conf_ctx = 0x0, pool = 0x14c1360, log = 0x728f80, > > new_log = {log_level = 0, file = 0x0, connection = 0, handler = 0, data = > > 0x0, action = 0x0}, files = 0x0, free_connections = 0x0, > > free_connection_n = 0, reusable_connections_queue = {prev = > 0x0, > > next = 0x0}, listening = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, > pool > > = 0x0}, paths = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, > > pool = 0x0}, open_files = {last = 0x0, part = {elts = 0x0, > > nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, shared_memory > = > > {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, > > nalloc = 0, pool = 0x0}, connection_n = 0, files_n = 0, > > connections = 0x0, read_events = 0x0, write_events = 0x0, old_cycle = > 0x0, > > conf_file = {len = 21, data = 0x4e0370 "/etc/nginx/nginx.conf"}, > > conf_param = {len = 0, data = 0x0}, conf_prefix = {len = 11, > data > > = 0x4e0370 "/etc/nginx/nginx.conf"}, prefix = {len = 11, data = 0x4e0364 > > "/usr/local/"}, lock_file = {len = 0, data = 0x0}, hostname = { > > len = 0, data = 0x0}} > > ccf = 0x14c3058 > > (gdb) > > > > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From vshebordaev at mail.ru Fri Jan 4 18:04:01 2013 From: vshebordaev at mail.ru (Vladimir Shebordaev) Date: Fri, 04 Jan 2013 22:04:01 +0400 Subject: Export all log specific variables In-Reply-To: References: Message-ID: <50E71991.8060409@mail.ru> Hi, On 04.01.2013 17:41, Kiril Kalchev wrote: > Hi Guys, > > I made a patch for exporting all log only variable as common nginx variables. I am wandering how can I submit the patch to the official nginx devs. I am attaching the patch in this email. If I have to do something more please write me back. Patch was made for nginx 1.3.10 which is the newest development nginx release. > I guess, nginx-devel@ is the only proper place to send in a patch. Btw, please don't hesitate to check out this thread Regards, Vladimir > > Regards, > Kiril > > From orz at loli.my Sat Jan 5 04:30:57 2013 From: orz at loli.my (=?UTF-8?B?44OT44Oq44OT44Oq4oWk?=) Date: Sat, 5 Jan 2013 12:30:57 +0800 Subject: Nginx 1.3.10 Segfault In-Reply-To: <201301041955.51844.vbart@nginx.com> References: <201301041955.51844.vbart@nginx.com> Message-ID: patched is still throw the same segfault. I think may be cause by 1.3.9 feature: *) Feature: the $request_time and $msec variables can now be used not only in the "log_format" directive. 2013/1/4 Valentin V. Bartenev > Please, try the patch from ticket 268: > http://trac.nginx.org/nginx/ticket/268 > > wbr, Valentin V. Bartenev > > -- > http://nginx.com/support.html > http://nginx.org/en/donation.html > > > On Friday 04 January 2013 19:29:08 ????? wrote: > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > Missing separate debuginfos, use: debuginfo-install > > glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 > > krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 > > libselinux-2.0.94-5.3.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 > > zlib-1.2.3-27.el6.x86_64 > > (gdb) bt > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > > buf=0xaf0fd08bab1b748d

, > > op=) at src/http/modules/ngx_http_log_module.c:901 > > value = 0x1a82fe8 > > #2 0x0000000000456ec5 in ngx_http_log_handler (r=0x1bf0070) at > > src/http/modules/ngx_http_log_module.c:308 > > line = > > p = > > len = > > i = > > l = > > log = > > op = 0x1576bc0 > > buffer = 0x157e640 > > lcf = 0x1ae1868 > > #3 0x000000000044b847 in ngx_http_log_request (r=0x1bf0070, rc= > optimized out>) at src/http/ngx_http_request.c:3109 > > i = > > n = 1 > > log_handler = 0x1ca4cb8 > > #4 ngx_http_free_request (r=0x1bf0070, rc=) at > > src/http/ngx_http_request.c:3064 > > log = 0x1ba82b0 > > linger = {l_onoff = 28185920, l_linger = 0} > > cln = > > ctx = > > #5 0x000000000044ca9b in ngx_http_close_request (r=0x1bf0070, rc=400) at > > src/http/ngx_http_request.c:3017 > > c = 0x7f39d3978610 > > #6 0x000000000044ed1e in ngx_http_read_request_header (r=0x1bf0070) at > > src/http/ngx_http_request.c:1214 > > n = > > rev = 0x7f39d37d4750 > > c = 0x7f39d3978610 > > #7 0x000000000044f890 in ngx_http_process_request_line > > (rev=0x7f39d37d4750) at src/http/ngx_http_request.c:743 > > host = > > n = > > rc = -2 > > rv = > > c = 0x7f39d3978610 > > r = 0x1bf0070 > > #8 0x0000000000438dc1 in ngx_epoll_process_events (cycle=0x15753e0, > > timer=, flags=) at > > src/event/modules/ngx_epoll_module.c:683 > > events = > > revents = > > instance = > > i = > > level = > > err = > > rev = 0x7f39d37d4750 > > wev = > > queue = > > c = 0x7f39d3978610 > > #9 0x000000000042e957 in ngx_process_events_and_timers (cycle=0x15753e0) > > at src/event/ngx_event.c:247 > > flags = > > timer = > > delta = 1357311866947 > > #10 0x0000000000436249 in ngx_worker_process_cycle (cycle=0x15753e0, > > data=) at src/os/unix/ngx_process_cycle.c:807 > > worker = > > i = > > c = > > #11 0x00000000004347d4 in ngx_spawn_process (cycle=0x15753e0, > proc=0x436180 > > , data=0x3, name=0x4e4875 "worker process", > > respawn=8) at src/os/unix/ngx_process.c:198 > > on = 1 > > pid = 0 > > s = > > #12 0x000000000043723f in ngx_reap_children (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:619 > > i = > > live = > > n = > > ch = {command = 2, pid = 22951, slot = 8, fd = -1} > > ccf = > > #13 ngx_master_process_cycle (cycle=0x15753e0) at > > src/os/unix/ngx_process_cycle.c:180 > > title = > > p = > > size = > > i = > > ---Type to continue, or q to quit--- > > n = > > sigio = 0 > > set = {__val = {0 }} > > itv = {it_interval = {tv_sec = 0, tv_usec = 21766488}, it_value = > > {tv_sec = 0, tv_usec = 0}} > > live = > > delay = 0 > > ls = > > ccf = 0x1575c78 > > #14 0x0000000000414a0b in main (argc=, argv= > optimized out>) at src/core/nginx.c:412 > > i = > > log = > > cycle = 0x14c2140 > > init_cycle = {conf_ctx = 0x0, pool = 0x14c1360, log = 0x728f80, > > new_log = {log_level = 0, file = 0x0, connection = 0, handler = 0, data = > > 0x0, action = 0x0}, files = 0x0, free_connections = 0x0, > > free_connection_n = 0, reusable_connections_queue = {prev = > 0x0, > > next = 0x0}, listening = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, > pool > > = 0x0}, paths = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, > > pool = 0x0}, open_files = {last = 0x0, part = {elts = 0x0, > > nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, shared_memory > = > > {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, > > nalloc = 0, pool = 0x0}, connection_n = 0, files_n = 0, > > connections = 0x0, read_events = 0x0, write_events = 0x0, old_cycle = > 0x0, > > conf_file = {len = 21, data = 0x4e0370 "/etc/nginx/nginx.conf"}, > > conf_param = {len = 0, data = 0x0}, conf_prefix = {len = 11, > data > > = 0x4e0370 "/etc/nginx/nginx.conf"}, prefix = {len = 11, data = 0x4e0364 > > "/usr/local/"}, lock_file = {len = 0, data = 0x0}, hostname = { > > len = 0, data = 0x0}} > > ccf = 0x14c3058 > > (gdb) > > > > > _______________________________________________ > nginx-devel mailing list > nginx-devel at nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From orz at loli.my Sat Jan 5 04:35:11 2013 From: orz at loli.my (=?UTF-8?B?44OT44Oq44OT44Oq4oWk?=) Date: Sat, 5 Jan 2013 12:35:11 +0800 Subject: Nginx 1.3.10 Segfault In-Reply-To: <201301041955.51844.vbart@nginx.com> References: <201301041955.51844.vbart@nginx.com> Message-ID: here is my log_format log_format logger '$http_host||$remote_addr||$msec||$status||$request_length||$bytes_sent||"$request"||"$http_referer"||"$http_user_agent"||$upstream_cache_status||$upstream_status||$request_time||$upstream_response_time'; 2013/1/4 Valentin V. Bartenev > Please, try the patch from ticket 268: > http://trac.nginx.org/nginx/ticket/268 > > wbr, Valentin V. Bartenev > > -- > http://nginx.com/support.html > http://nginx.org/en/donation.html > > > On Friday 04 January 2013 19:29:08 ????? wrote: > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > Missing separate debuginfos, use: debuginfo-install > > glibc-2.12-1.80.el6_3.6.x86_64 keyutils-libs-1.4-4.el6.x86_64 > > krb5-libs-1.9-33.el6_3.3.x86_64 libcom_err-1.41.12-12.el6.x86_64 > > libselinux-2.0.94-5.3.el6.x86_64 openssl-1.0.0-25.el6_3.1.x86_64 > > zlib-1.2.3-27.el6.x86_64 > > (gdb) bt > > #0 0x000000348a289087 in memcpy () from /lib64/libc.so.6 > > #1 0x00000000004565c5 in ngx_http_log_variable (r=, > > buf=0xaf0fd08bab1b748d