- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: "netstat -in" or "netstat -rn" will hang
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2003 06:43 PM
тАО11-19-2003 06:43 PM
"netstat -in" or "netstat -rn" will hang
I run "netstat -in" or "netstat -rn"
the command will hang, and no output.
mes1pdb2# dbx -k /vmunix
dbx version 5.1
Type 'help' for help.
thread 0xfffffc017fe12a80 stopped at [thread_block:3230 ,0xfffffc00004eaf00] Source not available
warning: Files compiled -g3: parameter values probably wrong
(dbx) p msginfo
struct {
msgmax = 8192
msgmnb = 16384
msgmni = 512
msgtql = 40
msg = 1635169
}
(dbx) p cur_msghdrs
40
(dbx) quit
I want ot know the reason of msg-queue will be full.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2003 10:12 PM
тАО11-19-2003 10:12 PM
Re: "netstat -in" or "netstat -rn" will hang
In your entry, I remark that you are aware of a possible netstat problem when
msgtql = cur_msghdrs
You can use the command ipcs -qa
This will show the PID of the processes holding these messagequeue's
A kill of these processes could help.
But, I think you should first investigate why this situation occurs.
I suggest also to increase the value of msgtql in /etc/sysconfigtab (in the ipc-subsystem)
A reboot will be required, as this is no dynamic parameter. %-{
Rgrds
Joris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 04:36 PM
тАО11-20-2003 04:36 PM
Re: "netstat -in" or "netstat -rn" will hang
I can't confirm PID of messages queue.
LSPID? LRPID?
use dbx to trace netstat, but no more info to analyze why the cur_msghdrs will be full.
the log file is attached.
thanks
jack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 07:17 PM
тАО11-20-2003 07:17 PM
Re: "netstat -in" or "netstat -rn" will hang
is there also a problem calling arp?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 07:18 PM
тАО11-20-2003 07:18 PM
Re: "netstat -in" or "netstat -rn" will hang
According the manpages.
LSPID (a,p)
The ID of the last process that sent a message to the associated queue.
LRPID (a,p)
The ID of the last process that received a message from the associated
queue.
QNUM (a,o)
The number of messages currently outstanding on the associated message
queue.
The second line of the messagequeues gives
q 1537 0x4c544952 --rw-rw-rw- root daemon root daemon 8320 40 16384 1504259 1341906 21:25:08 21:25:08 17:00:51
40 is the number of currently outstanding messages in the messagequeue with ID 1537
1504259 is the PID of the process that sent the last message to the messagequeue
1341906 is the PID of the last process that received a message
Joris