Oops, secure memory pool already initialized

yuri · October 23, 2022, 7:27am

I have same issue in ubuntu 20 but gsad service

/etc/systemd/system/gsad.service

[Service]
Type=forking
User=gvm
Group=gvm
RuntimeDirectory=gsad
RuntimeDirectoryMode=2775
PIDFile=/run/gsad/gsad.pid
ExecStart=/usr/local/sbin/gsad --listen=192.168.101.1 --port=9392

cat /var/log/gsad.log

gsad main:MESSAGE:2022-10-23 07h21.52 utc:5305: Starting GSAD version 22.04.0
gsad main:CRITICAL:2022-10-23 07h21.52 utc:5306: main: start_https_daemon failed!
gsad main:WARNING:2022-10-23 07h21.52 utc:5307: main: start_http_daemon redirect failed !
gsad main:MESSAGE:2022-10-23 07h23.22 utc:5333: Starting GSAD version 22.04.0
gsad main:CRITICAL:2022-10-23 07h23.22 utc:5334: main: start_https_daemon failed!
gsad main:WARNING:2022-10-23 07h23.22 utc:5335: main: start_http_daemon redirect failed !
gsad main:MESSAGE:2022-10-23 07h23.23 utc:5337: Starting GSAD version 22.04.0
gsad main:CRITICAL:2022-10-23 07h23.23 utc:5338: main: start_https_daemon failed!
gsad main:WARNING:2022-10-23 07h23.23 utc:5339: main: start_http_daemon redirect failed !

journalctl -xe

Oops, secure memory pool already initialized
Okt 23 15:24:54 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?) after start: Operation not permitted

systemctl start greenbone-securey-assistant

Okt 23 15:26:24 scanner systemd[1]: Starting Greenbone Security Assistant daemon (gsad)…
Okt 23 15:26:24 scanner gsad[5465]: Oops, secure memory pool already initialized
Okt 23 15:26:24 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?) after start: Operation not permitted

cfi · October 24, 2022, 9:57am

This looks like the reason for this problem and unrelated to the current discussion about the Can't open PID message.

Some notes how to solve this are e.g. available here:

yuri · October 25, 2022, 3:59am

I still have the same issue

kt 25 11:49:55 scanner systemd[1]: Reloading.
Okt 25 11:49:56 scanner sudo[6858]: pam_unix(sudo:session): session closed for user root
Okt 25 11:49:56 scanner systemd[1]: gsad.service: start operation timed out. Terminating.
Okt 25 11:49:56 scanner systemd[1]: gsad.service: Failed with result ‘timeout’.
Okt 25 11:49:56 scanner systemd[1]: Failed to start Greenbone Security Assistant daemon (gsad).
Okt 25 11:49:57 scanner systemd[1]: gsad.service: Scheduled restart job, restart counter is at 10.
Okt 25 11:49:57 scanner systemd[1]: Stopped Greenbone Security Assistant daemon (gsad).
Okt 25 11:49:57 scanner systemd[1]: Starting Greenbone Security Assistant daemon (gsad)…

sysadmin@scanner:~$ sudo systemctl start gsad
Job for gsad.service failed because a timeout was exceeded.
See “systemctl status gsad.service” and “journalctl -xe” for details.

