-
Notifications
You must be signed in to change notification settings - Fork 318
APIs adding torrents not responding while others work well #113
Comments
that's strange.
and I'm getting A possible place is that , if you reconfigured there are several seconds while the engine restarts, meanwhile API calls are locked. An other issue. In the 1.2.19 release I added logs before the calls to adding tasks, try and if the issue still present, paste the log as well. |
Here's systemctl log, only [NewMagnet] appeared.
I tried some other interfaces, it seems only GET /api/torrents and /api/torrent/[link] is acting good while other POST and GET APIs are not working. |
Looks like some how I added log to every try to complie the
and you will get the executable file |
Here's the log since last restart until adding new magnet. [magnet6] contains the link of ubuntu-20.04.1-legacy-server-amd64.iso
An error related to parsing saved task? |
OK I reimplemented your situation. A malformed magnet link cause the function returned without releasing the lock. I'll release a bug fix. |
APIs adding torrents (including magnet or with torrent file) not responding while other apis (like get list) works well. The binary is built with go with latest src.
Here's my auth config.
Here's my
cloud-torrent.json
I'm calling api using curl
curl "http://localhost:3378/api/magnet" -u _user:password_ --data "_magnet-link_" -m 60
and here's the response
I also setup Nginx to access the UI, no need to say these APIs are returning 504 Gateway TImeout (I have configured Cloudflare and Cf is suggesting it cannot connect to the instance upon target API), but everything else were good, I can see the torrent list added before (with 3 tasks) and left disk space.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: