# Nginx, solaris, eventport

**URL:** <https://www.ruby-forum.com/t/nginx-solaris-eventport/235625>\
**Category:** NGINX\
**Created:** [July 4, 2013, 8:14am UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625 "2013-07-04T08:14:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alcina](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a587f6/32.png) [@alcina](https://www.ruby-forum.com/u/alcina)\
**Post date:** [July 4, 2013, 8:14am UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625/1 "2013-07-04T08:14:15Z")

</div>

Hi.

I’m using nginx on Solaris for years. For years I’ve been experiencing  
errors when eventport is on (with /dev/poll everything is fine, but I’m  
kinda perfectionist and I want to use native solaris features).

I realize that screaming “help with eventport” is counter-productive, so  
how  
can I localize/debug my troubles to write a comprehensive error report ?  
Right now the problem looks like the inability to connect to port 80  
which  
nginx is listening on, error log on the “notice” level is silent about  
reasons of this. Restarting nginx helps. Will switching to “debug”  
loglevel  
clarify this or do I need to do something else ?

Thanks.  
Eugene.

Posted at Nginx Forum:

> **[nginx, solaris, eventport](https://forum.nginx.org/read.php?2,240568,240568#msg-240568)**
>
> Hi. I'm using nginx on Solaris for years. For years I've been experiencing errors when eventport is on (with /dev/poll everything is fine, but I'm kinda perfectionist and I want to use native solaris features). I realize that screaming "help...

---

<div class="post-metadata">

**Author:** ![drook](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@drook](https://www.ruby-forum.com/u/drook)\
**Post date:** [July 4, 2013, 8:58am UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625/2 "2013-07-04T08:58:38Z")

</div>

On Thu, Jul 04, 2013 at 02:13:38AM -0400, drook wrote:

> reasons of this. Restarting nginx helps. Will switching to “debug” loglevel  
> clarify this or do I need to do something else ?
> 
> Thanks.  
> Eugene.

> **[A debugging log](http://nginx.org/en/docs/debugging_log.html)**

> **[GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki...](https://github.com/nginxinc/nginx-wiki)**
>
> ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com

---

<div class="post-metadata">

**Author:** ![drook](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@drook](https://www.ruby-forum.com/u/drook)\
**Post date:** [July 5, 2013, 12:54am UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625/3 "2013-07-05T00:54:59Z")

</div>

Hello!

On Thu, Jul 04, 2013 at 02:13:38AM -0400, drook wrote:

> reasons of this. Restarting nginx helps. Will switching to “debug” loglevel  
> clarify this or do I need to do something else ?

There are number of known problems with eventport implementation,  
notably related to work with upstream servers. It needs  
attention.

–  
Maxim D.

> **[nginx: donation](http://nginx.org/en/donation.html)**

---

<div class="post-metadata">

**Author:** ![drook](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@drook](https://www.ruby-forum.com/u/drook)\
**Post date:** [August 1, 2013, 8:54am UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625/4 "2013-08-01T08:54:37Z")

</div>

Hi.

I finally managed to catch this situation.  
I have a log from nginx running the following config:

worker\_processes 8;  
worker\_rlimit\_nofile 16384;

error\_log /var/log/nginx/error.log debug;  
pid /var/run/nginx.pid;

events {  
worker\_connections 1024;  
use eventport;

}

It can be obtained from: [http://music.enaza.ru/error.log.bad.gz](http://music.enaza.ru/error.log.bad.gz)

Around 13:36 August, 1st, log time, nginx stopped handling web-request  
(I  
gor timeout in browser). This situation was cleared with nginx restart.

nginx version and modules information:

nginx version: nginx/1.4.1  
TLS SNI support enabled  
configure arguments: --prefix=/usr/local/nginx --with-http\_ssl\_module  
–with-debug --with-http\_realip\_module --with-http\_xslt\_module  
–with-pcre=…/pcre-8.33 --with-cc-opt=-m64 --with-ld-opt=-m64  
–with-http\_secure\_link\_module --with-pcre-opt=-m64  
–with-http\_stub\_status\_module --with-poll\_module --with-select\_module

Thanks.  
Eugene.

Posted at Nginx Forum:

> **[Re: nginx, solaris, eventport](https://forum.nginx.org/read.php?2,240568,241434#msg-241434)**
>
> Hi. I'm using nginx on Solaris for years. For years I've been experiencing errors when eventport is on (with /dev/poll everything is fine, but I'm kinda perfectionist and I want to use native solaris features). I realize that screaming "help...

---

<div class="post-metadata">

**Author:** ![drook](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a698b9/32.png) [@drook](https://www.ruby-forum.com/u/drook)\
**Post date:** [August 1, 2013, 4:48pm UTC](https://www.ruby-forum.com/t/nginx-solaris-eventport/235625/5 "2013-08-01T16:48:31Z")

</div>

I have also a cacti graph, representing the state of tcp connections for  
the  
period of the accident:

[![](https://unix.zhegan.in/files/tcp_connections.png) ](https://unix.zhegan.in/files/tcp_connections.png)

looks like handshakes were fine, but the the exchange was stalled for  
each  
stream.

Posted at Nginx Forum:

> **[Re: nginx, solaris, eventport](https://forum.nginx.org/read.php?2,240568,241466#msg-241466)**
>
> Hi. I'm using nginx on Solaris for years. For years I've been experiencing errors when eventport is on (with /dev/poll everything is fine, but I'm kinda perfectionist and I want to use native solaris features). I realize that screaming "help...