Kernal memory share issue with CA ARCserve Backup

I successfuly upgraded to SLES 11 SP2 86_64, but when tried to install the CA ARCserve backup 11.5SP3, there was an issue with the kernel memory share. It keep failing because the system doesn’t have enough resourse and can not share the memory? The system’s memory is 24G and only 4G is used and there are 20G free memory?

It was working fine before I upgrade to SP2, any clue.

Thanks

Here is the error I get when I try to install CA ARCserve backup

75210752 byte shared memory segment required by LG/LK sub-systems.
1064960 byte shared memory segment required by DBMS server(s).
0 bytes is the maximum shared memory segment size.

Your system may not have sufficient resources to run Ingres as configured.

maged67 wrote:
[color=blue]

Your system may not have sufficient resources to run Ingres as
configured.[/color]

SLES11-SP2 is based on the version three kernel. Some applications may
not be compatible. Do you know if Ingres is supported running on a
version three kernel?


Kevin Boyle - Knowledge Partner
If you find this post helpful and are using the web interface,
show your appreciation and click on the star below…

@maged67: I think Kevin is on the right track here - the shared memory settings may be inadequate, but in this case this message
“0 bytes is the maximum shared memory segment size.”
wouldn’t be 0, but a lower value than requested by the installer. It probably can’t read the value under this kernel.

can you check

sysctl -a | grep -i shm

ipcs -m

to see if you have shm segments?

If so, you should try the installation with the uname26 command, which tells the application that it’s running under a 2.6 kernel. See http://www.suse.com/releasenotes/x86_64/SUSE-SLES/11-SP2/#fate-313187

here is the ipcs -m result

------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 360448 root 600 393216 2 dest
0x00000000 393217 root 600 196608 2 dest
0x00000000 425986 root 600 393216 2 dest
0x00000000 458755 root 600 196608 2 dest
0x00000000 491524 root 600 393216 2 dest
0x00000000 524293 root 600 393216 2 dest
0x00000000 557062 root 600 393216 2 dest
0x00000000 655369 root 600 196608 2 dest
0x00000000 688138 root 600 393216 2 dest

and sysctl -a | grep -i shm

kernel.shmmax = 512000000
kernel.shmall = 1152921504606846720
kernel.shmmni = 4096
vm.hugetlb_shm_group = 0

do you still recommend installing uname26?

Thanks

maged67 wrote:
[color=blue]

Your system may not have sufficient resources to run Ingres as
configured.[/color]

I thought of your post when I read this section from the Release Notes
for SUSE Linux Enterprise Server 11 Service Pack 2.
[color=blue]

4.1. Applications Not Recognizing Linux Kernel 3.0 as Valid

With SUSE Linux Enterprise 11 SP2 we introduce Linux Kernel 3.0. This
kernel is a direct successor of the Linux kernel 2.6 series, thus all
applications run without change. However, some applications or
installation programs are broken and may check for version “2.6”
literally, thus failing to accept the compatibility of our kernel.

We provide two mechanisms to encourage applications to recognize the
kernel 3.0 in SUSE Linux Enterprise 11 SP2 as a Linux kernel 2.6
compatible system:

Use the uname26 command line tool, to start a single application

in a 2.6 context. Usage is as easy as typing uname26 [PROGRAM] . More
information can be found in the manpage of “setarch”.

Some database systems and enterprise business applications expect

processes and tasks run under a specific user name (not root). The
Pluggable Authentication Modules (PAM) stack in SUSE Linux Enterprise
allows to put a user into a 2.6 context. To achieve this, please add
the username to the file /etc/security/uname26.conf . For more
information, see the manpage for “pam_unix2”. Caveat: We do not
support the “root” user to run in a 2.6 context.[/color]

Does that help?


Kevin Boyle - Knowledge Partner
If you find this post helpful and are using the web interface,
show your appreciation and click on the star below…

Yes, you can see that shared memory is allowed on your system.
uname26 ist installed by default, it’s part of the util-linux package on SP2.

Try to use it with the installer, and when it doesn’t work, you either have to experiment with the pam option, or wait for CA to release a 3.0/SP2-compatible Arcserve…

I tried to use the uname26 during the program setup but still not working. Guess I have no other choice but waiting for ARCserve to release the update.