Jump to content

bonienl

Community Developer
  • Content Count

    7779
  • Joined

  • Last visited

  • Days Won

    45

Report Comments posted by bonienl


  1. 1 minute ago, dan91 said:

    Hi, are they windows VM's?

    Yes, some are Windows VMs, and stopping them brings cpu load down.

    2 minutes ago, dan91 said:

    Just double check your not experiencing this issue;

    Thanks for the pointer. I see the high load already before using RDP, but may experiment a bit with the given workaround.


  2. 5 minutes ago, local.bin said:

    Thanks, but I have checked and all seems fine

    Your errors messages indicate something is wrong with the bz* files on the USB stick (maybe bad download).

     

    You can try to revert to the previous version (see Tools -> Update OS)

    And afterwards update again (make sure the USB stick is error free)

     


  3. 7 hours ago, emuhack said:

    If someone can point me in the direction of setting up the Vibr0 to pass to my br0 traffic

    That's not possible.

    7 hours ago, emuhack said:

    Otherwise I will have to go get another NIC

    That's the easiest way to solve the issue.

    You should configure the 2nd NIC without IP address under network settings, and assign it to VMs


  4. 14 hours ago, olympia said:

    Does this make any sense to you?

    Yes.

    Tips and tweaks makes changes to the interface, which becomes disabled, causing docker not to see it when it is started and hence the custom network br0 is not created.

    Oct 15 11:24:25 Tower kernel: br0: port 1(eth0) entered disabled state
    Oct 15 11:24:25 Tower tips.and.tweaks: Tweaks Applied
    Oct 15 11:24:33 Tower rc.docker: qbittorrent: Error response from daemon: network 69343f3bce328d98de4c1f7a854261aad7985f52c84c8026adbe8aef3826c91b not found

     


  5. If interface assignment wasn't as before or the driver wasn't loaded, it points to an issue with the USB device where all this information is stored.

     

    Did you check your USB device for any corruption?

     

    - please attach diagnostics if the issue re-occurs.

    - this is not common at all, no need to mark as urgent