Possible issue with postgres process closing, runaways. #199
Comments
|
I believe it's related to this issue also affecting the official community containers: I installed 22.4.18 instead and it's working for now. |
|
I haven’t seen this yet, but if it is a code based problem from GB, then it’s not yet fixed in my container.
Thanks. I’ll start tracking this down. M
…-Scott
On Jul 10, 2023 at 19:24 +0200, xenago ***@***.***>, wrote:
I believe t's related to this:
greenbone/gvmd#2038
I installed 22.4.18 instead and it's working.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Just to confirm it was not upgrade related I installed a new VM and a clean copy of the image, and the same issue appeared. unrelated: immauss, Thank you so much for putting this container together. It has been super solid for me and as someone who has fought the OpenVAS install many times, the number of hours and headaches you've saved me since I've switched to your container is immeasurable. Your service to the community is most appreciated!!! |
|
@NOVACyclist Thanks! I do think this is code based. If I'm following the thred provided by @xenago correctly, this should be in gvmd 22.5.4, which I'm building now as 22.4.20-beta. Once I've tested it, I'll push all 3 archs to docker hub. -Scott |
|
Just updated the container this morning, and I am running into the same issue. It's been really solid up until now. Looking forward to getting it going again. Thanks a bunch for all of your work on this. So far, it has made running greenbone / openvas a breeze. |
|
@immauss FYI: I have had the same issue and used the 22.4.20-beta and seems to run smoothly, will let you know when I encounter something. Anyway, thanks for maintaining this project so well, Scott! |
|
@DRIgnazGortngschirl |
|
Hi! same problem here. |
|
You can use the 22.4.20-beta version as mentioned by Scott
or main release 22.4.20 version I think you can close this issue @immauss. |
|
@DRIgnazGortngschirl : thank you and sorry for the question, i've missed the 22.4.20 version tag. |
|
immauss/openvas:22.4.20 has resolved the issue. Thanks!!!!!! |
I have been using the container for a while and just updated it to :latest on Ubuntu and it seems to be spinning a lot of processes off to postgres and not closing them, leaving me in a condition where I have no sockets left to do any actual scanning. It keeps spinning off processes and then it hits the 100 connection limit and I am unable to navigate around the front-end UI, delete reports that are having errors, etc. It then runs away with all of the system resources and I am forced to kill the container. I've tried leaving the instance idle to let any background processes finish
Symptoms:
log:
==> /usr/local/var/log/gvm/gvmd.log <==
md manage:WARNING:2023-07-10 16h27.08 utc:1819: sql_open: PQconnectPoll failed
md manage:WARNING:2023-07-10 16h27.08 utc:1819: sql_open: PQerrorMessage (conn): connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: remaining connection slots are reserved for non-replication superuser connections
md manage:WARNING:2023-07-10 16h27.08 utc:1819: init_manage_open_db: sql_open failed
md manage:WARNING:2023-07-10 16h27.16 utc:1822: sql_open: PQconnectPoll failed
md manage:WARNING:2023-07-10 16h27.16 utc:1822: sql_open: PQerrorMessage (conn): connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: remaining connection slots are reserved for non-replication superuser connections
md manage:WARNING:2023-07-10 16h27.16 utc:1822: init_manage_open_db: sql_open failed
md manage:WARNING:2023-07-10 16h27.27 utc:1826: sql_open: PQconnectPoll failed
md manage:WARNING:2023-07-10 16h27.27 utc:1826: sql_open: PQerrorMessage (conn): connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: remaining connection slots are reserved for non-replication superuser connections
==> /usr/local/var/log/gvm/healthchecks.log <==
HEALTHECHECK FAILED !
These services failed
openvas
ps -ef | grep gvmd | egrep -v "post|grep"
docker-user 25218 24268 54 12:07 ? 00:03:43 gvmd -a 0.0.0.0 -p 9390 --listen-group=gvm --osp-vt-update=/var/run/ospd/ospd-openvas.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000 --
docker-user 25265 24268 53 12:07 ? 00:03:30 gvmd -a 0.0.0.0 -p 9390 --listen-group=gvm --osp-vt-update=/var/run/ospd/ospd-openvas.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000 --
docker-user 25267 24268 54 12:07 ? 00:03:34 gvmd -a 0.0.0.0 -p 9390 --listen-group=gvm --osp-vt-update=/var/run/ospd/ospd-openvas.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000 --
docker-user 25272 24268 54 12:07 ? 00:03:36 gvmd -a 0.0.0.0 -p 9390 --listen-group=gvm --osp-vt-update=/var/run/ospd/ospd-openvas.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000 --
(repeated about 100x)
ps -ef | egrep "gvm|UID" | egrep "idle|UID" | grep -v grep | cat -n
OS:
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
OpenVAS Container Versions:
Before Upgrade:
pg_gvm=v22.4.0
notus_scanner=v22.5.0
gvmd=v22.4.2
openvas=v22.6.2
openvas_smb=v22.5.0
gvm_libs=v22.5.2
openvas_scanner=v22.6.2
gsa=v22.4.1
ospd=v21.4.4
ospd_openvas=v22.5.1
python_gvm=v23.4.2
gvm_tools=v23.4.0
greenbone_feed_sync=v23.4.0
After:
pg_gvm=v22.5.1
notus_scanner=v22.5.0
gvmd=v22.5.3
openvas=v22.7.2
openvas_smb=v22.5.3
gvm_libs=v22.6.3
openvas_scanner=v22.7.2
gsa=v22.5.0
ospd=v21.4.4
ospd_openvas=v22.5.1
python_gvm=v23.5.1
gvm_tools=v23.4.0
greenbone_feed_sync=v23.6.0
The text was updated successfully, but these errors were encountered: