Re: Cannot allocate/attach shared (1386 Views)
Reply
Occasional Advisor
Dennis_134
Posts: 23
Registered: ‎04-22-2004
Message 1 of 12 (1,386 Views)

Cannot allocate/attach shared

Backing up x2 Solaris 9 servers. The client and agents are installed all ok. when i run the backup i get the following errors

Critical] From: BDA-NET@vusno683 "vusno683 [/usr]" Time: Fri, Dec 3, 2004 10:20:02 AM
[80:1003] Cannot allocate/attach shared memory (IPC Cannot Create Shared Memory Segment
System error: [22] Invalid argument

Can anybody help me ?
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 2 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Hi dennis,
I am also facing the same problem, but i am using solari os 8 as client and data protector 5.5 version.. If you find out the solution please let me know.
Thanks in ADVANCE
Venkat
Honored Contributor
Scott McIntosh_2
Posts: 6,874
Registered: ‎08-26-2003
Message 3 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

What's vbda -version report?
Have you changed shmmax at all?

Thanks,
Scott
HP Support
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 4 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Thanks for your quick responce.

Its a solaris box running sun os 8
can you please advice to which values i have set shhmax.
And i didn't understand what is vbda -version report???
Please help me..
Thanks A lot

Venkat
Honored Contributor
Scott McIntosh_2
Posts: 6,874
Registered: ‎08-26-2003
Message 5 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

output of:
/opt/omni/lbin/vbda -version
sorry about that.

Well, one possibility is we're trying to allocate a shared memory segment larger than what shmmax allows, which is by default 1MB on Solaris.

But to know how big a segment we're trying to get, you'd have to know the block size and disk agent buffers values for the tape drive configuration in Data Protector. Go to the device, Settings tab, Advanced, Sizes tab. Is block size * disk agent buffers larger than 1MB?

Could just be a coding error, but that's why I ask for the version info.

Thanks,
Scott
HP Support
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 6 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Here is the output.
/opt/omni/lbin/vbda -version
HP OpenView Storage Data Protector A.05.50: VBDA, internal build PHSS_32840/PHSS
_32841/DPSOL_00150,
But i didn't how to know the block size and disk agent buffers values for the tape drive configuration in Data Protector.Where i have to try for device, Settings tab, Advanced, Sizes tab.

I really appreciate your quick responces.
Thanks

Venkat
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 7 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Here is the output.
/opt/omni/lbin/vbda -version
HP OpenView Storage Data Protector A.05.50: VBDA, internal build PHSS_32840/PHSS
_32841/DPSOL_00150,
But i didn't understand how to know the block size and disk agent buffers values for the tape drive configuration in Data Protector.Where i have to try for device, Settings tab, Advanced, Sizes tab.
Please guide me i am new to data protector.
I really appreciate your quick responces.
Thanks

Venkat
Honored Contributor
Scott McIntosh_2
Posts: 6,874
Registered: ‎08-26-2003
Message 8 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Go to Devices & Media. Under Devices, find the drive that the backup was using. It'll be under Drives under the library or just under Devices if a standalone drive.

Click on the drive and go to Settings, then click on Advanced and go to Sizes. Then you should see the values of interest.

Is there any additional information in the /var/opt/omni/log/debug.log on the client? Maybe additional information such as how large a shared memory segment we were trying to do a shmget on?

Thanks,
Scott
HP Support
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 9 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Hi,

Sorry for the delay

This is the error i found on client side under 09/29/var/opt/omni/log/debug.log

05 12:56:32 INET.21861.0 ["inet/inet.c /main/dp55/26":1990] A.05.50 bPHSS_32323/PHSS_32324/DPSOL_00125
mkdir /opt/omni
Command not allowed! Aborting

09/29/05 13:03:54 BDA-NET.22093.0 ["lib/ipc/ipc.c /main/dp55/dp55_fix/1":4590] A.05.50 bPHSS_32840/PHSS_32841/DPSOL_00150
[IpcAllocShmem] shmget(1783634325, 4194320, IPC_CREAT|IPC_EXCL|IPC_SHMEM_PERM) failed (err=22)

09/29/05 13:03:56 BDA-NET.22094.0 ["lib/ipc/ipc.c /main/dp55/dp55_fix/1":4590] A.05.50 bPHSS_32840/PHSS_32841/DPSOL_00150
[IpcAllocShmem] shmget(1783634325, 4194320, IPC_CREAT|IPC_EXCL|IPC_SHMEM_PERM) failed (err=22)

And the values i found on data protector side is

Block Size : 256KB
Segment Size : 2000MB
DiskAgent Buffers : 16

Thanks in advance

waitingf or your reply

Venkat
Honored Contributor
Scott McIntosh_2
Posts: 6,874
Registered: ‎08-26-2003
Message 10 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

256KB * 16 = 4MB, which is bigger than the Solaris default of shmmax of 1MB.

And we see that in the error, where 4194320 is 4194320 bytes, or 4MB:

[IpcAllocShmem] shmget(1783634325, 4194320, IPC_CREAT|IPC_EXCL|IPC_SHMEM_PERM) failed (err=22)

So you need to modify shmmax to at least 4MB:

Edit the /etc/system file and add variable:

set shmsys:shminfo_shmmax=4194320

Verify the shared memory value changes.

"grep shmsys /etc/system"

Reboot the system.
Regular Advisor
Venkat_11
Posts: 104
Registered: ‎06-12-2002
Message 11 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

Hi,

I tried to increase the shmmax by updating the /etc/system file. But after rrebooting also i observed that the values are not changing. I ran the sysdef command there its showing up the default shhmax only....
Any advice please.
THanks
Venkat
Honored Contributor
Scott McIntosh_2
Posts: 6,874
Registered: ‎08-26-2003
Message 12 of 12 (1,386 Views)

Re: Cannot allocate/attach shared

I guess it's possible you modify shmmax on Solaris 9 differently, but those instructions worked correctly on my Solaris 8 box to bump up shmmax to 256MB to run the DP cell server, and sysdef reports the 256MB modified value after reboot.

Thanks,
Scott
HP Support
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.