>
> On Thursday 01 April 2010 22:37:35 Geoff Galitz wrote:
> > 1) In the current state, the GSA function to update the NVTs does not
> work.
> > The openvasad.log states:
> >
> > /usr/sbin/openvas-nvt-sync is not a NVT synchronization script
> >
> > What would cause this error?
> >
> > 2) When trying to view settings I get:
> >
> > Operation: List Settings
> > Status code: 500
> > Status message: Internal error
> >
> > The logs do not show anything informative. Where should I look to
> resolve
> > this?
>
> These are likely more related to openvas-administrator.
>
> A new release will be published soon.
> Apart from this, the openvasad.log might provide a clue.
>
Ok, I've included two log snippets which may help:
#1 is using the GSA to view the settings.
------------------------------------------------------------------
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: -> client:
<authenticate_response status="200" status_text="OK"/>
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: client state set: 1
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: => client 54 bytes
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: => client done
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: FD_CLIENT_READ
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: <= client
"<commands><get_settings/></commands>"
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: XML start: commands (1)
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: -> client:
<commands_response status="200" status_text="OK">
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: client state set: 3
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: XML start: get_settings
(3)
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: client state set: 15
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: XML end: get_settings
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: -> client:
<get_settings_response status="500" status_text="Internal error"/>
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: client state set: 1
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: XML end: commands
ad oap: DEBUG:2010-04-06 16h28.21 UTC:8666: -> client:
</commands_response>
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: => client 135 bytes
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: => client done
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: FD_CLIENT_READ
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: EOF reading from client.
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: Cleaning up.
ad main: DEBUG:2010-04-06 16h28.21 UTC:8666: Exiting.
------------------------------------------------------------
Here is the log segment when trying to synchronize the feed. After the GSA
fails, the administrator is dead.
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: -> client:
<authenticate_response status="200" status_text="OK"/>
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: client state set: 1
ad main: DEBUG:2010-04-06 16h29.14 UTC:8743: => client 54 bytes
ad main: DEBUG:2010-04-06 16h29.14 UTC:8743: => client done
ad main: DEBUG:2010-04-06 16h29.14 UTC:8743: FD_CLIENT_READ
ad main: DEBUG:2010-04-06 16h29.14 UTC:8743: <= client
"<commands><describe_feed/></commands>"
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: XML start: commands (1)
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: -> client:
<commands_response status="200" status_text="OK">
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: client state set: 3
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: XML start: describe_feed
(3)
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: client state set: 14
ad oap: DEBUG:2010-04-06 16h29.14 UTC:8743: XML end: describe_feed
ad main: DEBUG:2010-04-06 16h29.21 UTC:8736: Cleaning up.
ad main: DEBUG:2010-04-06 16h29.21 UTC:8736: Exiting.
ad main: DEBUG:2010-04-06 16h29.28 UTC:8743: Cleaning up.
ad main: DEBUG:2010-04-06 16h29.28 UTC:8743: Exiting.
Installed packages:
openvas-administrator-0.7.0-1.2.i586
libopenvas_base3-3.0.4-1.1.i586
libopenvas_hg3-3.0.4-1.1.i586
libopenvas_omp3-3.0.4-1.1.i586
libopenvas-devel-3.0.4-1.1.i586
openvas-manager-1.0.0.beta5-3.1.i586
libopenvas_misc3-3.0.4-1.1.i586
libopenvas_nasl3-3.0.4-1.1.i586
openvas-scanner-3.0.2-2.1.i586
greenbone-security-assistant-1.0.0.beta5-2.1.i586
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
