Mystery solved. In my config file, I had listen instead of ip_listen...
I had to check the config file carefully many times to see the difference with the production config. Conclusion: if you see your APE binding to 255.255.255.255 instead of the intended IP, you probably have ip_listen badly written or missing. On Thursday, May 12, 2016 at 9:58:17 AM UTC+2, Nicolas wrote: > > I will try to do that. I have no clue how. But I am sure I will find a > way. > > It definitely looks as if the requested IP is already bound. > > But thinking of it, I am not sure actually, because when a port is already > used, APE displayed a message first thing saying it could not bind. Here it > does not display this message. So we are in a special case... Or maybe the > fact that it is an IP issue not a port one leads to no message when the > problem is the same. > > Speak to you later! > > Thanks for helping guys! > > > On Thursday, May 12, 2016 at 6:58:31 AM UTC+2, Pablo wrote: >> >> Check that the IP in your config file is still attached to your sever. >> Like John mentioned, the IP 255.255.255.255 is the broadcast IP. >> >> On Wed, May 11, 2016, 6:57 PM Nicolas <[email protected]> wrote: >> >>> >>> >>> On Thursday, May 12, 2016 at 12:37:49 AM UTC+2, John Kettlekey wrote: >>>> >>>> Binding to a port is per IP address. >>>> >>>> Most of the time you bind to a port on all available IP addresses at >>>> once and then you can't bind anything else to that port. >>>> >>>> But you can bind to a port on a specific IP and allow something else to >>>> bind to the same port on a different IP. >>>> >>> >>> Agreed. >>> >>> >>>> >>>> Remember that local host (127.0.0.1) counts as a separate IP so even a >>>> machine with just one real/public IP can end up with two things bound to a >>>> port; one on the real/public IP and one on the localhost interface. >>>> >>>> From the netstat output it looks like something has bound to port 80 of >>>> the real/public IP and the other process has bound to port 80 for every >>>> remaining address (255.255.255.255) which will probably just be localhost. >>>> >>>> The thing that is bound to an IP in the netstat output is the >>> production APE process (aped). This is correct. >>> The other process (aped_staging) should bind to the other IP but binds >>> to 255.255.. instead. And I wonder why... >>> >>> >>> >>> >>>> -JK >>>> >>>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "APE Project" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/ape-project?hl=en >>> --- >>> APE Project (Ajax Push Engine) >>> Official website : http://www.ape-project.org/ >>> Git Hub : http://github.com/APE-Project/ >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "APE Project" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> >> Sincerely, >> >> Pablo Tejada >> >> From Mobile >> > -- -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/ --- You received this message because you are subscribed to the Google Groups "APE Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
