Re: Re: [Database-devel] Problem with nessus_sql 2.2.3

"the Moonspeller" <[email protected]> Mon, 06 Jun 2005 20:48:58 +0200
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
Alex, Javier

This was the first scan i launched. The database is actually empty - so is the session table-, and the "select" statement returns no record.

I applied the correction to mysql's config timeout value, and got the same message
in nessusd.messages as Alex.

HIWH you in tracking down the problem!

Best regards

--
M.

>From: Alex Campoe <[email protected]>
>To: Javier Fernandez-Sanguino <[email protected]>
>CC: the Moonspeller <[email protected]>,[email protected]
>Subject: Re: [Nessus-devel] Re: [Database-devel] Problem with nessus_sql 2.2.3
>Date: Mon, 06 Jun 2005 14:06:06 -0400
>
>Javier
>
>This is the same error I got when trying the diff back in March. The
>SELECT statement itself works just fine. I increased the timeout
>value on mysqld to no avail. Here's the only error message on
>nessus.dump:
>
>Could not realloc() a pointer of size 1279611651 !
>
>Alex
>
>Javier Fernandez-Sanguino
wrote:
>>the Moonspeller wrote:
>>
>>>
>>>When looking into nessusd.messages...
>>>
>>
>>(...)
>>
>>>[Sun Jun 5 12:36:37 2005][3272] SQL : find by name: "onyxium-gif"
>>>[Sun Jun 5 12:36:37 2005][3272] MYSQL: SELECT hostid FROM host
>>>WHERE name="onyxium-gif" : Lost connection to MySQL server during
>>>query : can't select row
>>>[Sun Jun 5 12:36:37 2005][3272] MATCHED HOSTID: [-1]
>>>
>>
>>Ummm... seems to be a problem when retrieving information from the
>>database. Can you please provide the result of running the SQL
>>query above: 'SELECT hostid FROM host WHERE name="onyxium-gif"'
>>
>>Also, it might be worth checking how the database has been changed
>>since the
scan started. Has the 'session' table been modified?
>>
>>The scan bails out because it lose a connection to the MySQL
>>server, the database code currently does not attempt to reconnect
>>in this event and that causes the abrupt en of the scan.
>>
>>If some of the tables were filled in but the code failed in this
>>change it might be due to connection timeout in the MySQL database.
>>The Nessus-SQL code does not explicitly set a timeout so you should
>>be able to handle this through MySQL's configuration file.
>>
>>Regards
>>
>>Javier
>>
>>_______________________________________________
>>Nessus-devel mailing
list
>>[email protected]
>>http://mail.nessus.org/mailman/listinfo/nessus-devel
>
>--
>-- Alex Campoe, CISSP Information Security Manager
>--
>-- Associate Director, Systems
>--
>-- Email: [email protected] Phone: (813) 974-1796
>--
>-- Academic Computing University of South Florida
>--
>-----------------------------------------------------------------------
><< smime.p7s >>

_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel