error with ubuntu 14.04

sumanadak · 2014-05-12T03:12:35+00:00

Hello! On Mon, May 12, 2014 at 11:07 AM, arthurx wrote: > I am actually trying to connect to Elasticsearch, which has endpoint like > this > > c...

error with ubuntu 14.04

sumanadak

Dear all,

I am using ubuntu 14.04 and build as said in site.

I was trying to run hello world from openresty site but I got this error

sudo nginx -p `pwd`/ -c conf/nginx.conf

nginx: [emerg] unknown directive "content_by_lua" in /home/suman/project_work/ngnixwork/conf/nginx.conf:13

Can someone help me??

Thanks

suman

agentzh

Hello!

On Sun, May 11, 2014 at 3:10 AM,  sumanadak wrote:
> I was trying to run hello world from openresty site but I got this error
>
> sudo nginx -p `pwd`/ -c conf/nginx.conf
> nginx: [emerg] unknown directive "content_by_lua" in
> /home/suman/project_work/ngnixwork/conf/nginx.conf:13
>

I think you were just trying to start the wrong nginx (you have
multiple nginx installations in the same system). By default,
openresty's nginx is installed to the location
/usr/local/openresty/nginx/sbin/nginx, so ensure this nginx's path
appears first in your PATH environment. And you can always use the
command "which nginx" to find out what is the current nginx you're
using, or just specify the absolute path of the right nginx on your
command line.

See also http://openresty.org/#GettingStarted

Regards,
-agentzh

sumanadak

Hi agentzh,

Thanks a lot.

solved the problem!!

Meanwhile, I would like to get help for my project. I am thinking to build API gateway based on nginx. Here is what I thought till now...

I am already running ngnix proxy on top of our API service. I am just thinking if I can use ngnix as API gateway like 3scale does. For all authentication and monitoring, redis can be used as data channel. Once I do API publishing with web based GUI, all rules will be published with redis. Ngnix would check rules before dispatching back-end API service, All monitoring logs also goes with redis ->logstash-> elasticsearch->kibana can be used for visualization of API traffic. This approach might save a round trip with API gateway server for authentication and metrics collection.

Please guide me to achieve this. What should I learn and guide me if it is a right approach or not. Also please help me to write nginx module for that.

Thanks

suman.

On Monday, May 12, 2014 12:45:35 AM UTC+5:30, agentzh wrote:

Hello!

On Sun, May 11, 2014 at 3:10 AM, sumanadak wrote:
> I was trying to run hello world from openresty site but I got this error
>
> sudo nginx -p `pwd`/ -c conf/nginx.conf
> nginx: [emerg] unknown directive "content_by_lua" in
> /home/suman/project_work/ngnixwork/conf/nginx.conf:13
>

I think you were just trying to start the wrong nginx (you have
multiple nginx installations in the same system). By default,
openresty's nginx is installed to the location
/usr/local/openresty/nginx/sbin/nginx, so ensure this nginx's path
appears first in your PATH environment. And you can always use the
command "which nginx" to find out what is the current nginx you're
using, or just specify the absolute path of the right nginx on your
command line.

See also http://openresty.org/#GettingStarted

Regards,
-agentzh

agentzh

Hello!

On Mon, May 12, 2014 at 11:02 AM, Suman Adak wrote:
> I am already running ngnix proxy on top of our API service. I am just
> thinking if I can use ngnix as API gateway like 3scale does. For all
> authentication and monitoring, redis can be used as data channel. Once I do
> API publishing with web based GUI, all rules will be published with redis.
> Ngnix would check rules before dispatching back-end API service, All
> monitoring logs also goes with redis ->logstash-> elasticsearch->kibana can
> be used for visualization of API traffic. This approach might save a round
> trip with API gateway server for authentication and metrics collection.
>

Yes, this looks like perfect fit for OpenResty :)

You're welcome to ask more specific questions here when you have a
particular problem or something. But you'd better google for an answer
first to avoid FAQs (like the one you asked in this thread).

Best regards,
-agentzh

sumanadak

Hi,

Thanks. I will do. Sure I will keep this in mind.

Thanks

suman

On Tue, May 13, 2014 at 12:08 AM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Mon, May 12, 2014 at 11:02 AM, Suman Adak wrote:
> I am already running ngnix proxy on top of our API service. I am just
> thinking if I can use ngnix as API gateway like 3scale does. For all
> authentication and monitoring, redis can be used as data channel. Once I do
> API publishing with web based GUI, all rules will be published with redis.
> Ngnix would check rules before dispatching back-end API service, All
> monitoring logs also goes with redis ->logstash-> elasticsearch->kibana can
> be used for visualization of API traffic. This approach might save a round
> trip with API gateway server for authentication and metrics collection.
>

Yes, this looks like perfect fit for OpenResty :)

