Sponsored Content
Operating Systems AIX How to know which process is causing the closed_wait? Post 302883240 by Yoda on Sunday 12th of January 2014 12:51:43 PM
Old 01-12-2014
You could run netstat and then run lsof with -i option:
Code:
lsof -i [ipv4/ipv6][protocol][@hostname|hostaddr][:service|port]

Check lsof manual for further reference.
 

10 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

HTML is causing problems

I have to suggest that we turn HTML back off. The problem is that angle brackets are used in code and this is causing stuff to get dropped from posts. I know that we can use the constructs that PxT mentions in this thread. But look how hard it is to educate folks about code tags and the search... (4 Replies)
Discussion started by: Perderabo
4 Replies

2. UNIX for Dummies Questions & Answers

Causing a disk to be corrupt

Hmm, how to ask this without sounding too malicious... How might one go about causing a disk corruption in OS X specifically or via the command line in UNIX in general? Doesnt matter the severity of the problem, I just want to scare the person a little, then fix the problem for them. Any... (1 Reply)
Discussion started by: Yummator
1 Replies

3. Solaris

Memory error causing reboot

Hi there I have a box that at 4pm started recieving soft errors on a DIMM, normally this is ok and we have time to swap it out. But I got the following error which caused the box to reboot NOTE: there were abount 6 or 7 normal "soft error encountered" messages before this one Nov 7... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

4. UNIX for Dummies Questions & Answers

GCC causing problems it seems.

Hi, I seem to be getting errors in relation to GCC it seems as I cant upgrade alot of pkgs until I can upgrade or use a later version of GCC. The error I get is along the lines of ( cc1: error: unrecognized command line option "-Wno-pointer-sign" *** Error code 1 ) Anyway I was wondering if... (2 Replies)
Discussion started by: Browser
2 Replies

5. Shell Programming and Scripting

Nohup causing issues

Hi folks... I really need some help soon with this issue I am having when I run my script using 'nohup'. Below is a function 'checkReturn' that my script uses to check whether other functions or tasks errored out with a non-zero exit code. function checkReturn { if ; then ... (2 Replies)
Discussion started by: ChicagoBlues
2 Replies

6. Shell Programming and Scripting

Using tee causing need for extra newlines.

I am working on capturing lines of output from a korn script that is used to import optical disks into a jukebox. The script is running on Solaris 8. Insertdiscs calls the binary named vimport which starts up and prompts for a disk to be inserted. I am able to capture output with this line below... (3 Replies)
Discussion started by: buggin
3 Replies

7. AIX

Which Process is causing Paging?

Hello On one of our systems (AIX 5) I am seeing (vmstat) paging intermittently I want to know which process is causing the paging? I understand that first I would need to find out which process is consuming most memory 1) Is that right? 2) How to find it out? 3) By googling I found... (8 Replies)
Discussion started by: Chetanz
8 Replies

8. BSD

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies

9. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies

10. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
checkrestart(1) 						  debian-goodies						   checkrestart(1)

NAME
checkrestart - check which processes need to be restarted after an upgrade SYNOPSIS
checkrestart [ -hvpa ] [ -b blacklist_file ] [ -i package_name ] DESCRIPTION
The checkrestart program tries to determine if there are processes in the system that need to be restarted after a system upgrade. This is necessary since an upgrade will usually bring new system libraries and running processes will be still using the old versions of the libraries. In stable Debian GNU/Linux systems this is typically needed to eliminate a system exposure to a vulnerability which might have been fixed by upgrading a library which that process makes use of. Consequently, checkrestart is sometimes used as an audit tool to find outdated versions of libraries in use, particularly after security upgrades. Administrators should not, however, rely on its output completely (see BUGS below). This script needs to run as root in order to obtain the information it needs for analysis. OPTIONS
-h,--help Show the program help and exit. -v,--verbose Generate detailed output. This output includes the list of all processes found using deleted files or descriptors as well as the deleted files and descriptors found. -p,--package Only process deleted files that belong to a package, ignoring deleted files which do not have an associated package in the package system. -a,--all Process all deleted files regardless of location. This makes the program analyse deleted files even if they would be discarded because they are located in locations, such as /tmp , which are known to produce false positives. It will take preceded if used simultaneously with the -p option. -b file,--blacklist=file Read a blacklist of regular expressions from file. Any files matching the patterns will be ignored. -i name,--ignore=name Ignore services that are associated to the package name provided in name. EXIT STATUS
The program will exit with error (1) if a non-root user tries to run it. Otherwise, it will always exit with error status 0. BUGS
This program might fail if the output of the lsof utility changes since it depends on it to detect which deleted files are used by pro- cesses. It might also output some false positives depending on the processes' behaviour since it does not check yet if the (deleted) files in use are really libraries. If you find a false positive in checkrestart please provide the following information when submitting a bug report: -- The output of checkrestart using the -v (verbose) option. -- The output of running the following command as root: lsof | egrep 'delete|DEL|path inode' Checkrestart is also sensitive to the kernel version in use. And might fail to work with newer (or older) versions. A rewrite to make it less dependent on lsof could improve this, however. SEE ALSO
lsof(8) AUTHOR
checkrestart was written by Matt Zimmerman for the Debian GNU/Linux distribution. COPYRIGHT AND LICENCE
Copyright (C) 2001 Matt Zimmerman <mdz@debian.org> Copyright (C) 2007,2010-2011 Javier Fernandez-Sanguino <jfs@debian.org> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. On Debian systems, a copy of the GNU General Public License may be found in /usr/share/common-licenses/GPL. debian-goodies December 19 2006 checkrestart(1)
All times are GMT -4. The time now is 11:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy