Apify Discord Mirror

Updated 5 months ago

I am getting Killed

At a glance
The post describes a series of Docker container runs that are being killed, and the community members are discussing the possible reasons for this. The main points are:

The Docker container runs are being killed repeatedly, with the log showing the container being pulled, created, and started, followed by the "Killed" message. The community members suggest that this could be due to Out of Memory (OOM) issues, and recommend adding debug logs to the code to investigate where the program is being killed.

There is no explicitly marked answer, but the community members provide suggestions that the issue is likely related to memory constraints and that increasing the memory or investigating the code further may help resolve the problem.

2023-11-15T12:55:38.594Z ACTOR: Pulling Docker image of build pC2UCjbFN1XUrUq53 from repository.
2023-11-15T12:56:01.109Z ACTOR: Creating Docker container.
2023-11-15T12:56:01.685Z ACTOR: Starting Docker container.
2023-11-15T12:56:04.422Z INFO System info {"apifyVersion":"3.1.12","apifyClientVersion":"2.8.2","crawleeVersion":"3.5.8","osType":"Linux","nodeVersion":"v16.20.2"}
2023-11-15T12:56:04.549Z Killed
2023-11-15T12:56:05.403Z ACTOR: Run exited with a non-zero exit code and was restarted.
2023-11-15T12:56:05.481Z ACTOR: Pulling Docker image of build pC2UCjbFN1XUrUq53 from repository.
2023-11-15T12:56:05.555Z ACTOR: Creating Docker container.
2023-11-15T12:56:05.607Z ACTOR: Starting Docker container.
2023-11-15T12:56:07.550Z INFO System info {"apifyVersion":"3.1.12","apifyClientVersion":"2.8.2","crawleeVersion":"3.5.8","osType":"Linux","nodeVersion":"v16.20.2"}
2023-11-15T12:56:07.635Z Killed
2023-11-15T12:56:08.593Z ACTOR: Run exited with a non-zero exit code and was restarted.
2023-11-15T12:56:08.755Z ACTOR: Pulling Docker image of build pC2UCjbFN1XUrUq53 from repository.
2023-11-15T12:56:08.757Z ACTOR: Creating Docker container.
2023-11-15T12:56:08.977Z ACTOR: Starting Docker container.
2023-11-15T12:56:11.691Z INFO System info {"apifyVersion":"3.1.12","apifyClientVersion":"2.8.2","crawleeVersion":"3.5.8","osType":"Linux","nodeVersion":"v16.20.2"}
2023-11-15T12:56:11.776Z Killed
2023-11-15T12:56:11.995Z ACTOR: The Actor run was aborted by the user.


why and what are the reasons for this?
1
v
M
!
6 comments
Hello , can you please send me the run id in a private message?
I wonder, is it because OOM (Out Of Memory)
As said it could be due to OOM. Generally, I would suggest adding debug logs into the code to see, where is the program getting killed.
it kills in the middle sometimes, where it is not using 10% of memory too
Killed is memory. Increase memory or investigate the problem in your code
Add a reply
Sign up and join the conversation on Discord