Sponsored Content
Operating Systems AIX Vmstat fault section all values are 0 Post 302770336 by MichaelFelt on Friday 15th of February 2013 09:25:12 AM
Old 02-15-2013
IMHO, this is not normal behavior. My first guess would be that a program has been restored, or a patch applied, and the libC and/or other shared library is not correct.

If I was on site and could look at other things I would recommend many other things - but for now, to remove many many variables in a short amount of time - AND to know if it is spurious or continous I would look at performing a reboot.

BUT!!! The other common cause of issues with libraries going bad, because they are cached in memory is either a disk gone bad (e.g. rootvg) so programs "run" but are in accurate because they cannot get/write to disk (e.g., a partition can run for hours even though it's rootvg is missing (VIOS is offline by accident) - or - that someone has done "rm -rf /..." by accident. So files are removed, but still open (shared libraries) so programs can still run "some".

Program to check: errpt

Code:
errpt | head

re: PID values. The long PID values imply that the 64-bit kernel is active so larger PID and TID values are normal

Code:
errpt -a | more

Code:
 
errpt -c

If you think the system will survive a reboot, and you can get a window to perform it - it is a serious option. But be careful - if your disk is bad and you cannot (re)boot you must decide beforehand what is worse: no availability or degraded integrity.

---------- Post updated at 04:25 PM ---------- Previous update was at 04:22 PM ----------

re: PID values. The 7-digit values imply that a 64-bit kernel is active.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

reset values for vmstat

How do you reset the values that vmstat displays? Vmstat displays a running average from the last the system was restarted on the first line, how do you reset these values without restarting the system? (Solaris 8) (3 Replies)
Discussion started by: kuczerp
3 Replies

2. UNIX for Dummies Questions & Answers

vmstat

When I exeute vmstat (e.g. vmstat 30 2), in some machines I get some wierd result as the first line. like: -117% or 208% for CPU idle percentage. But the second line is alright. Could someone explain this please. Thanks ! Chaadana (4 Replies)
Discussion started by: chaandana
4 Replies

3. UNIX for Dummies Questions & Answers

vmstat

Hi I wanted to collect data by using vmstat -I 60 >xxxx.txt & using my own account It was stopped by it self after 2 hours try again same result We want to collect day date by succession how to collect data using vmstat for day Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies

4. Linux

vmstat help

Hi everyone, I need to see some VM manager performance/behavior information on some Linux boxes regarding pages scanned/activation of the paging algorithm in order to get an idea if a given server needs more memory and is actually paging. In Aix servers, by using the vmstat cmd you... (1 Reply)
Discussion started by: jcpetela
1 Replies

5. Shell Programming and Scripting

Extract section of file based on word in section

I have a list of Servers in no particular order as follows: virtualMachines="IIBSBS IIBVICDMS01 IIBVICMA01"And I am generating some output from a pre-existing script that gives me the following (this is a sample output selection). 9/17/2010 8:00:05 PM: Normal backup using VDRBACKUPS... (2 Replies)
Discussion started by: jelloir
2 Replies

6. AIX

fr and sr (from vmstat output) values are very high

Hi AIX Expert, the fr (page freed/page replacement) and sr (pages scanned by page-replacement algorithm) values from the vmstat output (see below please) are very high. I usually see this high value during the oracle database backup. In addition, the page scan/page steal/ page faults values... (7 Replies)
Discussion started by: Beginer0705
7 Replies

7. Shell Programming and Scripting

Prepend first line of section to each line until the next section header

I have searched in a variety of ways in a variety of places but have come up empty. I would like to prepend a portion of a section header to each following line until the next section header. I have been using sed for most things up until now but I'd go for a solution in just about anything--... (7 Replies)
Discussion started by: pagrus
7 Replies

8. Programming

Using gdb, ignore beginning segmentation fault until reproduce environment segmentation fault

I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this : i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies

9. Linux

Vmstat

I m checking idle time using vmstat, below are the results var=$(ssh wmtmgr@$hostname vmstat | tail -1 | awk '{print $15}') 89 and now im subtracting 89 with 100 & im getting expected results expr 100 - $var 11 Now How can I get the result 11 in one line code? (4 Replies)
Discussion started by: sam@sam
4 Replies

10. Programming

C. To segmentation fault or not to segmentation fault, that is the question.

Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1... I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one. Below are two very condensed snippets of which I have added the results inside the each code section. IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
process_id_max(5)						File Formats Manual						 process_id_max(5)

NAME
process_id_max - limit the maximum value for process IDs (PIDs) VALUES
Failsafe Default Minimum Maximum must be greater than or equal to If the difference between and inclusive is less than is effectively limited to this difference. DESCRIPTION
The tunable allows the administrator to select a potential value range for process IDs (PIDs) as generated by (see fork(2)). It allows the administrator to select a balance between compatibility, capacity, and aesthetics. Warning: Some programs cannot tolerate PID values up to the maximum. If such programs exist and are critical, the maximum PID should be appropriately constrained. For more details on these concerns, see below. Who is Expected to Change This Tunable? Anyone. Restrictions on Changing Do not increase the maximum PID if there are critical applications which assume that PIDs fit into a restricted range. (See below). The value of can be increased at any time, and it takes effect immediately. (However, its effect may not be noticed until a sufficient number of new processes have been created to cause the system to utilize the available higher values.) A decrease in the value of also takes effect immediately. However any existing processes with PIDs that are higher than the new value are not affected. The decrease will be in full effect for all processes only after a reboot. When Should the Value of This Tunable Be Raised? Increase the maximum PID if the range of PIDs defined by the and tunables needs to be increased to allow the creation of more simultaneous processes. See nproc(5) for limits on the number of processes. Increase the maximum PID in systems which have many active processes (for example, >25,000). The larger range may increase the efficiency of creating of new processes (because it may take less work to find available PIDs). If it is desired to validate that software programs execute properly in environments where PID values may be large, increase the tunable along with the tunable to force all new process IDs to take on large values. (See process_id_min(5) for more information.) Do not increase the maximum PID if there are critical applications which assume that PIDs fit into a restricted range. (See below.) What are the Side Effects of Raising the Value? If the difference between and tunables is less than the number of processes allowed to exist simultaneously is limited to that difference. When Should the Value of This Tunable Be Lowered? Lower the maximum PID if critical applications make assumptions that the PID range is restricted. What are the Side Effects of Lowering the Value? If the difference between and tunables is less than the number of processes allowed to exist simultaneously is limited to that difference. What Other Tunable Values Should Be Changed at the Same Time? It may be desirable to change For program development and validation, a change in the tunable may also be needed. Potential Application Issues The range of PID values has, in the past, been restricted to 0..30,000. Some programs have built-in assumptions about this range. This section briefly describes some of those assumptions. Some application programs have a built-in assumption that a PID does not exceed 30,000 (which was the old value of the (undocumented) and constants). They could fail if PIDs exceed this maximum. Some application programs store PIDs in 16-bit variables (type in C). Such programs could fail if the maximum PID exceeds 32,767. Some programs provide output formats which can be sensitive to the number of digits in the PID. Such programs may produce aesthetically displeasing output if PIDs exceed 5 digits (exceed 99,999). In some cases automatic expansion of output fields can disturb column align- ment. In some other cases, adjacent fields could run together, making the output incomprehensible. Some programs or scripts parse the outputs of other programs which contain PID values. Some such programs have built-in assumptions that a PID will not exceed five character positions. Such a program could fail if the range exceeds 99,999. Because session IDs (SIDs) and process group IDs (PGIDs) are the same as the process ID of the session or group leader, an increase in the maximum PID also increases the maximum SID and PGID. Though much less likely, the same application issues may exist for SIDs and PGIDs. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. The HP-UX kernel may silently round the selected values for and/or (e.g., to the nearest power of 2) in order to accommodate the PID gener- ation algorithm. Do not increase the maximum PID if there are critical applications which assume that PIDs fit into a restricted range. See the previous section, for more details on such programmatic assumptions. The default maximum (30,000) has been selected to provide compatibility with all such programs. This value should be used if program sensitivity to larger PID values is unknown. See process_id_min(5) for informa- tion about how large PID values can be selected for software validation purposes. Increasing the PID range does not increase the maximum number of processes in the system. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
fork(2), nproc(5), process_id_min(5). whitepaper, available on Tunable Kernel Parameters process_id_max(5)
All times are GMT -4. The time now is 01:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy