connectors
connectors copied to clipboard
[Malpedia] No progress bar and crash
Hello! @SamuelHassine
Description
The connector ran for the first time after I deploy it but no progress bar is shown in the web page.
And I assure that the connector actually ran via reading the log file
And I can also prove it by find out the entities created by author "malpedia", the results show that these entities are created when I first ran the connector.
After that, the connector has never run for more than 10 days.
Environment
- OS (where OpenCTI server runs): Ubuntu Server LTS 20.04
- OpenCTI version: OpenCTI 4.5.5
- OpenCTI client: frontend
Reproducible Steps
Steps to create the smallest reproducible scenario:
- I installed the connector using docker-compose.
- I leave the MALPEDIA_AUTH_KEY empty.
Expected Output
- Every time the connector start a new work progress, there should be a progress bar in the web page, such as below:
- The progress should start every 172800 seconds as I set up in the docker-compose.yml file.
Actual Output
- No progress bar is shown even if the connector ran successfully once.
- The connector never runs again.
Additional information
At the end of the first progress, the log shows some errors:
The docker status is running:
Thanks for your help!
@rhaist Hello! Thanks for your attention. I click the "reset the connector state", nothing happens.
I change "MALPEDIA_INTERVAL_SEC" from 179200 to 216000 in the docker-compose.yml file and then deploy the container again. The connector begins to work again. I change the docker-compose.yml file only to update the container. Actually, the "MALPEDIA_INTERVAL_SEC" field does not matter.
You can see that the connector imports new data today (June 29). The last time the connector worked is on June 15.
Still no progress bars show on the web page.
@rhaist Hello! I find that the read and write operations show effective numbers when the malpedia connector runs.
Hi @Ken-Abruzz, Thanks for the detailed analysis. Much appreciated.
The Malpedia connector is from a time where the work API didn't exist yet in OpenCTI, thus no progress in the UI currently.
I am waiting for the STIX output to be finished by the Malpedia team before I work on the connector again and fix this.
I'll update this issue as soon as there's news.
Hello @rhaist . The connector doesn't start to send bundles at the frequency as the yaml file tells it. Resetting the connector doesn't work, neither does "docker restart docker_connector-urlhaus_1". I have to reboot my machine to wake up the connector.
Hey @Ken-Abruzzi
Based on your other github issue, it seems that this issue is connector independent. Try either doing a docker restart
or to entirely remove the docker container docker stop
, docker rm
and docker-compose up -d
again. Does this help?
Is the Malpedia connector or the urlhaus connector the problem in your current issue?
Regards,
@nor3th Hello! I'm sorry to make a mistake in the above comment about regarding "urlhaus". But both urlhaus and malpedia share the same problem.
Does simply doing a docker restart
or stop
as described above also help?
@rhaist any chance to have this connector updated to generate a bundle?
I still don't have an ETA from Malpedia. Try to solve this ASAP. Sorry for the inconvenience.
The problem with "no progress bar" has been explained in #479 .
And now I update the connector to version 5.0.0. The error recorded in the log is not "Failed to establish a new connection [ERRNO 111]: connection refused". The new error is "Failed to establish a new connection: [Errno -3] Try again". This error is mentioned in #467 . And it is promised to be solved in a new version.
But the timer stops when there is 157890 seconds left, and hence no new work starts.
When I reboot my computer, the connector runs again. But it is stopped by a new error:
@rhaist any update for this connector?
Malpedia wanted to do an update this week. Will update the connector right afterwards. Should not take long.
@rhaist Any news on the connector?
@Jipegien @nino-filigran @Megafredo @helene-nguyen we need a full refactor of this connector to generate STIX bundles / works instead of querying API / send stix bundles without works.
@helene-nguyen @Megafredo to do after other rework on enrichement connectors, instead of VMRay one. thanks!
@Megafredo @Jipegien, just FYI, since confidence level modifications this connector is not working anymore which makes urgent to upgrade it to STIX bundle generation.
Short story long: as the connector is trying to directly update things in the platform it crashes everytime it has an insufficent confidence level to do so...
Thanks for the information @SamuelHassine, it is currently in the roadmap, but should I change the priority of my task and focus on malpedia ?