Error response from daemon

[superit63]

Hi,

I have faced the issue:

when I run command to start or delete the script.
Thanks

[engageub]

Hello,
Could you please let me know which container were you trying to run.
Is this main branch or test branch.

Thank you

[engageub]

Are you able to delete it after restarting the containers. If you see dindearnapp in containernames.txt file, you are using the latest version for earnapp.

Thank you

[engageub]

If restarting and deleting the containers does not work, then follow the suggestion mentioned in docker forums to kill the zombie process.

https://forums.docker.com/t/cannot-do-a-kill-or-stop-or-anything-else-to-zombie-container/86201/2

Thank you

[superit63]

I got this error when I excute delete container:

Is it possible to run docker stop $(docker ps -aq) and docker rm $(docker ps -aq)? I have tried and it works
Thanks

[engageub]

Hello,
There are two solutions here based on the above discussion.

1. Start the containers using --init option as suggested by the docker error message.
2. Stop and Delete the containers as it was done in earlier versions. The wiki still mentions in main page that we stop and delete containers. This was taking longer time to stop and delete the containers, so docker rm -f command is being used to force delete the containers immediately.

However, it is still not clear why this is happening on your PC and not mine.
Could you please let me know which version of docker you are using and also the architecture whether it is arm64 or amd64.
I have been running earnapp for about a month and did not have problem with --delete command.

Could you please search for docker run in the code and replace all of them with docker run --init and then start the containers.
Please confirm if you are able to delete them after starting.

Thank you

[superit63]

Thanks a lot for your help. I can fix it with --init. I get these error after starting.
Another option is upgrading the hardware of machine as 1 app can consume around 100-150mb RAM

[superit63]

I have seen the logs and see that:
2024-08-19 14:24:03.478 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_02_4min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200
2024-08-19 14:24:03.513 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_02_4min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200
2024-08-19 14:25:03.009 NOTICE: idle_state_monitor run
2024-08-19 14:26:04.049 NOTICE: idle_state_monitor run
2024-08-19 14:27:05.089 NOTICE: idle_state_monitor run
2024-08-19 14:28:03.479 ERR: perr heartbeat_proxy_js_conn_03_8min {}
2024-08-19 14:28:03.480 NOTICE: perr lum_sdk_node_heartbeat_proxy_js_conn_03_8min proxy
2024-08-19 14:28:03.517 ERR: perr heartbeat_proxy_js_conn_03_8min {}
2024-08-19 14:28:03.518 NOTICE: perr lum_sdk_node_heartbeat_proxy_js_conn_03_8min proxy
2024-08-19 14:28:04.126 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_03_8min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200
2024-08-19 14:28:04.264 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_03_8min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200
2024-08-19 14:28:06.129 NOTICE: idle_state_monitor run
2024-08-19 14:29:07.169 NOTICE: idle_state_monitor run
2024-08-19 14:30:01.705 NOTICE: status_get: {"idle":true,"usage":{},"idle_state":{"mem_usage":5,"mem_usage_ts":1724077747190,"cpu_usage":0.34,"cpu_usage_ts":1724077748208},"bw":{}}
2024-08-19 14:30:01.716 NOTICE: status_get: {"idle":true,"usage":{},"idle_state":{"mem_usage":5,"mem_usage_ts":1724077747190,"cpu_usage":0.34,"cpu_usage_ts":1724077748208},"bw":{}}
2024-08-19 14:30:08.209 NOTICE: idle_state_monitor run
2024-08-19 14:31:09.249 NOTICE: idle_state_monitor run
It seems that my machine specs is not good enough. I suggest to run 100 earnapp in machine that has at least 32gb RAM to have the best performance and good earning. How do you think?

[engageub]

Thank you for response. It is not clear whether adding --init actually resolved the issue.
In addition to this, could you please elaborate what you mean by "upgrading the hardware of machine as 1 app" .
Do you mean adding all the apps into single docker image?

Thank you

[engageub]

I have seen the logs and see that: 2024-08-19 14:24:03.478 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_02_4min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200 2024-08-19 14:24:03.513 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_02_4min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200 2024-08-19 14:25:03.009 NOTICE: idle_state_monitor run 2024-08-19 14:26:04.049 NOTICE: idle_state_monitor run 2024-08-19 14:27:05.089 NOTICE: idle_state_monitor run 2024-08-19 14:28:03.479 ERR: perr heartbeat_proxy_js_conn_03_8min {} 2024-08-19 14:28:03.480 NOTICE: perr lum_sdk_node_heartbeat_proxy_js_conn_03_8min proxy 2024-08-19 14:28:03.517 ERR: perr heartbeat_proxy_js_conn_03_8min {} 2024-08-19 14:28:03.518 NOTICE: perr lum_sdk_node_heartbeat_proxy_js_conn_03_8min proxy 2024-08-19 14:28:04.126 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_03_8min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200 2024-08-19 14:28:04.264 NOTICE: perr https://perr.l-err.biz/perr?id=lum_sdk_node_heartbeat_proxy_js_conn_03_8min&appid=node_earnapp.com&ver=1.294.218&ver_sdk=1.294.218&uuid=sdk-node-cd333f8649d0e5d6513351fb57b077bc res 200 2024-08-19 14:28:06.129 NOTICE: idle_state_monitor run 2024-08-19 14:29:07.169 NOTICE: idle_state_monitor run 2024-08-19 14:30:01.705 NOTICE: status_get: {"idle":true,"usage":{},"idle_state":{"mem_usage":5,"mem_usage_ts":1724077747190,"cpu_usage":0.34,"cpu_usage_ts":1724077748208},"bw":{}} 2024-08-19 14:30:01.716 NOTICE: status_get: {"idle":true,"usage":{},"idle_state":{"mem_usage":5,"mem_usage_ts":1724077747190,"cpu_usage":0.34,"cpu_usage_ts":1724077748208},"bw":{}} 2024-08-19 14:30:08.209 NOTICE: idle_state_monitor run 2024-08-19 14:31:09.249 NOTICE: idle_state_monitor run It seems that my machine specs is not good enough. I suggest to run 100 earnapp in machine that has at least 32gb RAM to have the best performance and good earning. How do you think?

The logs show cpu usage as 0.34. Do you not see any earnings.
Also, have you checked the cpu usage using top command. Based on that you can decide the number of containers that can be run on a single machine. Make sure your network has enough bandwidth.

Thank you

[engageub]

Hello,
I would like to let you know that new options --stop and --restart have been added to the test branch.
In case you have issues with zombie process, please use --stop and then --delete .
Using --init option is creating a new process which consumes slight CPU utilization.
Ideally zombie process should not be created while using docker container.

Thank you

[engageub]

An additional option USE_DOCKER_INIT has been added to properties file to start the containers with --init option if required. It is disabled by default.
Both the solutions mentioned above have been added to the code in test branch.