Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
.
Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . rpaprocki Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . rpaprocki The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . rpaprocki The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . rpaprocki The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . rpaprocki The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. . dsgnvictor Works! Yes, there was a stray server in the config.Thanks so much for your help!On Wed, Feb 28, 2018 at 8:44 PM, Robert Paprocki <rpap...@fearnothingproductions.net> wrote:The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
The answer is pretty clear, process 5047 is trying to bind to 0.0.0.0:80. Double check your config file and make sure you don't have a stray server {} block.On Wed, Feb 28, 2018 at 11:37 AM, Wiktor Sadowski <dsgn...@gmail.com> wrote:As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
As for what I'm trying to accomplish:I have an openresty bundle in /usr/local/restyix, listening on 80. Running.Works great. Self contained, compiled with -rpath. Awesome :-)And another openresty in /usr/local/cyix, configured to listen on 22222. I would like to run it simultaneously with the already running one.But I'm not able to start that 22222 - errors in the log:2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: bind() to 0.0.0.0:80 failed (98: Address already in use)2018/02/28 20:04:56 [emerg] 5047#5047: still could not bind()If I stop restyix:80 then can start cyix:22222, but not able to get running both at the same time.On Wed, Feb 28, 2018 at 6:55 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Can you please provide a complete, minimal example of what you're trying to accomplish, as well as error output, so we can reproduce what you're running into? There's a distinct lack of details of what specific problem you're having. Sent from my iPhoneOn Feb 28, 2018, at 09:48, Wiktor Sadowski <dsgn...@gmail.com> wrote:Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
Doesn't work on the same ip and two separate ports. Tried several times. Something is hardcoded in NGINX or openresty, maybe?On Wed, Feb 28, 2018 at 6:38 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, you cannot have two processes listening on the same ip/port. You will need to have them listen on separate IPs or ports; if you want both services to listen on port 80, you will need to do some layer 4 translation before packets arrive. On Feb 28, 2018, at 09:33, Wiktor Sadowski <dsgn...@gmail.com> wrote:Thanks, but I already know about --prefix :-) Just seems the one listening on 80 "blocks" the other one. I wasn't even able to start it. On Wed, Feb 28, 2018 at 5:56 PM, Robert Paprocki <rpaprocki@fearnothingproductions.net> wrote:Yes, this is trivial to do. Just define the '--prefix' accordingly where you want each install to live.On Wed, Feb 28, 2018 at 8:19 AM, Victor <dsgn...@gmail.com> wrote:Have someone tried to install two completely separated openresty, custom compiled, bundles on the same server? Listening on different ports, of course. .
