Gpg: out of memory while allocating 8192 bytes

sradithya · January 20, 2013, 12:25pm

We are receiving the below error message when trying to encrypt or decrypt a file on AIX server :

gpg: out of memory while allocating 8192 bytes

gpg process was working for years on the server until the day we started to see this.

This same gpg encryption is working on an other AIX server in the same environment. Many options were tried including copying the gpg from the server that's working on, recycling the server etc. But the error is persisting.

This is not a problem with any one specific id or a group of id's. Any id trying to encrypt/decrypt is getting this error. Hence this is observed at a server level and not at a user or id level.

We have an other server with identical settings where it is working normally. Even restoring the file system from this server didn't help.

The server memory is just fine and is well within limits. Even trying to encrypt / decrypt an empty or a 3 record file is facing a problem, hence its irrespective of the file size or who is trying to encrypt/decrypt it.

Sample Error :

/home>touch simple1
/home >chmod 777 simple1
/home >/opt/TWWfsw/gnupg12/bin/gpg --encrypt-file simple1
You did not specify a user ID. (you may use "-r")
 
Enter the user ID.  End with an empty line: sradithya
gpg: out of  memory while allocating 8192 bytes
/home >

The issue that surprises is that it also worked for a day after the crash recovery. Its only the next day that it stopped working. There was a hardware component failure that had to be replaced. gpg encryption and decryption was working for a day after the crash recovery, but stopped working from the day after when no system changes took place.

No visible changes happened in that one day nor any new file systems were restored. The fact that it worked for a day after crash and then lost is perplexing.

Any help or suggestions on this or any clues to look out for would be of a invaluable help to me. Please post any suggestions that you may have.

Yoda · January 20, 2013, 12:59pm

Can you compare ~/.gnupg/gpg.conf between 2 environments?

sradithya · January 20, 2013, 1:02pm

Thanks for responding.

Could you please let me know where could i get the gpg.conf file , so that i can quickly compare and get back.

Yoda · January 20, 2013, 1:06pm

It should be in ~/.gnupg/gpg.conf or $HOME/.gnupg/gpg.conf

Or look for environment variable $GNUPGHOME

sradithya · January 20, 2013, 1:25pm

Hi,

Im not seeing the gpg.conf on both the servers where its working and where its not :

Server Not working :

/home/ gnupg
$ ls -a
.             ..            pubring.gpg   pubring.gpg~  random_seed   secring.gpg   trustdb.gpg
 
Server working :


/home/.gnupg >ls �a
 
$ ls -a
.             ..            pubring.gpg   pubring.gpg~  random_seed   secring.gpg   trustdb.gpg
$

Yoda · January 20, 2013, 1:28pm

Is that period (.) missing in front of directory name gnupg for server not working?

/home/ gnupg

sradithya · January 20, 2013, 1:39pm

sorry my bad...it was a typo...

it looks the same on both the servers.

---------- Post updated at 12:39 PM ---------- Previous update was at 12:30 PM ----------

We even tried re-install, restore from back ups, creating a mount to the server thats working, server recycle etc, but nothing helps.

The memory issue "gpg: out of memory while allocating 8192 bytes" doesn't indicate which component its trying to hit is having a problem.

The server looks just fine and all the functionalities are working. It has enough physical and swap/page memory.

All the file systems are thoroughly checked and have enough free memory.

Yoda · January 20, 2013, 2:07pm

That is one strange problem. Can you run truss - trace system calls and signals and see if it gives any helpful info?

truss gpg --encrypt-file simple1

sradithya · January 20, 2013, 2:45pm

Hi,

Do we need to have admin privileges to run a truss ? Im getting the below message when i try to issue a truss :

$ truss /opt/TWWfsw/bin/gpg --encrypt-file simple1
truss: 0915-015 Cannot create subject process.
wait4all: i: 0, status: 589833, pid: 12357818, created: 0

Yoda · January 20, 2013, 3:00pm

Looks like gpg is suid root and truss cannot trace suid application.

sradithya · January 20, 2013, 4:17pm

Could you please let me know if there is any other alternative in understanding and fixing this problem?

bakunin · January 20, 2013, 6:02pm

