Giter VIP home page Giter VIP logo

ngx_zeromq's People

Contributors

piotrsikora avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ngx_zeromq's Issues

88: Socket operation on non-socket

When I post http call, it prompt
10 connect() failed (88: Socket operation on non-socket) while connecting to upstream, client: 127.0.0.1, server:

Questions on nginx, ngx_zeromq and uwsgi

Hi,

I has one of our servers powered by nginx, uwsgi and Bottle WSGI framework for a while now. The deployment model is as follows:

request --> nginx + uwsgi plugin (port 80/HTTP protocol) ---> (forward) --> uwsgi web server (port 8080/uwsgi protocol)---> WSGI app

I learn from this project that this plugin can speak in uwsgi. What does it mean?

  1. nginx parses HTTP packets (header + body) into uwsgi packets and push them to zeromq-based queue. uWSGI must some ways to pick messages from that queue
  2. nginx parses HTTP packets (header + body) into uwsgi packets and push them to zeromq-based queue. There is a built-in process picks messages from that queue and push them to uwsgi server.
  3. nginx parses HTTP packets (header + body) into uwsgi packets and push them to zeromq-based queue. Developer write uwsgi-aware workers that pick messages from that queue, parse that piece of information into WSGI friendly values and handle it

Thanks

Dinh

"stream processing" the incoming request

@PiotrSikora: great stuff. I see you're playing with the Push/Pull sockets also..

Q: Does nginx allow access to the incoming stream? For example, "parsed headers", "parsed body chunk", etc, or do you have to wait until the entire request completes before you have access to it?

Cannot talk to ZMQ, connect failed

I am running Nginx with the ngx_zeromq module, and I believe everything is built and running to some degree. I can get resources from my Nginx server, but when I attempt to hit the ZMQ proxy I get an error.

My configuration is identical to the example given in the readme,md:

http {
    upstream blackhole {
        zeromq_remote   REQ tcp://127.0.0.1:5555;
    }

    server {
        location / {
            proxy_pass  http://blackhole;
        }
    }
}

The error I am getting from the error.log is:

2014/05/28 11:06:08 [alert] 5836#0: *4 connect() failed (88: Socket operation on non-socket) while connecting to upstream, client: 10.xxx.154.yyy,
   server: localhost, request: "GET /zmq HTTP/1.1", upstream: "http://tcp://127.0.0.1:5555/zmq", host: "dans-ubuntu-8375.lvs01.dev.xxx.com"

Any ideas why the two protocols on the upstream value? I tried changing the proxy_passs to tcp:// or leaving it off, and got config loading errors. Any remedies appreciated.
Thanks, Dan

Always 502s

I created this https://github.com/jamesmarlowe/ngx-zmq-sample so that I could test the functionality of this module. After following the README though, all I am able to get from curling localhost/ is:

<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>openresty/1.7.7.1</center>
</body>
</html>

If I am just using it incorrectly, I would love to hear as I would really like to use this module. Any help appreciated.

Question about PULL PUSH and module overall

Good day.

First of all, excuse me for asking the question instead of reading sources.

  1. Are zmq sockets integrated to nginx event loop? I believe so, but still want to get definite answer
  2. Could you provide example config where both PUSH and PULL configured for upstream?
    1. Will nginx will detect message incoming to PULL socket as an answer for message sent into PUSH socket? How does he do it if so?
    2. Which way client should determine address of PULL socket configured in Nginx?

With respect,
Yura

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.