• Content Count

  • Joined

  • Last visited

Everything posted by Gyurci

  1. Not just you... this docker has a very frequent update. The auto updater plugin is your friend in this case, set it and forget it.
  2. There was an update for the container midnight and my server auto updated at 6am without problems, and looks like my dbengine database files are persistent now. So looks like the "delete obsolete charts files = no" setting solved the problem.
  3. Ok, I looked through the global section of the netdata config file and found this: delete obsolete charts files = yes I set this to "no" and restarted the docker. Maybe this prevent the system from deleting the cache files??? Now testing with this until the next update...
  4. @primeval_god After a day of testing this, it is not working as it should. I now have graphs back about 5hours. But I configured the dbengine cache size to 4GB and it runs from about 23hours ago, the cache file size is now about 18MB only. I added a new path to the docker container: /var/cache/netdata (container) -> /mnt/user/appdata/netdata/cache/ (host) It is working correctly, because I can see the generated dbengine files in my appdata/netdata/cache/dbengine folder. But, in the meantime there was an update to the container and I set the docker auto update to run at 6am and
  5. @primeval_god Thanks, thats very good news. I will give it a try again. edit: Looks like it is working perfectly!
  6. Hi! Is there a way to enable the dbengine? I've got the following error, if I trying to enable it: "2019-11-02 11:41:07: netdata FATAL : MAIN :RRD_MEMORY_MODE_DBENGINE is not supported in this platform. # : No such file or directory"
  7. Thanks for the reply, yes I'm using unRaid 6.7.2. I give a chance to the Auto Update Plugin and see if it helps. I do not want to upgrade to 6.8 yet, I will stay in the stable branch.
  8. Looks like most of my problems are gone. I stopped my array and then restarted it for another reason and since then there are no segfault errors in my log. The settings of transmission looks like persistent now. Only one error left: the transmission docker keeps saying that an update is available, but I can live with it... Maybe the next real update will correct this too.
  9. I'm trying to investigate the errors I mentioned earlier. In my syslog, there are these error lines about transmission: Oct 17 09:57:29 NAS kernel: transmission-da[24735]: segfault at 48 ip 000055b839ebe934 sp 00001530e6e90a48 error 4 in transmission-daemon[55b839e96000+4b000] Oct 20 13:23:35 NAS kernel: transmission-da[5810]: segfault at 48 ip 000055987f3e9934 sp 000014e5d87a2a48 error 4 in transmission-daemon[55987f3c1000+4b000] Oct 21 19:06:08 NAS kernel: transmission-da[4383]: segfault at 24000000 ip 0000557c9f39c93f sp 000014ba6191ba48 error 4 in transmission-daemon[
  10. There is no settings.json file on the flash drive. It is in the appdata/transmission folder, and if I look in that file, my settings are there, for example the ones for throttling download and upload speeds and scheduling them. I think there is not much to edit in the settings.json file, becouse my settings is already in there. And what about the update issue? It is constantly says, there is an update for the container, nevertheless I already applied the update.
  11. I am also having the same issue! And also have another issue: my settings in the transmission ui is not persistent, for example if I set a speed limit schedule, I must re-set every time when I restart the container. Please give us some help about these issues.