[Bug 538183] Re: failed to bind unix socket

2010-05-16 Thread TitusX
Yes, the default config is working perfectly. But if you change in "etc/nginx/sites-available/default" line 7 simply from "listen 80 default;" to "listen unix:/var/run/nginx.socket default;", it would produce the errors above. -- failed to bind unix socket https://bugs.launchpad.net/bugs/538183 Y

[Bug 538183] Re: failed to bind unix socket

2010-03-25 Thread Daniel Hahler
TitusX, can you provide your config? I guess it's working with the default config for you? -- failed to bind unix socket https://bugs.launchpad.net/bugs/538183 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

Re: [Bug 538183] Re: failed to bind unix socket

2010-03-14 Thread Dulmandakh Sukhbaatar
Sure, start it with default configuration and check whether it work or not. If it's working, this bug would be closed. On Mar 15, 2010 1:50 AM, "TitusX" wrote: My original configuration is very complex and contains some servers with port 80. Therefore I checked this at the beginning. Then I "ext

[Bug 538183] Re: failed to bind unix socket

2010-03-14 Thread TitusX
My original configuration is very complex and contains some servers with port 80. Therefore I checked this at the beginning. Then I "extracted" the config until it onlyproduces the error and then finally - i posted it here. I guess it we had both the same idea - another good idea would be to insta

[Bug 538183] Re: failed to bind unix socket

2010-03-13 Thread Daniel Hahler
What changes in 0.7.62 and 0.7.65 are you referring to? Also, Dulmandakh may be right: do you have any "listen 80" servers, which prevent nginx from starting up, because this port is occupied already? -- failed to bind unix socket https://bugs.launchpad.net/bugs/538183 You received this bug noti

[Bug 538183] Re: failed to bind unix socket

2010-03-13 Thread Dulmandakh Sukhbaatar
please check if there is another process is listening to 80 port. use netstat -tlnp | grep 80 to see result. if another process is using this port, you need to stop it before starting nginx. -- failed to bind unix socket https://bugs.launchpad.net/bugs/538183 You received this bug notification be

[Bug 538183] Re: failed to bind unix socket

2010-03-13 Thread TitusX
Sorry I forgot - I tried following packages: 0.7.62-4ubuntu1 (karmic) 0.7.63-1ubuntu2 (old lucid package) and 0.7.65-1ubuntu2 (lucid). And you are right about the bugfixes: - Changes with nginx 0.8.29, 30 Nov 2009 - Changes with nginx 0.8.22, 03 Nov 2009 But the 0.7.x version is the stable branch

[Bug 538183] Re: failed to bind unix socket

2010-03-12 Thread Daniel Hahler
Which nginx version are you using? (try "apport-collect 538183" to attach info to this bug report) There are some things mentioned in http://nginx.org/en/CHANGES: 0.8.29: Bugfix: listen unix domain socket had limited access rights. 0.8.22: Bugfix: nginx did not delete unix domain socket after conf