A start job for unit gsad.service has begun execution.
–
– The job identifier is 6415.
Okt 25 11:56:00 scanner gsad[7232]: Oops, secure memory pool already initialized
Okt 25 11:56:00 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?>
Okt 25 11:57:26 scanner sudo[7301]: sysadmin : TTY=pts/0 ; PWD=/etc/systemd/system ; USER=root>
Okt 25 11:57:26 scanner sudo[7301]: pam_unix(sudo:session): session opened for user root by sy>
Okt 25 11:57:30 scanner systemd[1]: gsad.service: start operation timed out. Terminating.
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Failed with result ‘timeout’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– The unit gsad.service has entered the ‘failed’ state with result ‘timeout’.
Okt 25 11:57:30 scanner systemd[1]: Failed to start Greenbone Security Assistant daemon (gsad).
– Subject: A start job for unit gsad.service has failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A start job for unit gsad.service has finished with a failure.
–
– The job identifier is 6415 and the job result is failed.
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Scheduled restart job, restart counter is at>
– Subject: Automatic restarting of a unit has been scheduled
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– Automatic restarting of the unit gsad.service has been scheduled, as the result for
– the configured Restart= setting for the unit.
Okt 25 11:57:30 scanner systemd[1]: Stopped Greenbone Security Assistant daemon (gsad).
– Subject: A stop job for unit gsad.service has finished
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A stop job for unit gsad.service has finished.
–
– The job identifier is 6493 and the job result is done.
Okt 25 11:57:30 scanner systemd[1]: Starting Greenbone Security Assistant daemon (gsad)…
– Subject: A start job for unit gsad.service has begun execution
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu
–
– A start job for unit gsad.service has begun execution.
–
– The job identifier is 6493.
Okt 25 11:57:30 scanner gsad[7304]: Oops, secure memory pool already initialized
Okt 25 11:57:30 scanner systemd[1]: gsad.service: Can’t open PID file /run/gsad/gsad.pid (yet?>
Okt 25 11:57:41 scanner sudo[7301]: pam_unix(sudo:session): session closed for user root

yuri · October 25, 2022, 4:01am

i can open the gui and login then do some staff

but gsad doesnt work.

is it okay to ignor gsad?

yuri · October 25, 2022, 4:02am

btw i follow this guide

github.com

libellux/Libellux-Up-and-Running/blob/master/docs/openvas/config/ubuntu-20_04_GVM-22.4.0.sh

#!/bin/bash
#
# Libellux: Up and Running
# GVM 22.04 (22.4.0) installation
# Author: Fredrik Hilmersson <fredrik@libellux.com>
# Credits: https://greenbone.github.io/docs/gvm-21.04/index.html
# Description: Pre-installation test for (GVM 22.04) 21.4.0 on Ubuntu 20.04 (Focal Fossa)
# Last updated: 2022-08-09
#

# Install dependencies
sudo apt-get update && \
sudo apt-get -y upgrade && \
sudo apt-get install -y build-essential && \
sudo apt-get install -y cmake pkg-config gcc-mingw-w64 \
libgnutls28-dev libxml2-dev libssh-gcrypt-dev libunistring-dev \
libldap2-dev libgcrypt20-dev libpcap-dev libglib2.0-dev libgpgme-dev libradcli-dev libjson-glib-dev \
libksba-dev libical-dev libpq-dev libsnmp-dev libpopt-dev libnet1-dev gnupg gnutls-bin \
libmicrohttpd-dev redis-server libhiredis-dev openssh-client xsltproc nmap \
bison postgresql postgresql-server-dev-all smbclient fakeroot sshpass wget \

This file has been truncated. show original

cfi · October 25, 2022, 6:59am

AFAICT this guide is not maintained anymore (see Install GVM 21.4.2 Ubuntu 20.04 - #62 by libellux).

Please use the official install guide linked below step by step (make sure to not skip any, use the commands in separate terminals, …). By following this guide these issues shouldn’t occur.

yuri · October 25, 2022, 6:59am

thanks i will try now

yuri · October 25, 2022, 1:26pm

Thanks it’s working

something catched my eye in log
tail -f /var/log/gvm/gvmd.log

event config:MESSAGE:2022-10-25 10h02.58 UTC:21872: Scan config GaussDB Kernel V500R001C00 Security Hardening Guide (2eec8313-fee4-442a-b3c4-fa0d5dc83d61) has been created by admin
event config:MESSAGE:2022-10-25 10h02.58 UTC:21872: Scan config Host Discovery (2d3f051c-55ba-11e3-bf43-406186ea4fc5) has been created by admin
md gmp: INFO:2022-10-25 10h32.54 UTC:22584: Failed to parse client XML: Command Unavailable
md gmp: INFO:2022-10-25 10h49.34 UTC:23086: Failed to parse client XML: Command Unavailable
event user:MESSAGE:2022-10-25 10h50.04 UTC:23222: User admin_Clone_1 (9f017336-7e27-4f61-b9c6-0e841fe41780) has been created by admin
md gmp: INFO:2022-10-25 13h24.41 UTC:27001: Failed to parse client XML: Command Unavailable

is this normal?

bricks · October 28, 2022, 6:28am

Yes this error is normal, can be ignored and will be gone in the next release.