Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Hi all!
We're running OnLine 7.10.UD1 on AIX 4.1.2 on an RS6000-J30 with 256MB memory
and 480MB paging space. There are 15 uniface developers/users filling about
50MB of logical logs per day with a peak of 30 concurrent users.
My question: Why can't OnLine free some memory instead of just adding
more and more virtual segments?
The case:
Just lately (as always for no apparent reason, no new release or programs,...)
we are getting ugly error messages in our OnLine logfile
...
2:53:30 Checkpoint Completed: duration was 1 seconds.
12:54:51 dynamically allocated new shared memory segment (size 8388608)
12:58:35 Checkpoint Completed: duration was 4 seconds.
13:23:36 Checkpoint Completed: duration was 0 seconds.
13:28:17 shmat: [EINVAL][22]: shared memory base address illegal
13:28:17 using 0xd0000000, needs 0xffffffff
13:28:17 out of virtual shared memory
13:28:17 shmat: [EINVAL][22]: shared memory base address illegal
13:28:17 using 0xd0000000, needs 0xffffffff
13:28:17 out of virtual shared memory
...
When I saw this message today I checked with onstat -g seg and saw that
we have the following segments
id key addr size ovhd class blkused blkfree
98305 1381451777 30000000 70541312 1880 R 8607 4
98306 1381451778 40000000 30720000 1064 V 2529 1221
77827 1381451779 50000000 557056 604 M 65 3
plus seven additional virtual segments with a size of 8388608 of which
most of the space was "used". The onmode -F freed so much of the space
that one or two virtual segments would have been more than sufficient.
Is it my uniface/polyserver clients blocking the memory? Is my ONCONFIG
not appropriate? The SHMTOTAL is set to 200MB so there would be some left
in case of a unix emergency - is this smart but wrong?
SHMBASE 0x30000000 # Shared memory base address
SHMVIRTSIZE 30000 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments (Kbytes)
SHMTOTAL 200000 # Total shared memory (Kbytes). 0=>unlimited
Hints on how to track memory usage or remedy the above problem will be
accepted gratefully. Sorry for the somewhat lengthy message - PLEASE do not
include the whole thing in your reply!
TIA.
Ralph.
+-----------------------------------------------------------------------------+
| Never attribute to malice that which is adequately explained by stupidity. |
+----------------------- ralph.halter@pac.panmail.com ------------------------+
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.