search

cve-search / vulnerability-lookup

Vulnerability-Lookup facilitates quick correlation of vulnerabilities from various sources, independent of vulnerability IDs, and streamlines the management of Coordinated Vulnerability Disclosure (CVD).
https://www.vulnerability-lookup.org
GNU Affero General Public License v3.0
146 stars 16 forks source link

Redis problem #90

Open jarozamena opened 2 days ago

jarozamena commented 2 days ago

Dear developers at Circl,

We are having some issues when starting Vulnerability Lookup (we are using a RedHat 9.5, using 8GB of RAM). When we start the application (running "poetry run start"), it fails, stating that Redis port (10002) is not available. If, without doing anything else, we execute "poetry run start" again, the application actually starts without the Redis port issue. Then, after some time (it may be anything between some minutes and a few hours), the issue with the port is shown again, and Vulnerability Lookup stops working properly, as it is not able to update, although the application continues running.

What we can see is: 1.- When checking port 10002 after running "poetry run start" for the first time, it is not available. 2.- When checking port 10002 after running "poetry run start" for the second time, it is available. 3.- When the application runs for some time, when it complains that the port 10002 is not reachable, it is indeed not available.

What we would need to know is: -Have you experienced something similar? -May it be related to memory issues? -We see that the process which runs port 10002 is owned by Kvrocks, but seems to be started by Redis. Which is actually the case? Which of both open and handle the port? We do not see anything in the logs, and we will like to know what is exactly the sequence of steps that follow the different components of the Vulnerability Lookup to know which one may be stopped or failing, to try to solve the issue. -Is there any recommendation regarding memory resources?

Just in case it helps, SELinux is completely disabled, we stopped all firewalls, and the application is not running with root or sudo privileges.

Thanks a lot, and best regards.

cedricbonhomme commented 1 day ago

Hi,

We do not have experienced such issue and we are not using RedHat at all. I do not think that the issue is coming from a lack of memory, even if 8Go is a bit low nowadays. My laptop has 32Go. Anyway, kvrocks should be ready almost immediately!

adulau commented 1 day ago

Not exactly sure were this could come from.

Maybe another option would be to add a control or delay when the script is starting to check if the required daemons are running.

Rafiot commented 3 hours ago

I'll update the run_backend script, seems it doesn't includes the check to make sure the backends are running before we move forward.

On a fresh install, it shouldn't make any difference, but it would make sense anyway.