bug in new function "core.log.__log_into_file"

[Ali-Razmjoo]

Hello,

I was testing the framework with -t 1000 -M 1000 threads and I've seen sometimes there is a deadlock in this function. Now the framework has a small SQLite database which I used for the web interface and the API. To prevent the deadlock we must remove flock and write the logs directly to the database hosts_log table. we may use the threads for inserting them (to avoid decreasing speed) and this part of core/log.py and do it while inserting logs in the database. we may use scan_id hash for selecting the logs and create the report log file too.

# this part must move into __log_into_file
if api_flag is 0:
        info(messages(language, 171))
    hosts = []
    for log in JSON_Data:
        if log["HOST"] not in hosts:
            hosts.append(log["HOST"])
    for host in hosts:
        for sm in scan_method.rsplit(','):
            remove_old_logs(host, sm, scan_id, language, api_flag)
    if api_flag is 0:
        info(messages(language, 170))
    for log in JSON_Data:
        submit_logs_to_db(language, api_flag, log)

__log_into_file also should be renamed to __log_into_db. and locate in api.__database file.
let me know if anyone has time to work on this.

Regards.

[Ali-Razmjoo]

Hello,

Bugs fixed, #1

Regards.