Jump to content

benflux

Members
  • Content Count

    65
  • Joined

  • Last visited

Posts posted by benflux


  1. I want to access a public share via NFS from my CCTV software. It can't connect to the share and I wonder if this screenshot is saying NFS isn't enabled on the share (it is enabled globally in the settings)?

    image.png


  2. 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.


  3. 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


  4. this is me disabling and re-enabling docker:

     

    Jun 12 09:07:41 NAS2 root: stopping dockerd ...
    Jun 12 09:07:42 NAS2 root: waiting for docker to die ...
    Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Interface docker0.IPv4 no longer relevant for mDNS.
    Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
    Jun 12 09:07:43 NAS2 avahi-daemon[4198]: Withdrawing address record for 172.17.0.1 on docker0.
    Jun 12 09:07:43 NAS2 emhttpd: shcmd (264): umount /var/lib/docker
    Jun 12 09:07:50 NAS2 ool www[9361]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
    Jun 12 09:07:50 NAS2 emhttpd: req (3): cmdStatus=apply&csrf_token=***************
    Jun 12 09:07:50 NAS2 emhttpd: Starting services...
    Jun 12 09:07:50 NAS2 emhttpd: shcmd (270): /etc/rc.d/rc.samba restart
    Jun 12 09:07:52 NAS2 root: Starting Samba: /usr/sbin/nmbd -D
    Jun 12 09:07:52 NAS2 root: /usr/sbin/smbd -D
    Jun 12 09:07:52 NAS2 root: /usr/sbin/winbindd -D
    Jun 12 09:07:52 NAS2 emhttpd: shcmd (283): /usr/local/sbin/mount_image '/mnt/disk1/docker.img' /var/lib/docker 50
    Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): disk space caching is enabled
    Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): has skinny extents
    Jun 12 09:07:52 NAS2 root: Resize '/var/lib/docker' of 'max'
    Jun 12 09:07:52 NAS2 kernel: BTRFS info (device loop2): new size for /dev/loop2 is 53687091200
    Jun 12 09:07:52 NAS2 emhttpd: shcmd (285): /etc/rc.d/rc.docker start
    Jun 12 09:07:52 NAS2 root: starting dockerd ...
    Jun 12 09:07:53 NAS2 avahi-daemon[4198]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
    Jun 12 09:07:53 NAS2 avahi-daemon[4198]: New relevant interface docker0.IPv4 for mDNS.
    Jun 12 09:07:53 NAS2 avahi-daemon[4198]: Registering new address record for 172.17.0.1 on docker0.IPv4.
    Jun 12 09:07:53 NAS2 kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready


  5. Solved it by following this guide here: https://community.home-assistant.io/t/help-smartthings-docker-unraid-installation-almost-there/10071/15

     

    I put unique IPs on each docker and got the MAC address of the MQTT docker to put in Smartthings.

     

    SO happy.


  6. If there is anyone that can help diagnose my inability to have Smartthings show it's devices in HASS then it will stop be tearing my hair out.

     

    I 'think' I've got HASS talking to MQTT, which seems to be talking to the Smartthings-Mqtt-Bridge, I've got the device handler, device and smartapp in Smartthings too. My issue is that Smartthings doesn't appear to be talking to the bridge because no devices show in Hass and when I view the Docker log in Unraid, there is no mention of anything incoming from Smartthings.

     

    Please can any one help?