ROOTVG

AIX => Administration => Topic started by: tomacho91 on November 22, 2006, 01:54:04 PM



Title: What causes the following error message?
Post by: tomacho91 on November 22, 2006, 01:54:04 PM
 :(  Hello

ps -fea
malloc: There is not enough memory available now.

System Configuration: lcpu=2 mem=7808MB
kthr     memory             page              faults        cpu
----- ----------- ------------------------ ------------ -----------
 r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
 1  1 1225159 665409   0   0   0   0    0   0 375 5592 530  5  2 94  0
 0  0 1225409 665159   0   0   0   0    0   0 482 2895 390  2  1 97  0
 0  0 1224927 665641   0   0   0   0    0   0 525 2983 466  8  2 90  0
 0  0 1225244 665324   0   0   0   0    0   0 463 3035 341  2  2 96  0
 0  0 1226121 664447   0   0   0   0    0   0 760 4243 930  5  1 94  0
Thank


Title: Re: What causes the following error message?
Post by: Michael on November 22, 2006, 07:30:17 PM
I would check your page space settings.

If your page space is nearly full (that is allocated, probably not written), you may have an application that has the environment  variable PSALLOC set to "early".

So, please verify your paging space settings and size.

As you didnt mention your version of AIX you will need to use either vmtune, or vmo to see the current settings, and lsls -s and lsps -a to display current usage statistics.

Hope this helps.


Title: Re: What causes the following error message?
Post by: tomacho91 on November 22, 2006, 09:32:42 PM
Hello

this is what I have

lsps -a
Page Space      Physical Volume   Volume Group    Size %Used Active  Auto  Type
paging00        hdisk1            rootvg       19968MB     4     yes   yes    lv
hd6             hdisk0            rootvg         512MB    79     yes   yes    lv
lsps -s
Total Paging Space   Percent Used
      20480MB               5%
vmo -a
      memory_frames = 1998848
      pinnable_frames = 1634836
                  maxfree = 128
                   minfree = 120
              minperm% = 20
                 minperm = 384593
              maxperm% = 80
                 maxperm = 1538373
        strict_maxperm = 0
                 maxpin% = 80
                    maxpin = 1599079
              maxclient% = 80
                  lrubucket = 131072
                       defps = 1
                   nokilluid = 0
               numpsblks = 5242880
                     npskill = 40960
              npswarn = 163840
             v_pinshm = 0
pta_balance_threshold = n/a
         pagecoloring = n/a
            framesets = 2
             mempools = 1
            lgpg_size = 0
         lgpg_regions = 0
     num_spec_dataseg = 0
     spec_dataseg_int = 512
      memory_affinity = 1
            htabscale = n/a
  force_relalias_lite = 0
  relalias_percentage = 0
data_stagger_interval = 161
 large_page_heap_size = 0
    kernel_heap_psize = 4096
soft_min_lgpgs_vmpool = 0
      vmm_fork_policy = 0
      low_ps_handling = 1
      mbuf_heap_psize = 4096
     strict_maxclient = 1
       cpu_scale_memp = 8
 lru_poll_interval = 0
      lru_file_repage = 1


Title: Re: What causes the following error message?
Post by: Michael on November 23, 2006, 09:31:08 AM
it is not really useful to have two paging spaces anymore. The idea is that you dont use paging space, but use more memory.

In any case, the unequal sizes makes the allocation a bit more dificult to follow.

In your case you have plenty allocated, lsps -s states only 5% in use.

The next possible cause is that the private segment is full.

svmon -C command should help us there. Need to look at segment with Eseg id #2, to see how much space the segment still has.