hitesh920
commented
1 year ago your system is crashing due to low/poor specs the issue is with your server, not with the repo
Closed m-hoseyny closed 1 year ago
hitesh920
commented
1 year ago your system is crashing due to low/poor specs the issue is with your server, not with the repo
m-hoseyny
commented
1 year ago Thanks for your reply.
I believe it is not. I added a little sleep before download = (await sync_to_async(aria2.add, link, a2c_opt))[0] in aria2.downloader.py and also disabled sendStatusMessage when it comes updating the status message a lot in a little time interval and the problem has been solved.
FYI. I have been using the sync old parent repo for more than 1.5 years. So, I am aware of the structure of the code.
anasty17
commented
1 year ago This from creating new thread... i will do it from one thread after repo install. But also ur server has low specifications
m-hoseyny
commented
1 year ago I think it comes from Aria2. Sometimes my uploads stuck with Aria2 too. Yes, my server config is low. But the container must not get an error with 4 forwarded leech commands.
Namlee123
commented
1 year ago Hi @m-hoseyny maybe as you said, the problem is not related to low profile. I also had the same problem a while back, when using aria2 running multiple tasks (10-15 tasks) I even created a discussion on Anasty's original repo about "start.sh killer python -m bot". I handled it by restricting "sendStatusMessage". and it was error free.
anasty17
commented
1 year ago I think it comes from Aria2. Sometimes my uploads stuck with Aria2 too. Yes, my server config is low. But the container must not get an error with 4 forwarded leech commands.
Not related to aria2c
anasty17
commented
1 year ago Hi @m-hoseyny maybe as you said, the problem is not related to low profile. I also had the same problem a while back, when using aria2 running multiple tasks (10-15 tasks) I even created a discussion on Anasty's original repo about "start.sh killer python -m bot". I handled it by restricting "sendStatusMessage". and it was error free.
It's related to profile! And i should take this in consideration why both of u assuming! I have added 100 torrent together with multi task and no issues because my vps is from oracle
m-hoseyny
commented
1 year ago Thanks for your reply.
After my edit on code, I did not get the error anymore. I got what I wanted in my small server. Please check it with the leech command and aria2. I didn't get any error with qbittorrent either.
anasty17
commented
1 year ago Thanks for your reply.
After my edit on code, I did not get the error anymore. I got what I wanted in my small server. Please check it with the leech command and aria2. I didn't get any error with qbittorrent either.
What u edit in repo ? SendStatusMessage on each task or the interval status update?
m-hoseyny
commented
1 year ago Actually, I changed two parts of the code:
SendStatusMessage to get many updates in small intervals (delete the old status message and send it again when leech or qleech sent.)download = (await sync_to_async(aria2.add, link, a2c_opt))[0] in aria2.downloader.py (I mentioned them before.)I didn't put further effort into finding out which one was effective. Telegram is very sensitive in updating and deleting messages and is very very slow in doing these actions (of course you know it better than me)
anasty17
commented
1 year ago Actually, I changed two parts of the code:
- Restrict
SendStatusMessageto get many updates in small intervals (delete the old status message and send it again whenleechorqleechsent.)- Add a little sleep before
download = (await sync_to_async(aria2.add, link, a2c_opt))[0]inaria2.downloader.py(I mentioned them before.)I didn't put further effort into finding out which one was effective. Telegram is very sensitive in updating and deleting messages and is very very slow in doing these actions (of course you know it better than me)
Well it's very fast in my tests even when i abuse all related to thread create
m-hoseyny
commented
1 year ago Humm.. well I think you can close the issue. I solved my problem on small server. Because it is on my business costs to get better server. This conversation will remain for other people with the same problem.
PS I checked the project with Hetzner Arm64 4 core cpu and 8 gb ram and still got the error.
anasty17
commented
1 year ago Humm.. well I think you can close the issue. I solved my problem on small server. Because it is on my business costs to get better server. This conversation will remain for other people with the same problem.
PS I checked the project with Hetzner Arm64 4 core cpu and 8 gb ram and still got the error.
No I'm waiting repo to be reinstalled. Then will push fix for it and want u to test it because i can't produce this error
anasty17
commented
1 year ago I have pushed commit mostly will fix the issue. @junedkh i have created only 1 extra thread for all blocking functions with 1000 worker it's not good idea to add this number but we need unlimited tasks 😂
Namlee123
commented
1 year ago I think: the problem is in compatibility with vps, because of some restrictions of the provider, they are always limited to users in some regions. Or some restriction that they don't publish according to the laws of their country. Like some software or games, it runs high on Nvidia discrete cards but not necessarily works well on Radeon cards.
The repo is deployed and tested on oracle vps, that's an advantage for oracle users, of course there will be a better vps provider, but not sure to run this repo well. This is just my personal opinion.
hitesh920
commented
1 year ago The repo is deployed and tested on oracle vps, that's an advantage for oracle users
"The repo is deployed and tested on oracle vps, that's an advantage for oracle users" bro you are stupid, thats not how this thing works
"This is just my personal opinion" no one asked you for a openion ok?
anasty17
commented
1 year ago I think: the problem is in compatibility with vps, because of some restrictions of the provider, they are always limited to users in some regions. Or some restriction that they don't publish according to the laws of their country. Like some software or games, it runs high on Nvidia discrete cards but not necessarily works well on Radeon cards.
The repo is deployed and tested on oracle vps, that's an advantage for oracle users, of course there will be a better vps provider, but not sure to run this repo well. This is just my personal opinion.
Bruh i asked u to test after the commit! Did u tested it ? And if yes, what is the result ? What vps compatability? Explain to me this new thing!!
hitesh920
commented
1 year ago I think: the problem is in compatibility with vps, because of some restrictions of the provider, they are always limited to users in some regions. Or some restriction that they don't publish according to the laws of their country. Like some software or games, it runs high on Nvidia discrete cards but not necessarily works well on Radeon cards. The repo is deployed and tested on oracle vps, that's an advantage for oracle users, of course there will be a better vps provider, but not sure to run this repo well. This is just my personal opinion.
Bruh i asked u to test after the commit! Did u tested it ? And if yes, what is the result ? What vps compatability? Explain to me this new thing!!
thats a diffrent guy xD
anasty17
commented
1 year ago I think: the problem is in compatibility with vps, because of some restrictions of the provider, they are always limited to users in some regions. Or some restriction that they don't publish according to the laws of their country. Like some software or games, it runs high on Nvidia discrete cards but not necessarily works well on Radeon cards. The repo is deployed and tested on oracle vps, that's an advantage for oracle users, of course there will be a better vps provider, but not sure to run this repo well. This is just my personal opinion.
Bruh i asked u to test after the commit! Did u tested it ? And if yes, what is the result ? What vps compatability? Explain to me this new thing!!
thats a diffrent guy xD
Ohh, @m-hoseyny
Hi,
I wanna use your project; however, when the bot gets more than 3 forwarded messages to start the leeching, the container stops, and I get these errors in my docker logs.
Could you please help me to solve this problem? This problem exists in the parent repo (anasty17) too.
I searched and increased
ulimiton the hosted machine, but the problem still exists.System Info: Intel(R) Xeon(R) CPU E5-2699C v4 @ 2.20GHz CPU family: 6 Model: 79 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping: 1 BogoMIPS: 4394.86
Ram 2 GB Storage 30 Gb (SSD) OS: Ubuntu 22.04 LTS (Jammy Jellyfish)