Re: another "bind() to 0.0.0.0:80 failed (98: Address already in use)" issue

2017-02-23 Thread sum-it
Hello Jeff, Thank you for your help. I tested your suggestion. This isn't the case. I also tested in normal debian system and this wasn't the case there either. I believe following section is the culprit. Start-stop-daemon tests if daemon was already running, however it doesn't relinquish the s

Re: another "bind() to 0.0.0.0:80 failed (98: Address already in use)" issue

2017-02-22 Thread Jeff Dyke
1:36 PM, sum-it wrote: > Hello All, > > I have another "bind() to 0.0.0.0:80 failed (98: Address already in use)" > issue. > > I am working on a minimal system including nginx only. System startup time, > and readiness time are important points. Whilte testing I figu

another "bind() to 0.0.0.0:80 failed (98: Address already in use)" issue

2017-02-22 Thread sum-it
Hello All, I have another "bind() to 0.0.0.0:80 failed (98: Address already in use)" issue. I am working on a minimal system including nginx only. System startup time, and readiness time are important points. Whilte testing I figured out sometime system boots up within 500ms and so

Re: sudden nginx hang -- restart fails, "98: Address already in use"

2014-02-06 Thread Maxim Dounin
Hello! On Thu, Feb 06, 2014 at 07:23:51AM -0500, dwirth wrote: > Thanks. I am fairly certain (?) at this point that NFS is the culprit. I had > a lot of trouble unmounting one of my NFS directories. Eventually I resorted > to rebooting, at which point it went into a permanent hang until a reboot

Re: sudden nginx hang -- restart fails, "98: Address already in use"

2014-02-06 Thread dwirth
Thanks. I am fairly certain (?) at this point that NFS is the culprit. I had a lot of trouble unmounting one of my NFS directories. Eventually I resorted to rebooting, at which point it went into a permanent hang until a reboot was forced via hypervisor. Is this particular situation, where NFS cau

Re: sudden nginx hang -- restart fails, "98: Address already in use"

2014-02-06 Thread Maxim Dounin
> > # service nginx restart > Stopping nginx:[FAILED] > Starting nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address > already in use) > nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > nginx: [emerg

Re: sudden nginx hang -- restart fails, "98: Address already in use"

2014-02-05 Thread Jonathan Matthews
nx restart > Stopping nginx:[FAILED] > Starting nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address > already in use) > nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > nginx: [emerg] bind() to 0.0.0.0:80 f

sudden nginx hang -- restart fails, "98: Address already in use"

2014-02-05 Thread dwirth
nginx: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use

Re: 98: Address already in use

2013-10-11 Thread Peleke
I have the same problem and even if I stop nginx with /etc/init.d/nginx stop it is running on Debian Wheezy: PID PPID %CPUVSZ WCHAN COMMAND 2709 1 0.0 127476 ep_pol nginx: worker process 2710 1 0.0 127716 ep_pol nginx: worker process 2711 1 0.0 127476 ep_pol nginx: worker