@tmm1 I'm having a similar issue on a QNAP using channels its basically is using all the memory 25GB worth in 1 day after a restart. I have no recordings on this just TVE. Just sent logs
Please take a screenshot. Virtual ram usage is normal.
It's using 25GB of my 32GB on my Qnap, the qnap can't even operate. This just started happening. Take a screenshot of what?
Of where you see that ram usage
Ok, I reboot the Qnap so its back to normal but if it happens again I'll take a pic
Please submit diagnostics from the DVR web UI.
Just did, I also did it last night as well
The problem appears to be coming from 192.168.20.190 which is requesting XMLTV data from the DVR once every second and its having to generate huge amounts of XML in RAM
2022/02/03 05:53:44.921136 [HTTP] | 200 | 1h37m23s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:53:47.568645 [HTTP] | 200 | 1h39m3s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:54:08.572324 [HTTP] | 200 | 1h39m25s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:54:14.336482 [HTTP] | 200 | 1h37m53s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:54:30.279815 [HTTP] | 200 | 1h38m9s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:27.754156 [HTTP] | 200 | 1h40m43s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:44.610245 [HTTP] | 200 | 1h39m23s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:48.701024 [HTTP] | 200 | 1h41m4s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:48.888270 [HTTP] | 200 | 1h41m4s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:51.494276 [HTTP] | 200 | 1h39m30s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:55:59.046738 [HTTP] | 200 | 1h39m38s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:02.983696 [HTTP] | 200 | 1h41m19s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:04.056459 [HTTP] | 200 | 1h39m43s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:05.742222 [HTTP] | 200 | 1h39m45s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:08.149112 [HTTP] | 200 | 1h39m40s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:09.139412 [HTTP] | 200 | 1h39m48s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:09.534038 [HTTP] | 200 | 1h39m49s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:11.962462 [HTTP] | 200 | 1h41m28s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:12.291383 [HTTP] | 200 | 1h41m27s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:12.434738 [HTTP] | 200 | 1h41m28s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:13.059188 [HTTP] | 200 | 1h38m36s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:15.986009 [HTTP] | 200 | 1h39m55s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:16.020903 [HTTP] | 200 | 1h41m32s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:16.285514 [HTTP] | 200 | 1h39m55s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:16.377243 [HTTP] | 200 | 1h41m32s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:16.953610 [HTTP] | 200 | 1h39m56s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:18.170412 [HTTP] | 200 | 1h38m48s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:18.201564 [HTTP] | 200 | 1h39m57s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:18.689570 [HTTP] | 200 | 1h39m58s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:18.695949 [HTTP] | 200 | 1h39m58s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:19.473768 [HTTP] | 200 | 1h41m35s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.086522 [HTTP] | 200 | 1h39m59s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.303255 [HTTP] | 200 | 1h39m59s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.409841 [HTTP] | 200 | 1h41m36s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.797441 [HTTP] | 200 | 1h40m0s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.818169 [HTTP] | 200 | 1h41m37s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:20.943903 [HTTP] | 200 | 1h41m37s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:21.200687 [HTTP] | 200 | 1h40m0s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:21.436970 [HTTP] | 200 | 1h41m37s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:21.439374 [HTTP] | 200 | 1h41m37s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
2022/02/03 05:56:22.144606 [HTTP] | 200 | 1h41m37s | 192.168.20.190 | GET "/devices/ANY/guide/xmltv?duration=500000"
This just started happening in past week, let me take a look. I didnt change anything.
Its the Shield, why would it do that? And its not even on.
You must have setup some software on there to hit this particular URL
Would Tivimate do this, I dont think I have it pulling anything though
If you put that URL into tivimate, then yes.
ill check
Ok, tivimate was doing this than, weird how it just started doing this, have had that in there for months and no issues. What would you recommend I put in there than?
