benflux

Members
  • Posts

    76
  • Joined

  • Last visited

Posts posted by benflux

  1. I recently lost my config for the UPS i've been using. Yesterday I had a power outtage and Unraid all went down uncleanly. Fortunately I think all is OK but I now need the settings for the UPS and i've been struggling to re-find the information. I'm connected by USB. Any tips?

     

    Tried many options and i'm currently here: 

     

    image.png.15eddfff42b4911e80356bf010e40ec8.png

  2. I've got Node-RED installed as a docker and it can see states on devices I share with it from my Hubitat hub at the time of deploying a change but if a state changes in Hubitat, the state doesn't update in Node-RED because the POST isn't getting through.

     

    This prevents my flows from starting because they don't know a state has changed.

     

    I've been told to look at whether the ports are open on my node-red docker to allow posts from the hub, the hub sends it's posts to: http://192.168.1.2:1880/hubitat/webhook__

     

    How do I ensure 1880 is 'open'? I'm running the docker with its own IP on br0.

     

    Or am I missing something?

     

     

  3. 4 hours ago, trurl said:

    Why have you allocated 50G to docker image? Have you had problems with it filling? Making it larger won't fix anything, it will just make it take longer to fill.

     

    I always recommend 20G and it is unlikely you would need even that much unless you have one or more of your docker applications misconfigured.

     

    The typical way you get a docker image filling up, or get usage growing, is by having some path in an application that doesn't correspond to a mapping. Common mistakes are not using the same upper/lower case as mapped, or not using an absolute path.

     

    Possibly unrelated, but other things I see with your configuration that are not ideal:

     

    Most of your disks are very full, and some are still ReiserFS.

     

    Your appdata, domains, and system shares are on the array instead of cache. Those shares, and their dockers and VMs, will perform better on cache since they won't be impacted by parity. And those shares on the array will keep array disks spinning. So the preferred location for those shares is all on cache and set to stay on cache.

    I went to 50G because once it filled up and I had plenty to give it. I guess I can reduce down.

     

    Also, how do i convert from ReiserFS? I guess I should fix the original issue before doing that anyway.

  4. 4 hours ago, BRiT said:

    One of the days you had an entire drive disappear from md slot 4. What happened there?

     

    On most of the days in your syslog it shows jackett docker being auto-uodated and restarted. Does that docker container actually get daily updates?

    I replaced a drive with a bigger one (it wasn't a trigger for dockers disappearing). jackett does seem to be update frequently