June 15, 20179 yr Important: If you want to report an issue, please start a new topic in this board. The main purpose of the 6.4 release is to improve some components that will be necessary for upcoming major features in 6.5. Hopefully the 6.4.0-rc series will be short. Note: please use plugin install method of upgrading a server to the next branch as described in this post. If you install by extracting from the release zip file, note there are now 5 "bz" files to copy. Here are some highlights of this release: Improved shfs/mover The LimeTech user share file system (shfs) has been improved in two areas. First, we now make use of FUSE read_buf/write_buf methods. This should result in significant throughput increases. Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array. Instead the move program invokes a new shfs ioctl() call. This should result in complete preservation of all metadata including atime and mtime. While this function has been fairly extensively tested, please keep an eye on mover activities - there shouldn't be any data loss, but it's a fairly significant code change. Also note: the /mnt/user0 mount point is no longer needed and has been removed. nginx http server We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGui). The emhttp process has been changed to a daemon (emhttpd) listening at a unix socket. Incorporating nginx provides several features: Multi-threaded access, though emhttpd is still single-threaded. https (SSL) support. At present unRAID OS will generate a self-signed certificate. https works but you will get a scary warning from your browser about not being able to verify the certificate. No worries. nchan (websocket) support. We have only just begun the process of converting many of the browser javascript polling functions to an event-driven websocket paradigm. This opens the door for us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard. enabling https To enable https support it's necessary to edit your 'config/go' file on your USB flash boot device. Use the -p option to specify the port(s) and optionally include the -r option to redirect http request from your browser to using https. Here's the detailed usage: # Usage: # emhttp [-r] [-p port [,sslport]] [OPER] # OPER is start or stop. Default is start. # By default nginx will be setup to listen only at port 80 (http). # The -p option may be used to define different listening ports and/or setup nginx # to listen at a specified port for https. The -r option may be used to setup # nginx so that any http request is redirected to https (this requires that both # ports have been specified with -p option). For example, to have nginx listen # at both standard ports but redirect all http to https use: # emhttp -rp 80,443 # To listen at only port 443 use: # emhttp -p ,443 # Note: the stop operation is only "safe" if the array has already been stopped # (this will be fixed). linux 4.11 kernel - should provide better Ryzen support among other improvements. IPv6 support We want to again, give a big "thank you" to bonienl who has greatly improved unRAID OS networking with the addition of IPv6 support. Give it a try and report any issues. Other Two new webGUI themes: Azure and Gray. Again, thanks to bonienl. Expanded driver support (QLogic) and more hardware monitoring support. Many more misc. improvements Version 6.4.0-rc3 2017-06-14 Linux kernel: version 4.11.5 md/unraid version: 2.8.1 bug fix: replacing "invalid" parity device does not check that size of new device is large enough Management: emhttp: by default have nginx listen only a port 80 (http); added -r option to redirect http to https emhttpd: fix mover logging enable/disable emhttpd: start nginx before docker and libvirt webgui: Add generation of custom icon in header (sidebar) for themes AZURE and GRAY webgui: Fixed IP address check and VLAN support in Docker service creation webgui: Enhanced Read/Write operations for easy cloning of user shares and disk shares webgui: More refinements in User share s and Disk shares webgui: Removed hardcoded width in share-edit webgui: Correction and update of clone functionality, now also available for AFP and NFS webgui: Fixed potential misbehavior of input element in themes AZURE and GRAY Version 6.4.0-rc2 2017-06-04 Management: emhttpd: fix mover invokation Version 6.4.0-rc1 2017-06-04 Base distro: acpid: version 2.0.28 adwaita-icon-theme: version 3.24.0 apcupsd: version 3.14.14 (rev2, added modbus-usb support) at-spi2-atk: version 2.24.0 at-spi2-core: version 2.24.0 atk: version 2.24.0 btrfs-progs: version 4.10.2 cairo: version 1.14.8 coreutils: version 8.27 cryptsetup: version 1.7.5 curl: version 7.54.0 (CVE-2017-7468, CVE-2017-2629) dbus: version 1.10.16 dejavu-fonts-ttf: version 2.37 dhcpcd: version 6.11.5 docker: version 17.05.0-ce dosfstools: version 4.1 e2fsprogs: version 1.43.4 etc: version 14.2 (rev10) ethtool: version 4.10 eudev: version 3.2.2 file: version 5.30 flex: version 2.6.4 fontconfig: version 2.12.1 freetype: version 2.7.1 gd: version 2.2.4 gdbm: version 1.13 gdk-pixbuf2: version 2.36.6 glibc: version 2.25 glibc-zoneinfo: version 2017b glib2: version 2.52.1 gnome-themes-standard: version 3.22.3 gnutls: version 3.5.10 (CVE-2017-5334, CVE-2017-5335, CVE-2017-5336, CVE-2017-5337) gptfdisk: version 1.0.1 grep: version 3.0 gtk+3: version 3.22.12 harfbuzz: version 1.4.6 hdparm: version 9.51 htop: version 2.0.2 iproute2: version 4.10.0 iptables: version 1.6.1 irqbalance: version 1.2.0 jemalloc: version 4.5.0 kernel-firmware: 20170330 keyutils: version 1.5.10 kmod: version 24 libarchive: version 3.3.1 libcroco: version 0.6.12 libdrm: version 2.4.80 libedit: version 20160903_3.1 libepoxy: version 1.4.2 libevdev: version 1.5.6 libevent: version 2.1.8 libgcrypt: version 1.7.5 libgudev: version 231 libjpeg-turbo: version 1.5.1 liblogging: version 1.0.6 libnetfilter_conntrack: version 1.0.6 libnftnl: version 1.0.7 libnl3: version 3.2.29 libpcap: version 1.8.1 libpciaccess: version 0.13.5 libpng: version 1.6.29 (CVE-2016-10087) libpthread-stubs: version 0.4 librsvg: version 2.40.17 libseccomp: version 2.3.2 libssh2: version 1.8.0 libtasn1: version 4.10 libusb-compat: version 0.1.5 libvirt: version 3.2.0 libX11: version 1.6.5 libXfont2: version 2.0.1 libXi: version 1.7.9 libXpm: version 3.5.12 lvm2: version 2.02.170 lz4: version 1.7.5 mc: version 4.8.19 mesa: version 17.0.5 mozilla-firefox: version 53.0.2 (CVE-2017-5031, CVE-2017-5433, CVE-2017-5435, CVE-2017-5436, CVE-2017-5461, CVE-2017-5459, CVE-2017-5466, CVE-2017-5434, CVE-2017-5432, CVE-2017-5460, CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442, CVE-2017-5464, CVE-2017-5443, CVE-2017-5444, CVE-2017-5446, CVE-2017-5447, CVE-2017-5465, CVE-2017-5448, CVE-2016-10196, CVE-2017-5454, CVE-2017-5455, CVE-2017-5456, CVE-2017-5469, CVE-2017-5445, CVE-2017-5449, CVE-2017-5450, CVE-2017-5451, CVE-2017-5462, CVE-2017-5463, CVE-2017-5467, CVE-2017-5452, CVE-2017-5453, CVE-2017-5458, CVE-2017-5468, CVE-2017-5430, CVE-2017-5429) nano: version 2.8.2 ncurses: version 6.0 netatalk: version 3.1.11 nettle: version 3.3 nfs-utils: version 2.1.1 nginx: version 1.12.0 ntfs-3g: version 2017.3.23 ntp: version 4.2.8p10 (CVE-2017-6464, CVE-2017-6463, CVE-2017-6458, CVE-2017-6460, CVE-2016-9042, CVE-2017-6462, CVE-2017-6451, CVE-2017-6455, CVE-2017-6452, CVE-2017-6459) openssh: version 7.5p1 (CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012) openssl: version 1.0.2k (CVE-2017-3731, CVE-2017-3732, CVE-2016-7055) pango: version 1.40.5 pciutils: version 3.5.4 php: version 7.1.4 procps-ng: version 3.3.12 qemu: version 2.9.0 (CVE-2017-2615, CVE-2017-2630) rsyslog: version 8.26.0 samba: version 4.6.4 (CVE-2017-7494, CVE-2017-2619) + patch for Time Machine fullsync support sed: version 4.4 sessreg: version 1.1.1 shadow: version 4.2.1 (rev2) (CVE-2017-2616) shared-mime-info: version 1.7 sqlite: version 3.16.2 sudo: version 1.8.19p2 util-linux: version 2.29.2 (CVE-2017-2616) wget: version 1.19.1 xauth: version 1.0.10 xf86-input-evdev: version 2.10.5 xf86-input-keyboard: version 1.9.0 xf86-input-mouse: version 1.9.2 xf86-input-synaptics: version 1.9.0 xf86-video-mga: version 1.6.5 xfsprogs: version 4.10.0 xorg-server: version 1.19.3 xterm: version 327 xz: version 5.2.3 zlib: version 1.2.11 Linux kernel: version 4.11.3 added IPv6 support added QLogic Ethernet support: CONFIG_BNA: QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support CONFIG_QLA3XXX: QLogic QLA3XXX Network Driver Support CONFIG_QLCNIC: QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support CONFIG_QLGE: QLogic QLGE 10Gb Ethernet Driver Support CONFIG_NETXEN_NIC: NetXen Multi port (1/10) Gigabit Ethernet NIC added squashfs to support mounting /boot/bzmodules, /boot/bzfirmware additional config options: CONFIG_BLK_DEV_PCIESSD_MTIP32XX: Block Device Driver for Micron PCIe SSDs CONFIG_BNXT: Broadcom NetXtreme-C/E support CONFIG_CMA: Contiguous Memory Allocator CONFIG_MTD: Memory Technology Device support CONFIG_NUMA_BALANCING: Memory placement aware NUMA scheduler CONFIG_NUMA_BALANCING_DEFAULT_ENABLED: Automatically enable NUMA aware memory/task placement expanded set of included hwmonitor modules md/unraid version: 2.8.0 accommodate kernel 4.11 api changes bug fix: if one disabled disk and another invalid disk, should not be able to unassign third disk modules now compressed with XZ Management: create ntp and avahi users if missing replace cpuload daemon with websocket endpoint firmware now loaded on-demand from 'bzfirmware' file located on USB boot device force correcting-fsck on USB boot flash before mounting integrate nginx http-server including php-fpm and nchan support modules now loaded on-demand from 'bzmodules' file located on USB boot device support https with auto-generated self-signed certificates update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} emhttp: detect "unraidsafemode" boot and prevent array autostart if set emhttp: eliminate "/mnt/user0" shfs mount point. emhttp: fix 'btrfs check' running status not detected correctly emhttp: if valid old key on same usb flash device as Trial key, offer to replace key emhttp: invoke emhttpd daemon listening on local unix socket shfs: Full atim/mtim preservation. shfs: implement ioctl() functions to move objects shfs: utilize FUSE read_buf/write_buf methods mover: use shfs ioctl() instead of 'rsync' webGui: added new themes 'Azure' and 'Gray' webGui: allow custom IP addresses for individual Docker containers webGui: changed screen width to automatic with minimum of 1080 webGui: networking now allows multi bonds and multi bridge groups webGui: new watchdog service with websockets instead of ajax polling webGui: utilize pubsub/cpuload nchan websocket endpoint to update cpu load info webGui: IPv6 networking and routing table management webGui: correct case of cache device assignment not being preserved across array restart webGui: Upgrade tooltipster to version 4.2.3 webGui: Fixed file read errors when system is started but array is stopped webGui: Fixed persisting the show banner value after applying disk settings webGui: Fixed regression error in erroneous display of disk table on Dashboard webGui: Registration page refinements
June 15, 20179 yr Currently my go file has: /usr/local/sbin/emhttp & Since /usr/local/sbin is in $PATH it makes sense that we don't need that part, but I'm not sure about the '&'. Do we still need that? Or can I just do this now: emhttp -rp 80,443
June 15, 20179 yr 2 hours ago, trurl said: Currently my go file has: /usr/local/sbin/emhttp & Since /usr/local/sbin is in $PATH it makes sense that we don't need that part, but I'm not sure about the '&'. Do we still need that? Or can I just do this now: emhttp -rp 80,443 Looks like /usr/local/sbin is still needed, I assume because $PATH hasn't been set yet. It seems to work without the '&' though. Should we be able to import the certificate to get rid of the warning?
June 15, 20179 yr 10 hours ago, limetech said: If you install by extracting from the release zip file, note there are now 4 "bz" files to copy. Sorry to be pedantic, but there are actually 5 bz files
June 15, 20179 yr 3 hours ago, trurl said: Should we be able to import the certificate to get rid of the warning? There isn't an interface yet, but you can replace certs on your flash drive: Lots more interesting SSL-related discussion in that thread too
June 15, 20179 yr 5 hours ago, trurl said: Currently my go file has: /usr/local/sbin/emhttp & Since /usr/local/sbin is in $PATH it makes sense that we don't need that part, but I'm not sure about the '&'. Do we still need that? Or can I just do this now: emhttp -rp 80,443 This is the default go script in the rc3 zip file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & So I think you'll still want to include the full path and the & Edited June 15, 20179 yr by ljm42
June 15, 20179 yr Author 20 minutes ago, ljm42 said: Sorry to be pedantic, but there are actually 5 bz files Right you are. Corrected. Reminds me of a scene in a certain Mel Brooks movie.
June 15, 20179 yr 2 minutes ago, ljm42 said: This is the default go script in the rc4 zip file: Sorry to be pedantic, but it is actually rc3
June 15, 20179 yr Author 2 minutes ago, ljm42 said: So I think you'll still want to include the full path and the & For stuff like this I kinda like explicit paths. Guards against stuff like a plugin changing PATH. Putting it immediately in the background retains the historic behavior where 'emhttp' can be performing initialization in parallel with other command specified after that line. For a stock build, again, doesn't really matter.
June 15, 20179 yr Interesting discovery over here on rc3... I've had a MacVLAN setup for Docker since 6.3.x and I've been using that happily since. I have to remake it every time I upgrade unRAID (which is fine) but I got to rc3 today, just did a reboot to make sure everything was in order and my MacVLAN disappeared! And as such one of my docker containers didn't start. Here's the command I'm running, taken straight from the Docker manual. docker network create -d macvlan \ --subnet=192.168.86.0/24 \ --gateway=192.168.86.1 \ -o parent=br0 macnet100 Any reason that it would be deleted automatically on reboot? Am I doing it wrong? Assistance would be appreciated Thanks! Edited June 15, 20179 yr by nexusmaniac
June 15, 20179 yr macvlan support is now built-in to unRAID. You can use the GUI to assign custom networks to docker containers instead of manual configuration, which may interfere with the automatic discovery and assignment of custom (macvlan) networks.
June 15, 20179 yr 5 minutes ago, bonienl said: macvlan support is now built-in to unRAID. You can use the GUI to assign custom networks to docker containers instead of manual configuration, which may interfere with the automatic discovery and assignment of custom (macvlan) networks. Care to point me in the right direction? The command I posted only creates the MacVLAN network. I cannot find a section in the GUI to create a MacVLAN network When macnet100 is created, I can select it on the dropdown in the container edit screen. (I still need to set extra parameters to get the static IP in the custom network) -h Raptor_Staging --net=macnet100 --ip=192.168.86.250 But like I said, after I reboot, my macnet100 (created by my first post) vanishes. If I can create a MacVLAN within the GUI that's awesome and I'd happily use that instead.
June 15, 20179 yr You don't need to create anything yourself. When the docker service is started it will scan the available network interfaces and any interface with an IP address assigned to it (e.g. eth0 or br0) gets added as a custom network to docker. When you edit a container itself you will see the custom networks added to the regular network choices: Bridge, Host and None. Select a custom network, eg. br0 and another field is made visible to enter an IP address to this container or leave it empty for automatic assignment by the Docker IPAM function. To avoid address conflicts between your DHCP server (router) and the Docker IPAM function, you can assign an address pool for the latter one. Go to settings -> Docker and stop the service. Once the service is stopped additional settings can be configured. Ps. Choose Advanced Mode to make all settings visible. Edited June 15, 20179 yr by bonienl
June 15, 20179 yr Apologies, you've lost me somewhat - And I'm supposed to be working in a networking company All I'm looking to do is assign 192.168.86.252 to one of my dockers I've got DHCP running on my network and have opted to run my whole network on DHCP and just reserve static IP's as I need (so that if I change my DNS settings, for instance, it rolls out automatically through DHCP). Anyway!.. I'm connected to my LAN via eth0 on 192.168.86.253 - How do I go about adding that additional IP address? I can see the above option, not sure that's exactly what I'm looking for as I don't need to setup a sub-DHCP pool for dockers within my network. I just need to assign a single IP to a single container I know the dropdown you speak of too, if I manually create my 'macnet100' it shows up in this list - Issue is that it doesn't persist through reboots anymore And there was no way I could see to add another IP address in the /Settings/NetworkSettings.
June 15, 20179 yr If you don't need dynamic addresses of your containers then just leave the option empty. Start the docker service and go edit your containers, you will see the network br0 added as a new choice. If this is not visible it is because you did a manual adding for the same resource. Make sure you remove the manual addition, remove it from docker with "docker network rm macnet100", then restart the docker service.
June 15, 20179 yr 7 minutes ago, bonienl said: If you don't need dynamic addresses of your containers then just leave the option empty. Start the docker service and go edit your containers, you will see the network br0 added as a new choice. If this is not visible it is because you did a manual adding for the same resource. Make sure you remove the manual addition, remove it from docker with "docker network rm macnet100", then restart the docker service. I don't want br0 though do I? That'll just use 192.168.86.253 I need it to be 192.168.86.252 on a specific container Wow... Sorry, I see exactly what you mean! Thanks for the help @bonienl!! I can select a static IP when I choose br0, my bad Edited June 15, 20179 yr by nexusmaniac
June 15, 20179 yr 2 minutes ago, nexusmaniac said: I don't want br0 though do I? That'll just use 192.168.86.253 I need it to be 192.168.86.252 on a specific container Yes you need br0, because it tells Docker which custom network to use and allows you to assign the address 192.168.86.252 to your container.
June 15, 20179 yr Just now, bonienl said: Yes you need br0, because it tells Docker which custom network to use and allows you to assign the address 192.168.86.252 to your container. I noticed pretty much as you sent this, I just edited my above post What a "Doh" moment... Sorry about that - Cheers!
June 15, 20179 yr 2 hours ago, bonienl said: Start the docker service and go edit your containers, you will see the network br0 added as a new choice. If this is not visible it is because you did a manual adding for the same resource. Make sure you remove the manual addition, remove it from docker with "docker network rm macnet100", then restart the docker service. That's super cool! though now that you guys fixed the 443 thing on boot i dunno if i need to worry about it lol.
June 15, 20179 yr 1 minute ago, Dephcon said: That's super cool! though now that you guys fixed the 443 thing on boot i dunno if i need to worry about it lol. You still can do a redirect to https. Maybe one day you want that
June 15, 20179 yr here's a silly feature request... can you guys add a command ailas for "ll". it drives me nuts when linux systems don't have that I know i can just dump an alias in my go, but I'd like to keep the base OS as stock as possible as a best practice. Edited June 15, 20179 yr by Dephcon
June 15, 20179 yr just gave the Azure theme a whril, it's very slick bonienl! Is it possible to remove the sidebar "jiggle" when highlighting the items?
June 15, 20179 yr Microsoft Edge uses an auto-hide feature and makes the scrollbar visible when moving the sidebar. There is no full hide possible. Chrome and Safari completely hide the scrollbar. Firefox you'll need to install the plugin "hidescrollbars" to get the same behaviour as Chrome & Safari Edited June 15, 20179 yr by bonienl
Archived
This topic is now archived and is closed to further replies.