Oops, secure memory pool already initialized" message

This document (7018609) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

Situation

Seeing "Oops, secure memory pool already initialized" messages.

See them with ifup and ifdown and gpg commands. The commands are working correctly.

localhost:~ # ifup eth3
Oops, secure memory pool already initialized
eth3            up

gpg --list-keys
localhost:~ # gpg --list-keys
Oops, secure memory pool already initialized
/root/.gnupg/pubring.gpg
------------------------
pub   2048R/39DB7C82 2013-01-31 [expired: 2017-01-30]
uid       [ expired] SuSE Package Signing Key <build@suse.de>

pub   2048R/50A3DD1C 2013-01-14 [expired: 2017-01-13]
uid       [ expired] SuSE Package Signing Key (reserve key) <build@suse.de>

note: random_seed file not updated
localhost:~ #

/var/log/messages shows nothing when this happens, dmesg shows nothing.
When I give the "debug" option to ifdown you first see the oops message then it goes into wicked debug information.

Resolution

This message comes from libgcrypt and is not a concern.

It's merely an indication that a call was made to initialize the secure
memory pool and it had already been initialized.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.