Phantom event?

casper_the_ghost · February 14, 2008, 10:22pm

i get these in my error logs… what does this mean? is this serious?

2008/02/14 11:01:25 [alert] 18361#0: phantom event 0004 for closed and
removed socket 12
2008/02/14 12:04:47 [alert] 18361#0: phantom event 0004 for closed and
removed socket 13
2008/02/14 12:39:26 [alert] 18361#0: phantom event 0001 for closed and
removed socket 11

casper_the_ghost · February 15, 2008, 12:14am

On Thu, 14 Feb 2008 13:11:29 -0800
“[email protected]” [email protected] wrote:

i get these in my error logs… what does this mean? is this serious?

2008/02/14 11:01:25 [alert] 18361#0: phantom event 0004 for closed and
removed socket 12
2008/02/14 12:04:47 [alert] 18361#0: phantom event 0004 for closed and
removed socket 13
2008/02/14 12:39:26 [alert] 18361#0: phantom event 0001 for closed and
removed socket 11

See http://www.ruby-forum.com/topic/133287. Igor’s provided
configuration has worked fine.

casper_the_ghost · February 15, 2008, 1:08am

so i have to add this:

events {
devpoll_events 1;
}

will this affect the performance?

casper_the_ghost · March 18, 2009, 2:18am

Increase your tcp queue size on your operating system. Most likely your
OS is dropping older tcp sessions once it hits it’s small concurrent tcp
limit.

On solaris for example…

Default is 128, so you can obviously see why you would hit this issue
with moderate traffic.

/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q 8192
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q0 8192