I think to remember having had this problem once. If i remember correctly it was a version problem. Check the depencies of "gpg" (these aren't too many) and maybe update.

Which version of "gpg" are you using and where do you have it from? Usually the packages from IBMs Linux-Toolbox and the Perzl-site are very good.

I hope this helps.

bakunin

sradithya · January 20, 2013, 6:38pm

/home/.gnupg >/opt/TWWfsw/bin/gpg --version
gpg (GnuPG) 1.2.3
Copyright (C) 2003 Free Software Foundation, Inc.

Hi we are using version 1.2.3.

The version isn't an actual problem here as the same version is working on an other server we have.

We tried copying from the server where its working, but it didn't help. But if i try to work on the other server, it works.

Its perplexing as to why its not working on this server alone, which in fact used to work till a week ago.

Corona688 · January 21, 2013, 10:48am

As stated above, not just version of gpg, but the version of its dependencies.

sradithya · January 22, 2013, 1:22am

Hi,

Thanks for your inputs. Could you please let us know if there are a list of known dependencies gpg and the most notable ones? We shall look out if we can narrow down to the problem.

---------- Post updated at 06:03 PM ---------- Previous update was at 02:32 PM ----------

Truss output from a server where gpg is NOT working :

/home> truss /opt/TWWfsw/bin/gpg --verbose --default-recipient-self --yes --encrypt-files sample2 > truss.out
execve("/usr/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/etc/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/ucb/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/home/adwodadm/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/bin/X11/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/datastage/adwprod_753_app/Ascential/DataStage/DSEngine/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
truss: 0915-007 Lost control of process.
gpg: using secondary key DFEEFFE instead of primary key 97SDFERF4
gpg: reading from `sample2'
gpg: writing to `sample2.gpg'
gpg: ELG-E/AES256 encrypted for: "D8C00BBB test01 (test ods)
gpg: out of memory while allocating 8192 bytes

---------- Post updated at 06:04 PM ---------- Previous update was at 06:03 PM ----------

Truss output from a server where its WORKING :

$ t-self --yes --encrypt-files sample3 > truss.out <
execve("/usr/bin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/etc/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/sbin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/ucb/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/home/adwodadm/bin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/bin/X11/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/sbin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF22C54, 0x2000FB38) argc: 7
_exit(127)

---------- Post updated 01-22-13 at 12:22 AM ---------- Previous update was 01-21-13 at 06:04 PM ----------

The gpg process is not running as a daemon on the server. Its a stand alone software which is invoked by the batch scripts (shell scripts) at scheduled times run by admin ids.
There is no centralized trustdb for all the id's. There are individual trustdbs for all the admin ids in their own home directories. The trustdbs are not expected to be corrupted and are in tact.
Please find the encryption outputs run with debug options on the server where it is working and where it isnt.

Debug output - Server where gpg is working:
$ /opt/TWWfsw/gnupg12/bin/gpg --debug-all --encrypt-file simple1
gpg: NOTE: no default option file `/home/a510373/.gnupg/options'
You did not specify a user ID. (you may use "-r")
Enter the user ID. End with an empty line: sradithya
Added 1024g/212DCF43 2013-01-18 "sradithya (Hi) <Aditya.Sr@abc.com>"
Enter the user ID. End with an empty line:
File `simple1.gpg' exists. Overwrite (y/N)? y
$ ls -lrt
-rwxrwxrwx 1 a510373 adwsup 6 Jan 20 13:41 simple1
-rw-r--r-- 1 a510373 adwsup 347 Jan 20 19:45 simple1.gpg

Debug output - Server where gpg is NOT working:

/home/a510373 >/opt/TWWfsw/gnupg12/bin/gpg --debug-all --encrypt-file simple1
gpg: NOTE: no default option file `/home/a510373/.gnupg/options'
You did not specify a user ID. (you may use "-r")
Enter the user ID. End with an empty line: sradithya
gpg: DBG: fd_cache_open (/home/a510373/.gnupg/pubring.gpg) not cached
gpg: DBG: iobuf-1.0: open `/home/a510373/.gnupg/pubring.gpg' fd=4
gpg: DBG: iobuf-1.0: underflow: req=8192
gpg: DBG: iobuf-1.0: underflow: got=1819 rc=0
gpg: DBG: parse_packet(iob=1): type=6 length=418 (search.keyring.c.963)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: free_packet() type=6
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: parse_packet(iob=1): type=13 length=37 (search.keyring.c.963)
gpg: DBG: fd_cache_open (/home/a510373/.gnupg/pubring.gpg) not cached
gpg: DBG: iobuf-2.0: open `/home/a510373/.gnupg/pubring.gpg' fd=5
gpg: DBG: iobuf-2.0: underflow: req=8192
gpg: DBG: iobuf-2.0: underflow: got=1819 rc=0
gpg: DBG: parse_packet(iob=2): type=6 length=418 (search.keyring.c.963)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: free_packet() type=6
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: fd_cache_open (/home/a510373/.gnupg/pubring.gpg) not cached
gpg: DBG: iobuf-3.0: open `/home/a510373/.gnupg/pubring.gpg' fd=6
gpg: DBG: iobuf-3.0: underflow: req=8192
gpg: DBG: iobuf-3.0: underflow: got=1819 rc=0
gpg: DBG: parse_packet(iob=3): type=6 length=418 (parse.keyring.c.382)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: parse_packet(iob=3): type=13 length=37 (parse.keyring.c.382)
gpg: DBG: parse_packet(iob=3): type=2 length=94 (parse.keyring.c.382)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: parse_packet(iob=3): type=12 length=2 (parse.keyring.c.382)
gpg: DBG: parse_packet(iob=3): type=14 length=269 (parse.keyring.c.382)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(32)
gpg: DBG: mpi_alloc_limb_space(32)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: parse_packet(iob=3): type=2 length=73 (parse.keyring.c.382)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: parse_packet(iob=3): type=12 length=2 (parse.keyring.c.382)
gpg: DBG: parse_packet(iob=3): type=6 length=418 (parse.keyring.c.382)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(160)
gpg: DBG: mpi_alloc_limb_space(160)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: mpi_alloc(1024)
gpg: DBG: mpi_alloc_limb_space(1024)
gpg: DBG: free_packet() type=6
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: mpi_free
gpg: DBG: dummy m_size called
gpg: DBG: mpi_free_limb_space of size 0
gpg: DBG: iobuf-3.0: close `file_filter(fd)'
gpg: DBG: /home/a510373/.gnupg/pubring.gpg: close fd 6
gpg: DBG: fd_cache_close (/home/a510373/.gnupg/pubring.gpg) new slot created
gpg: DBG: build_packet() type=6
gpg: out of memory while allocating 8192 bytes

Please find the truss outputs run on gpg on the server where it is working and where it isnt.
Truss output - Server where gpg is working:
$ t-self --yes --encrypt-files sample3 > truss.out <
execve("/usr/bin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/etc/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/sbin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/ucb/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/home/adwodadm/bin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/usr/bin/X11/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("/sbin/gpg", 0x2FF22C54, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF22C54, 0x2000FB38) argc: 7
_exit(127)

Truss output - Server where gpg is NOT working:
home> truss /opt/TWWfsw/bin/gpg --verbose --default-recipient-self --yes --encrypt-files sample2 > truss.out
execve("/usr/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/etc/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/ucb/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/home/adwodadm/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/bin/X11/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/datastage/adwprod_753_app/Ascential/DataStage/DSEngine/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
truss: 0915-007 Lost control of process.
gpg: using secondary key D8C00BBB instead of primary key 97DBC284
gpg: reading from `sample2'
gpg: writing to `sample2.gpg'
gpg: ELG-E/AES256 encrypted for: "D8C00BBB test01 (test ods) gpg: out of memory while allocating 8192 bytes

bakunin · January 22, 2013, 1:49am

Depending on how you installed it (a bff-file or a rpm-package) use the "lslpp"- or the "rpm"-command to list the dependencies.

I hope this helps.

bakunin

sradithya · January 22, 2013, 12:40pm

Thanks for your inputs. I wanted to consolidate some more observations below :

WRITE/EDIT OPTIONS ARE ONLY FAILING :

Trying to do an encryption :

//home> truss /opt/TWWfsw/bin/gpg --verbose --default-recipient-self --yes --encrypt-files sample2 > truss.out
execve("/usr/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/etc/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/ucb/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/home/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/usr/bin/X11/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/sbin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("/datastage/aprod_753_app/Ascential/DataStage/DSEngine/bin/gpg", 0x2FF2253C, 0x2000FB38) argc: 7
execve("./gpg", 0x2FF2253C, 0x2000FB38) argc: 7
truss: 0915-007 Lost control of process.
gpg: using secondary key D8C00BBB instead of primary key 97RGV098
gpg: reading from `sample2'
gpg: writing to `sample2.gpg'
gpg: ELG-E/AES256 encrypted for: "D8CDFRRG test01 (test ods) <adserr@abc.com>"
gpg: out of memory while allocating 8192 bytes

Please note that it is failing while trying to read the data and write it in the encrypted format.

Or when we tried editing the keys :

$ /opt/TWWfsw/bin/gpg --edit-key Joseph Johnson
gpg (GnuPG) 1.2.3; Copyright (C) 2003 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
Secret key is available.
gpg: checking the trustdb
gpg: out of memory while allocating 8192 bytes
$

READ OPERATIONS ARE SUCCEEDING :

/home/a510373 >/opt/TWWfsw/bin/gpg --list-key
/home/a510373/.gnupg/pubring.gpg
--------------------------------
pub 1024D/9FA4A9F0 2013-01-18 sradithya (Hi) <Aditya.Sr@abc.com>
sub 1024g/8CF038A9 2013-01-18
pub 1024D/45834B11 2013-01-18 sraditya (Hi) <sraditya@gmail.com>
sub 1024g/3A935DA1 2013-01-18
/home/a510373 >
/home/a510373 >/opt/TWWfsw/bin/gpg --version
gpg (GnuPG) 1.2.3
Copyright (C) 2003 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, TIGER192, SHA256
Compression: Uncompressed, ZIP, ZLIB
/home/a510373 >

Hence, the gpg is trying to use some memory for the write/edits that is currently failing. If we would be able to figure out this memory where it is temporarily trying to store data, we would be able to crack the issue.

Corona688 · January 22, 2013, 12:50pm

The question may be rather why it is trying to use this memory. Perhaps an incompatible version of a library it uses is causing a code error of some sort.