You're welcome to ask more specific questions here when you have a
particular problem or something. But you'd better google for an answer
first to avoid FAQs (like the one you asked in this thread).

Best regards,

-agentzh.

--
Thanks and Regards
Suman Adak

sumanadak

Dear All,

I am getting error same again though I set the correct nginx path in my system

here is my error msg
suman@suman-ripsac:~/project_work/ngnixwork$ sudo nginx -p `pwd`/ -c conf/nginx.conf
nginx: [emerg] unknown directive "content_by_lua" in /home/suman/project_work/ngnixwork/conf/nginx.conf:13
suman@suman-ripsac:~/project_work/ngnixwork$ which nginx
/usr/local/openresty/nginx/sbin/nginx
suman@suman-ripsac:~/project_work/ngnixwork$ nginx -v
nginx version: openresty/1.5.12.1
suman@suman-ripsac:~/project_work/ngnixwork$

Trying to run helloworld program only. I was able to run successfully after correcting path but dont know why it showing error again. Sorry, I am very new to nginx world.. I make sure. nothing is run on 8080 and no nginx process. Could someone tell me the possible reason???

Thanks

Suman

On Mon, May 12, 2014 at 11:32 PM, Suman Adak <suma...@gmail.com> wrote:

Hi agentzh,
Thanks a lot.
solved the problem!!

Meanwhile, I would like to get help for my project. I am thinking to build API gateway based on nginx. Here is what I thought till now...

I am already running ngnix proxy on top of our API service. I am just thinking if I can use ngnix as API gateway like 3scale does. For all authentication and monitoring, redis can be used as data channel. Once I do API publishing with web based GUI, all rules will be published with redis. Ngnix would check rules before dispatching back-end API service, All monitoring logs also goes with redis ->logstash-> elasticsearch->kibana can be used for visualization of API traffic. This approach might save a round trip with API gateway server for authentication and metrics collection.

Please guide me to achieve this. What should I learn and guide me if it is a right approach or not. Also please help me to write nginx module for that.

Thanks
suman.

On Monday, May 12, 2014 12:45:35 AM UTC+5:30, agentzh wrote:
Hello!

On Sun, May 11, 2014 at 3:10 AM, sumanadak wrote:
> I was trying to run hello world from openresty site but I got this error
>
> sudo nginx -p `pwd`/ -c conf/nginx.conf
> nginx: [emerg] unknown directive "content_by_lua" in
> /home/suman/project_work/ngnixwork/conf/nginx.conf:13
>

I think you were just trying to start the wrong nginx (you have
multiple nginx installations in the same system). By default,
openresty's nginx is installed to the location
/usr/local/openresty/nginx/sbin/nginx, so ensure this nginx's path
appears first in your PATH environment. And you can always use the
command "which nginx" to find out what is the current nginx you're
using, or just specify the absolute path of the right nginx on your
command line.

See also http://openresty.org/#GettingStarted

Regards,
-agentzh

.

--
Thanks and Regards
Suman Adak

agentzh

Hello!

On Tue, May 13, 2014 at 12:05 PM, Suman Adak wrote:
> here is my error msg
> suman@suman-ripsac:~/project_work/ngnixwork$ sudo nginx -p `pwd`/ -c
> conf/nginx.conf
>
> nginx: [emerg] unknown directive "content_by_lua" in
> /home/suman/project_work/ngnixwork/conf/nginx.conf:13
>
> suman@suman-ripsac:~/project_work/ngnixwork$ which nginx
> /usr/local/openresty/nginx/sbin/nginx

Well, this is a common mistake for *NIX beginners. When you use
"sudo", you're actually using the "root" user, which usually has a
different PATH environment than your own user account. You're still
invoking the wrong nginx. Try the command "sudo which nginx" (do not
miss the "sudo" part!) to see which nginx you're actually using.

Regards,
-agentzh

sumanadak

Hi,

Ohhh!! such a silly mistake!! I am sorry. I learned. Thanks for a great and prompt help.

Thanks

Suman

On Wed, May 14, 2014 at 12:42 AM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Tue, May 13, 2014 at 12:05 PM, Suman Adak wrote:
> here is my error msg
> suman@suman-ripsac:~/project_work/ngnixwork$ sudo nginx -p `pwd`/ -c
> conf/nginx.conf
>
> nginx: [emerg] unknown directive "content_by_lua" in
> /home/suman/project_work/ngnixwork/conf/nginx.conf:13
>
> suman@suman-ripsac:~/project_work/ngnixwork$ which nginx
> /usr/local/openresty/nginx/sbin/nginx

Well, this is a common mistake for *NIX beginners. When you use
"sudo", you're actually using the "root" user, which usually has a
different PATH environment than your own user account. You're still
invoking the wrong nginx. Try the command "sudo which nginx" (do not
miss the "sudo" part!) to see which nginx you're actually using.

Regards,
-agentzh.

--
Thanks and Regards
Suman Adak