Operating System - HP-UX
1833788 Members
2851 Online
110063 Solutions
New Discussion

Re: fbackup errors (not the same in the "search")

 
SOLVED
Go to solution
Thi Vu
Frequent Advisor

fbackup errors (not the same in the "search")

Hello everyone,

Have any one ran into this error message from fbackup (HP-UX 10.20)?

fbackup(1009): can not get the specified shared memory segment.

We have 5 servers where the other 3 are D class (no problem with fbackup) but these 2 servers that I am having the same error is 9000 model E35 and 9000 800/H20. Any help is greatly appreciate. Thank you.

Thi

3 REPLIES 3
Vincenzo Restuccia
Honored Contributor

Re: fbackup errors (not the same in the "search")

To see what shared memory segments are in use, use "ipcs".
Could be someone has grabbed some (via shmget) and not
released them (they aren't released on program termination).
A. Clay Stephenson
Acclaimed Contributor
Solution

Re: fbackup errors (not the same in the "search")

The config file may be requesting too much shared memory on these servers. Look at blocksperrecord and records in your fbackup config file. Now look at you kernel shared memory paramters. You do have shared memory enabled?

Hope some of this helps, Clay
If it ain't broke, I can fix that.
Thi Vu
Frequent Advisor

Re: fbackup errors (not the same in the "search")

When I did "ipcs -qb" - I have 2 processes running with 32768 Qbytes for 1 process and 264 Qbytes for the other. So when I went and look at the kernel parameter "Max share mem segment (byte)" is set at 67108864, does this mean that there's plenty of memory seg. available ?

For the second advise. I went and changed my blockperrecord in the config file from 2000 to 1200 -it works fine but when I went and change from 1200 to 1500 I got the same message about memory seg. I also check with the D class server the "Max share memory segment" has the same value as E35 model so shouldn't fbackup error out when I ran fbackup with blockperrecord = 14000 ? or am I comparing apple and orange in the server's classes. Any input or insight is welcome and appreciated.
Thanks.

Thi