Finally I could execute update and rebuild without problems. But, I had to re-run all the installation process in a fresh Kali distribution and without openvas. In that case, when I tried to rebuild, I obtained the same error. But, I could fix it with a restarting of postgres services.
Next, when I see the properties at the greenbone web application, for all sections, I obtain the following error message: SCAP and/or CERT database missing on OMP server. For try to solve this problem, in several sites and posts, the instruction is: "run openvas-certdata-sync". But, when I run this command, I get the following new error: [i] Initializing CERT advisory database > psql:<stdin>:27: NOTICE: schema "cert" does not exist, skipping Any ideas? Thanks! 2015-12-29 0:12 GMT-03:00 Ryan Schulze <[email protected]>: > Hmm, I remembered seeing that error before, so I checked my notes and > found a short discussion on the openvas-dev mailing list about that error > happening on ubuntu based systems. > http://comments.gmane.org/gmane.comp.security.openvas.devel/3535 > > I never did find out why the change only broke stuff on Ubuntu systems, so > I never got around to making a real fix. But the workaround still works > fine for me (changing Requires.private back to Requires in > openvas-libraries/libopenvas_*.pc.in). Sorry for not mentioning that > problem, I had totally forgot that that patch was still in our workflow. > I'll attach the patch we use when compiling OpenVAS for our Ubuntu servers > to the email. > > > On 12/21/2015 9:14 PM, Julian wrote: > > I don't use strace frequently, but it called my attention the following > lines: > > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or >> directory) >> futex(0x7ffc33592950, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, >> NULL, 7f7afaca18c0) = -1 EAGAIN (Resource temporarily unavailable) >> statfs("/sys/fs/selinux", 0x7ffc33592920) = -1 ENOENT (No such file or >> directory) >> statfs("/selinux", 0x7ffc33592920) = -1 ENOENT (No such file or >> directory) >> open("/usr/share/zoneinfo/utc 0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No >> such file or directory) > > > Also, find attached the complete output of "strace -o strace openvas > openvasmd --rebuild". > > On the other hand, the "openvasmd.log" shows: > > md main:WARNING:2015-12-22 02h32.14 utc:2061: sql_exec_internal: SQL: >> CREATE OR REPLACE FUNCTION max_hosts (text, text) RETURNS integer AS >> '/usr/local/var/lib/openvas/openvasmd/pg/libmanage-pg-server', >> 'sql_max_hosts' LANGUAGE C; >> md main:WARNING:2015-12-22 02h32.14 utc:2061: sqlv: sql_exec_internal >> failed >> md main:WARNING:2015-12-22 02h41.58 utc:2128: sql_exec_internal: PQexec >> failed: ERROR: could not load library >> "/usr/local/var/lib/openvas/openvasmd/pg/libmanage-pg-server.so": >> /usr/local/lib/libopenvas_omp.so.8: undefined symbol: openvas_server_sendf >> (7) > > > I don't know why the library couldn't load. > > Thanks! > > 2015-12-21 23:24 GMT-03:00 Ryan Schulze <[email protected]>: > >> tasks.db is the sqlite database, so you can ignore that >> openvas-check-setup error (it currently doesn't check which backend openvas >> manager is using). Have you checked the logs to see why the --rebuild is >> failing? Or just run it with strace to see where openvas starts to complain >> (could be a permission problem)? >> >> >> On 12/20/2015 10:31 PM, Julian wrote: >> >> Hi Ryan, thanks for the quick answer! >> >> I tried to follow the "howto" and the install instructions for each >> packet. >> Finally, when I run the openvas-check-setup, I got the following result: >> >> >>> # . /openvas-check-setup --v8 >>> openvas-check-setup 2.3.3 >>> Test completeness and readiness of OpenVAS-8 >>> (add '--v6' or '--v7' or '--v9' >>> if you want to check for another OpenVAS version) >>> Please report us any non-detected problems and >>> help us to improve this check routine: >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >>> Send us the log-file (/tmp/openvas-check-setup.log) to help analyze >>> the problem. >>> Use the parameter --server to skip checks for client tools >>> like GSD and OpenVAS-CLI. >>> Step 1: Checking OpenVAS Scanner ... >>> OK: OpenVAS Scanner is present in version 5.0.4. >>> OK: OpenVAS Scanner CA Certificate is present as >>> /usr/local/var/lib/openvas/CA/cacert.pem. >>> OK: redis-server is present in version v=2.8.4. >>> OK: scanner (kb_location setting) is configured properly using >>> the redis-server socket: /tmp/redis.sock >>> OK: redis-server is running and listening on socket: >>> /tmp/redis.sock. >>> OK: redis-server configuration is OK and redis-server is running. >>> OK: NVT collection in /usr/local/var/lib/openvas/plugins >>> contains 44735 NVTs. >>> WARNING: Signature checking of NVTs is not enabled in OpenVAS >>> Scanner. >>> SUGGEST: Enable signature checking (see >>> http://www.openvas.org/trusted-nvts.html). >>> OK: The NVT cache in /usr/local/var/cache/openvas contains 44735 >>> files for 44735 NVTs. >>> Step 2: Checking OpenVAS Manager ... >>> OK: OpenVAS Manager is present in version 6.0.6. >>> OK: OpenVAS Manager client certificate is present as >>> /usr/local/var/lib/openvas/CA/clientcert.pem. >>> >>> * ERROR: No OpenVAS Manager database found. (Tried: >>> /usr/local/var/lib/openvas/mgr/tasks.db) ** FIX: Run 'openvasmd >>> --rebuild' while OpenVAS Scanner is running.* >>> ERROR: Your OpenVAS-8 installation is not yet complete! >> >> >> >> >> Then, when I tried to run the command "openvasmd --rebuild', It shows the >> following error: >> >> # openvasmd --rebuild -v --progress >>> *Rebuilding NVT cache... failed.* >> >> >> Besides, I can't find task.db file. >> >> Any ideas? >> >> Best regards. >> Julián. >> >> >> >> >> 2015-12-10 0:03 GMT-03:00 Ryan Schulze < <[email protected]> >> [email protected]>: >> >>> If you are doing a clean source install it's pretty straightforward >>> following the openvas-manager/doc/postgres-HOWTO document. You probably >>> won't find much information googling since smaller installations do fine >>> with sqlite and larger installations may not want to play around with it >>> yet since it is still work-in-progess. >>> I've never tried it on a Kali installation, but for my ubuntu servers it >>> was just "install postgresql, compile manager with postgresql support, >>> grant database permissions, activate uuid-ossp extension in postgresql, >>> make sure ld knew the path to the openvas libraries" >>> >>> Migrating existing data from sqlite to postgresql can be complicated >>> since the script doesn't work for all openvas db versions (only versions >>> 133-136 if I remember correctly). I just exported everything*) using the >>> OMP protocol from a sqlite backend manager and imported it to the >>> postgresql backend manager. >>> >>> *) "everything" in my case not including the ssh credentials (the >>> private key can't be exported via OMP, but it can be imported. so you would >>> have to extract it form the database manually if you need it). >>> >>> >>> >>> >>> >>> On 12/9/2015 11:09 AM, Julian wrote: >>> >>> Hi!, I have been trying to install openvas with postgresql support but >>> with a lot of troubles. >>> >>> I installed a fresh kali and last stable openvas from bin / from >>> sources, I applied the migration tool too but with a lot of errors. >>> >>> I can't find any guide or something googling or reviewing the mailing >>> list. >>> >>> What is the recommended tasklist to install it? Could you tell me some >>> few steps to start again? >>> Any comment will be appreciated!! >>> Best regards. >>> >>> Julian. >>> >>> >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >> > > > > _______________________________________________ > Openvas-discuss mailing > [email protected]https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
