Problem with services starting and errors and errors
Posted: Mon Apr 15, 2019 9:49 am
I’ve had OpenVAS/Greenbone running on CentOS7 for about a year, but we had a problem with the server scanning to 1% and failing. This has happened a few time recently, and I saw a similar post for I believe Ubuntu last week (don't recall the URL), but after some time of troubleshooting, I decided to attempt an upgrade the app. I just found the following post which describes the same conflicts that I encountered during the upgrade last Thursday:
https://community.greenbone.net/t/updat ... on-10/2003
I downloaded the RPMs and forced the installation of the latest versions. I had problems with the openvas-setup, so I elected to remove all openvas and atomic RPMs and (using yum remove) and restart the scanner installation from scratch. Everything seemed to go through the processes OK, except when I typed “systemctl enable openvas-manager.” I got the error “Failed to execute operation: Too many levels of symbolic links.” I never could resolve this, even if I use the absolute path.
I ended up multiple times making sure all RPMs for atomic and openvas were removed and deleted any related file structure. I removed all RPMs and tried the reinstallation, and all RPMs installed without a hitch. However, I’m still getting the same error with “systemctl enable openvas-manager.” I also see the following:
Typing “systemctl |grep openvas”:
● openvas-scanner.service loaded failed failed OpenVAS Scanner
There is no openvasmd file.
Error messages in /var/log/openvas/openvassd.log last week:
[Thu Apr 11 16:56:25 2019][7604] Failed to initialize nvti cache.
[Thu Apr 11 16:57:10 2019][8080] openvassd 5.1.1 started
[Thu Apr 11 17:46:13 2019][8080] Received the Terminated signal
[Thu Apr 11 17:46:25 2019][9319] openvassd 5.1.1 started
[Thu Apr 11 18:04:22 2019][9319] Received the Terminated signal
Today, the openvassd.log file is empty.
There is no current gsad.log file.
The following is in the /var/log/messages file:
Apr 11 17:11:44 localhost systemd: Starting OpenVAS Scanner…
Apr 11 17:11:44 localhost systemd: Started OpenVAS Scanner.
Apr 11 17:11:44 localhost systemd: openvas-scanner.service: main process exited, code=exited, status=1/FAILURE
Apr 11 17:11:44 localhost systemd: Unit openvas-scanner.service entered failed state.
Apr 11 17:11:44 localhost systemd: openvas-scanner.service failed.
Apr 11 17:11:45 localhost systemd: openvas-scanner.service holdoff time over, scheduling restart.
Apr 11 17:11:45 localhost systemd: Stopped OpenVAS Scanner.
Apr 11 17:11:46 localhost systemd: Failed to start OpenVAS Scanner.
The openvassd.dump has the following repeated over and over:
(openvassd:122159): GLib-CRITICAL **: g_path_get_dirname: assertion 'file_name != NULL' failed
There used to be an “openvas-check-setup,” but I can’t find one that works with the latest version. I’m inclined to track down the earlier version, but can anyone point me in the right direction to hopefully make version 10 work? I don't mind using version 9, but I don't know the specific file names I need to use. Any assistance would be greatly appreciated. Thanks
https://community.greenbone.net/t/updat ... on-10/2003
I downloaded the RPMs and forced the installation of the latest versions. I had problems with the openvas-setup, so I elected to remove all openvas and atomic RPMs and (using yum remove) and restart the scanner installation from scratch. Everything seemed to go through the processes OK, except when I typed “systemctl enable openvas-manager.” I got the error “Failed to execute operation: Too many levels of symbolic links.” I never could resolve this, even if I use the absolute path.
I ended up multiple times making sure all RPMs for atomic and openvas were removed and deleted any related file structure. I removed all RPMs and tried the reinstallation, and all RPMs installed without a hitch. However, I’m still getting the same error with “systemctl enable openvas-manager.” I also see the following:
Typing “systemctl |grep openvas”:
● openvas-scanner.service loaded failed failed OpenVAS Scanner
There is no openvasmd file.
Error messages in /var/log/openvas/openvassd.log last week:
[Thu Apr 11 16:56:25 2019][7604] Failed to initialize nvti cache.
[Thu Apr 11 16:57:10 2019][8080] openvassd 5.1.1 started
[Thu Apr 11 17:46:13 2019][8080] Received the Terminated signal
[Thu Apr 11 17:46:25 2019][9319] openvassd 5.1.1 started
[Thu Apr 11 18:04:22 2019][9319] Received the Terminated signal
Today, the openvassd.log file is empty.
There is no current gsad.log file.
The following is in the /var/log/messages file:
Apr 11 17:11:44 localhost systemd: Starting OpenVAS Scanner…
Apr 11 17:11:44 localhost systemd: Started OpenVAS Scanner.
Apr 11 17:11:44 localhost systemd: openvas-scanner.service: main process exited, code=exited, status=1/FAILURE
Apr 11 17:11:44 localhost systemd: Unit openvas-scanner.service entered failed state.
Apr 11 17:11:44 localhost systemd: openvas-scanner.service failed.
Apr 11 17:11:45 localhost systemd: openvas-scanner.service holdoff time over, scheduling restart.
Apr 11 17:11:45 localhost systemd: Stopped OpenVAS Scanner.
Apr 11 17:11:46 localhost systemd: Failed to start OpenVAS Scanner.
The openvassd.dump has the following repeated over and over:
(openvassd:122159): GLib-CRITICAL **: g_path_get_dirname: assertion 'file_name != NULL' failed
There used to be an “openvas-check-setup,” but I can’t find one that works with the latest version. I’m inclined to track down the earlier version, but can anyone point me in the right direction to hopefully make version 10 work? I don't mind using version 9, but I don't know the specific file names I need to use. Any assistance would be greatly appreciated. Thanks