-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Radarr站點無法連接 #76
Comments
看日志是站点请求错误后,Prowlarr 暂时关闭了站点,需要在 Prowlarr 重新测试通过才能使用 几点建议
|
謝謝回覆 我先看看Prowlarr的日志好了,因為我Sonarr完全沒有問題只有Radarr有,一直也找不到原因,還以為是Jproxy中間出現了問題 |
這是我Prowlarr的log 看起來沒有關閉站點? |
看起来有些站点还是偶尔会挂掉,但是看你的 radarr 是所有站点都挂了,请确保你的索引器配置正确,并且清除 JProxy 的所有缓存,不要修改默认的缓存时间 |
把日志都清空掉,有问题再把日志放上来,现在给的日志没有看到全部站点挂掉的情况,都是一两个 |
請問你的索引器配置正确是指Radarr還是Jproxy? |
所有地方都要按文档步骤设置正确,最终以 Radarr 中的地址为准 |
我查看過全部的配置了 Radarr跟Sonarr全部都一樣 Sonarr完全沒問題唯獨Radarr有問題...想不明白.. |
這是我重新啟動後的tracelog...我也找不到有任何indexer的error 但介面上就是顯示全部fail |
radarr裡我只找到一堆都是timeout的訊息;
|
这样更可能是你的网络问题,进 radarr 服务器内(docker 的话进容器内),执行 telnet / curl 命令检查网络连通性 telnet 100.73.185.136 8117 curl http://100.73.185.136:8117/radarr/prowlarr/93/api |
都查過了 從radarr/jproxy/prowlarr裡互相ping curl大家都沒有問題 沒有packet loss 如果是這條連結的話倒是能出現XML檔案沒問題 |
在radarr那邊的discord跟github都發過issue也找不到問題 |
補充一點個人的小觀察 |
我建议你先按照我的建议,用 telnet 和 curl 测试,并把测试结果截图发出来 |
或者你有QQ的话,可以加QQ群: |
那再试试这个,看看是否正常,看看用了多长时间(记得修改 apikey) curl "http://100.73.185.136:8117/radarr/prowlarr/91/api?t=movie&cat=2000,2040,2045,2060&extended=1&apikey=(removed)&offset=0&limit=100" |
從Radarr裡面試用這個指令,測試結果可以連通,但第一次比較久,需要等上大概3-4分鐘 我試過把連結裡的91改成別的號碼,一樣每次第一次測試都需要等3-4分鐘才有反應,之後重覆測試同一個號碼都是立即有反應 |
正常,因为做了缓存,第二次肯定是秒出结果的,这样测试正常的话,真的不知道啥情况了,因为我这边也没法复现这个问题 |
我嘗試了一下找Chatgpt幫忙, AI建議我用以下指令測試;
Here's a breakdown of the command: -o /dev/null: This discards the actual output of the curl command (i.e., the content of the webpage or API response). %{time_namelookup}: Time it took for DNS resolution. 然後結果出來是:
AI給的建議是; Namelookup: The DNS resolution time is negligible (0.000046 seconds), which means the domain name was quickly resolved to its corresponding IP address. Connect: It took approximately 0.04 seconds to establish a connection to the server, which is a reasonable time for initial connection setup. StartTransfer: This indicates the time taken until the first byte was received after the connection was established. It took about 69.92 seconds, which is notably long. Total: The entire request from start to finish took around 70.08 seconds. The significant delay seems to be in the "StartTransfer" time, indicating that the server took a considerable amount of time to start sending the response after the connection was established. This could be due to server-side processing, database queries, or other backend operations. Given these results, the network latency (connection setup) isn't the primary issue. Instead, the delay seems to be on the server side (possibly the service running at "http://100.73.185.136:8117/"). You might want to investigate the backend service or application to determine the cause of this delay. 不知道有沒有幫助 |
没什么帮助,还是不知道你的为什么怎么慢,正常应该几秒钟就出结果,建议你换其他索引器试试,看看是否一样耗时怎么长 |
部署环境(windows / docker)
docker
问题描述
設置好Prowlarr / Radarr / Sonarr / Jproxy,確定互相都能連通,明明Sonnar裡沒有問題,可是Radarr裡的Indexerr長期顯示不能連接通,有時候得要手動測試連接才能通,可是過一陣子又顯示無法連接
相关日志
Radarr;
Jproxy
相关截图
Radarr:
Jproxy:
Sonarr:
The text was updated successfully, but these errors were encountered: