[how is this zfs-related?] Matty writes: > We are running zones on a number of Solaris 10 update 3 hosts, and we > are bumping into an issue where the kernel doesn't clean up > connections after an application exits.
Are you sure? One possible cause of this sort of problem is that the application has forked, and one of the forked processes is still holding the file descriptor open. To check this, use pgrep for processes the application may have started, or pfiles to list the open files for given processes, or download and install the open source `lsof' tool to search for specific open file descriptors. > When this issue occurs, the > netstat utility doesn't show anything listening on the port the > application uses (8080 in the example below), but connections are > still listed in the ESTABLISHED state: Note that the listening descriptor is separate from the accepted descriptor(s). Thus, it's possible for one to be closed, while the other is still open. > Normally I would open a ticket with Sun when I bump into issues with > Solaris 10, but I couldn't find anything in the bug database to > indicate this was a known problem. Does anyone happen to know if this > is a known issue? I rebooted the server with the '-d' option the last > time this issue occurred, so I have a core file available if anyone is > interested in investigating the issue (assuming this is an unknown > problem). Contacting Sun's support group sounds like a good impulse, especially given that you're using Solaris 10, and that's not OpenSolaris. I don't see any problems exactly like this for U3 in the database, though. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
