Bad response from server: (0[error,tasklist]) #22
Comments
ive not seen that particular error, and btw we arent using apache, its nginx, i will keep an eye out for it |
Thank you. do we know how much ram is being allocated? Maybe done through NGINX or PHP? |
its set to 512 MB for php.ini, how many torrents have you got running?, also this issue looks interesting, again pointing at possible resource issues with ram:- |
I have about 90 torrents running. Not nearly as 5000 like that other user. I can try making those edits as well. |
Do not see an option to edit memory in the rtorrent.rc file. |
Get this from Accessing rtorrent through a VPN Terminal Debug: And this is when I access it from home Terminal Debug: 2017-04-05 18:05:02,423 DEBG 'rutorrent-script' stderr output: 2017-04-05 18:05:03,671 DEBG 'rutorrent-script' stderr output: |
can you please post your docker run command your using |
that explains it, Synology devices have issues with nginx, currently the only way around it is to turn off apparmor, you will also most likely need to load all the required kernel modules too, try stopping the container and then execute the following and then start it again:-
|
I mean it does look like a permissioning issue. Is there anything else I can try? 2017-04-06 12:16:59,152 DEBG 'rutorrent-script' stderr output: |
ok so the below is a bug in rutorrent, i dont think it causes any issues from what i can see:-
so looks like it got fixed, but its possible its not included in the latest release yet:- |
Can you add |
Not sure how to do that within the synology interface. |
Based on this forum post. I've already done this. https://forum.synology.com/enu/viewtopic.php?t=118103 |
Been getting this error. After reloading my webpage a bunch of times "sometimes" it goes away. I've read online that we might have to increase the memory in Apache? Anyone else have this issue?
This is in the rutorrent webui.
The text was updated successfully, but these errors were encountered: