Jokerigno

Members
  • Posts

    180
  • Joined

  • Last visited

Everything posted by Jokerigno

  1. For me having it working should be enough
  2. I would say a 40-50%. I noticed that the MQTT settings for user and pass are uncorrect it is not present (even if my overall cpu is more intense with this new release. I'm thinking to dowgrade.
  3. I rebuild the container and found a new template. In this one there are not variable as reflesh and cache. Look:
  4. If I have a backup of the flash drive there’s some shortcut? Inviato dal mio iPhone utilizzando Tapatalk
  5. Because I have problem with dockers and VM. They absorb much more cpu that stays at 100% all the time. I hoped that 6.9.1 would solve this but nothing. I rebuild some docker and the only vm but nothing. Moreover the vm needs more time to startup. Inviato dal mio iPhone utilizzando Tapatalk
  6. Hi, what is the safest and best way to downgrade? I searched in wiki but didn't find anything. TY
  7. Hi, I updated to 6.9.1 and noticed that when container is on I have a more intense CPU use. Look below At left when container is on. On the right when it is switched off. I'm the only one who noticed it? Moreover I found this on Supervisor LOG of HA: 21-03-11 15:37:48 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'startup' with 'before' is deprecated. Please report this to the maintainer of Unraid API.
  8. @fireb1adex do you have any working template for it?
  9. It's working but it's slow and not always responding. There's another process that I don't know that is kicking up CPU Do you know it? Below new diagnostics joshua-diagnostics-20210311-1240.zip
  10. Hey, thank you. I removed Dynamix Cache and stopped nextcloud. If the VM is off the peaks are gone and CPU usage seems regular. I tried your XML but still CPU dedicated is 100% all the time
  11. Disable Dynamix Cache Directories and seems gone. The main issue persist: VM in HTOP is always 100% CPU. Even if I wait or add more core to it.
  12. I disabled al VM and Docker. Still see CPU pick related to this process. Anyone can support me?
  13. OK I updated AND re created VM based on new template coping settings from previous one. I don't understand why CPU now is always high (related to VM) Below the diagnostics. joshua-diagnostics-20210310-1951.zip
  14. OK now dockers are back on line. Thank you. VM instead in on but gui in unreacheable. I had to manually reselect image to make it start again
  15. Here it is, sorry. joshua-diagnostics-20210302-1559.zip
  16. To the empty appdata folder. But maybe it's better to stop this backup, erase those files restored via CA application and simply readd cache. Right?
  17. Yes I noticed now that cache drive as not mounted. What to do know? Let appdata restore finish or delete appadata restored and mount cache drive?
  18. Hi all, This morning I update to 6.9. At first it seems that all was good but my hassio VM was not responding an CPU was constantly at 100%!. So I decided to go back to working 6.8.3 but this erased all my dockers and my VMs. (!) I have a backup of appdata but I'm wondering what is the best way to restore dockers. And also how can I restore VM from image? TY in advance!
  19. hi @ElectricBrainUK can you please add to your docker also information coming from UPS? It would be great to see status, battery percentage and runtime left . I don't know if it is better APC UPS or NUT for this. Thank you
  20. @jonathanm @Squid @iarp any feedback on how to do this now? My StartVMs works but it's not trigged by Delay VM Start #!/bin/bash echo "/boot/config/plugins/user.scripts/scripts/StartVMs/script" | at now Thank you
  21. OK changed MQTTCacheTime to 60 and MQTTRefreshRate to 5. Will let you know the results.
  22. Yes my system is in italian (ui) but status are always in english (on - off, true - false) and are visibile in the other language only in the frontend. I don't think it is related. Moreover I want you to notice that it's just a delay. After some time the status is updated.
  23. Hi all, I use this docker container from a while now and I noticed a issue that maybe it's not related to the container because it seems no other has is. This are my settings: What I noticed is that it tooks more time than declared : HA tooks some time to see the status of the containers, vm etc. Look at this picture: status is "started" but the switch created by HA is in "off" status. Any hint?