On Sat, Oct 6, 2012 at 5:07 PM, Shashwat Srivastava <
dar...@gmail.com> wrote:
> Hi Marek,
>
> Another error stack:
I replied to the traceback in this bug:
https://github.com/sockjs/sockjs-node/issues/91
It is not related to the socket problem.
Few comments:
6) maybe there is a problem with your disconnection logic? what
happens if you disable it?
8) cacti / nagios / mrtg / rrd / graphite, there are tons of charting tools,
they all require a significant investment in configuration but are
invaluable tool for ops.
9) can you provide haproxy logs?
Additionally, please send me a result of `lsof -p` for both node.js
app and haproxy
(I'm assuming haproxy speaks directly to node.js), your haproxy.cfg config, and
`netstat -p` results for both haproxy and node.js
As a final note, this what lsof FAQ says:
10.2.2 Why does /proc-based lsof report "can't identify protocol" for
some socket files?
/proc-based lsof may report:
COMMAND PID ... TYPE ... NODE NAME
pump 226 ... sock ... 309 can't identify protocol
This means that it can't identify the protocol (i.e., the
AF_* designation) being used by the open socket file. Lsof
identifies protocols by matching the node number associated
with the /proc/<PID>/fd entry to the node numbers found in
selected files of the /proc/net sub-directory. Currently
/proc-based lsof examines these protocol files:
/proc/net/ax25 (untested)
/proc/net/ipx (needs kernel patch)
/proc/net/raw
/proc/net/raw6
/proc/net/tcp
/proc/net/tcp6
/proc/net/udp
/proc/net/udp6
/proc/net/unix
If /proc-based lsof says it can't identify the protocol
for an open socket file, you may be able to identify the
protocol yourself by using grep to look for the specific
node number in the files of /proc/net -- e.g.,
$ grep <node_number> /proc/net/*
You may not be able to find the desired node number, because
not all kernel protocol modules fully support /proc/net
information.
If you find a matching node number in a /proc/net file that is
not currently being processed by lsof, contact me via e-mail at
<
a...@purdue.edu>. I'll discuss adding support to /proc-based
lsof for the protocol of the /proc/net file with you. Make
sure "lsof" appears in the "Subject:" line so my e-mail filter
won't classify your letter as Spam.
The code that matches node numbers of open IPX protocol
socket files to those in /proc/net/ipx requires Jonathan
Sergent's Linux 2.1.79 patch to /usr/src/linux/net/ipx/af_ipx.c.
The patch, suitable for input to Larry Wall's patch program,
may be found in the lsof distribution file: