unevent

The page doesn't update on its own when you start the vboxwebserv. A few seconds after you see the 'vboxwebserv service started', hit the refresh button in your browser, or stop then refresh.

Post a screenshot of the virtualbox plugin page. What Apache are you using (Docker/plugin and author)?

Pipework EOL should be 6.3.5 as it was written to perform this function before Docker had a native method, and I don't see it as a convoluted solution as it is simple to implement and customize. Moving forward with 6.4 release there are native Docker methods to use that hopefully get better and easier with age.

Do you have the pipework Docker installed? The br0 bridge can be enabled in the Network Settings page in the GUI - set the 'Enable Bridging' to Yes and set the 'Bridging Members' to the interface you intend to use (eth0 as example). The 'Homenet' thing sounds like part of the manual macvlan method, and if going with pipework, yes remove it. Install the pipework Docker if not already. Start it and view the log for it and check the last line of the log has 'started' in it. Sometimes it will not start and so you stop then start again until the last line shows pipework start. Pipework should be the running before starting any other Dockers that use it. PIpework itself requires no configuration. For each Docker you want to assign an IP for, view the Docker config page and change "Network Type' to 'None'. In the 'Extra Parameters' box, add the line below, but change the IP addresses for those you are using on your network. It is set up as [IP of Docker]/24@[gateway address]. The '@CONTAINER_NAME@' needs to be exactly that, do not change it to match the Docker name. In the example below, the IP of the Docker will be '192.168.1.110' with a Gateway of '192.168.1.1'. -e 'pipework_cmd=br0 @CONTAINER_NAME@ 192.168.1.110/[email protected]' The IP address you choose for each docker should be outside the range for DHCP if you have one configured on your network. There are more ways to use pipework such as associating the IP to a MAC address so you can do a static map on your router and associate the IP with a hostname in local DNS so instead of typing '192.168.1.110:[port]' into a web browser, you can do 'http://sabnzbd:[port]', as example. If you change the Docker host port to container port map to 80 or 443 for http/https, respectively, you can get rid of the port requirement and just do https://sabnzbd, http://plex, etc. So plex host map would be 80 while the container map would be 32400, as example. There is a trickle-down effect with this port map method depending on the Docker for connectivity requirements with the outside world and may not work for every Docker. -e 'pipework_cmd=br0 @CONTAINER_NAME@ 192.168.1.110/[email protected] fd:df:b6:95:53:1c' The MAC address should be unique, random, and valid for each IP. The remainder is up to whatever router you use on your network to assign the MAC/IP static map to hostname.

I see...you are using the speedtest plugin for unRAID and comparing it to the web based version of speedtest. The results are not the same as what you would get using the web site. I believe the author even states this in the plugin thread. If you want to verify your local network speeds suggest using iperf on two computers. Iperf is available in the Nerd Pack plugin. A Google search should get you instructions for how to perform a test.

According to Plex, that feature requires Plex Pass.

Your mixing pipework with the alternate manual macvlan method. If you stay with pipework (undo all the manual macvlan first and enable br0 bridge) you can either change the IP address in the 'extra options' box in the Docker config (advanced view turned on) or change the port map to use a different port. Ideally each Docker should have a unique IP when used with pipework as that is what it was written for. Pipework or manual macvlan - one method or the other, but use only one method.

TLER? 3.3v reset? I've read mixed reports on reddit regarding those being present.

I used a 4-40 (or 6-32, can't remember which one fit better) tap to make threads between the vanes on the sink and just used two screws to hold my 40x40 fan on. Edit: I have two H310, the first I used this copper heatsink/fan combo. The second I used this fan with the stock heatsink. To attach, I drilled two 4-40 thru-holes between the fins (fan sits slightly out of square to the sink due to this), lightly chamfered the holes on the smooth side. I used a 4-40 tap on the two diagonal holes and polished the flat side with 1200 grit on flat surface. I attached the fan with socket head cap screws. Both fans plug into separate motherboard fan headers and I control them using the motherboard.

For balance-rr you will only see greater than 1Gbit with a Linux client - it will not work in Windows except for Windows Server. Also, even with Linux you will suffer throughput issues with smb transfers due to the out of order packets and the congestion control kicking in. NFS is better and I can get 2Gbit transfer speeds. It needs switch support - trunking/link aggregation. Mode 4/802.3ad I believe will not get you faster than 1Gbit on a single copy/transfer, but you can have multiple 1Gbit transfers taking place depending on the number of members in the group. Infiniband/2.5/5/10G Ethernet is about the only real way to get faster than 1Gbit with Windows.

The logging/display would/could be done separately in a Docker or VM on unRAID. pfLogstash in Docker form here on the forums will work for pre 2.4.x release. The grok filters need an update to work with the latest pfSense release (which was release a couple weeks ago or so). Graylog is also available in a Docker here and can also spin up a VM using Ubuntu Server which I did for a while , but also needs filter update for 2.4.1. There are a few 'traditional' ELK stacks in Docker flavor floating around as well. There is a package or two available on pfSense to do some logging/sorting such as which websites an IP visited, but no fancy graphics like what is available using the external tools. Regarding running pfSense in a VM on unRAID , my suggestion is to not do it without an in-place backup to take over the tasks when you stop the array or shut down the server. I like KISS principal when it comes to network security, get a low power-draw dedicated system to run your firewall. There are numerous guides on the 'net for setting up just about anything pfSense. Squid is a caching proxy server and has limited use these days since Internet pipes are fat and fast. I only use it for some minor additional filtering and for basic antivirus (clamav) on unencrypted traffic.

Started similar, but with 600MHz MIPS ASUS router running Tomato. I miss Tomato's configuration GUI and QOS, but pfSense is much more powerful/capable. With the Kabini I can do VPN using PIA strong encryption to the full 100Mbit Internet I have which is usually around 14MB/s. OpenVPN being single threaded my only suggestion is to favor higher clock speeds vs. more cores at lower clock and of course AES-NI hardware support.

Check syslog for any activity not generated by you. If you intend to open common ports like http temporarily in the future, port forward from some obscure irrelevant port that is way out there so no one or the typical port scan won't ping it and discover it easily.

Different product, WDBCKA0080HBK-NEBB what it is now at $129 and WDBCKA0080HBK-NESN which is what it has been and is at $199 now. Most likely different drives inside. The NEBB is sold out, the NESN should still be in stores. Go try your luck at convincing a store tech to price match.

pfSense. Use ELK, Greylog, pfLogstash, etc. to get your reporting with the pretty views. I run it on AMD 5350 Kabini and ASRock AM1H-ITX with 16GB, 4-port Intel card and external laptop power supply. Runs around 30W at full load, 10-15W average. Snort, pgBlockerNG, Squid, OpenVPN, Radius server, probably forgot something.

If you cross your eyes, it's there...

I briefly looked at your diagnostic files and saw a whole lot of interesting things going on...Looks like you have about 64GB of ram with a 64GB swap file with all but 775MB used. Really don't need a swap file with that much ram installed and definitely not that large. Your appdata folder should be cache-only and if you don't have a cache drive I strongly suggest getting one. As you read/write files you are filling up your ram between flushes as that is what Linux does and then you swap out to disk adding to the disk I/O issue. Suggest installing the Docker called 'Netdata' from CA and have it open in a web browser the next time you do one of those large SMB transfers and post a screenshot. Then disable your swap file and try it again.

Update for new sale: Newegg has the HGST 0S04012 8TB NAS drive for $209.99 with promo code, expires 11/19 ($26.25/TB) Newegg has the HGST 0S04037 10TB NAS drive for $299.99 with promo code, expires 11/19 ($30/TB)

Newegg.com has a sale ending Sunday (11/5) with rebates for the Seasonic FOCUS Plus series 80+ Gold 10-year warranty power supplies in several flavors: 550W: $79.90 and after $20 rebate, $59.90 650W: $79.99 and after $20 rebate, $59.99 750W: $79.90 and after $10 rebate, $69.90 850W: $99.99, regular price, no rebate Tom's 750W Review JonnyGuru 850W Review JonnyGuru 750W Review JonnyGuru 550W Review

Those UPS coax protections are typically not good for anything beyond analog antenna which is of no use these days. The lightning protection typically consists of a poorly implemented gas discharge tube device and on most if not all consumer grade surge protectors/UPS they are typically not impedance matched for 75 ohm use and the higher frequencies involved with digital OTA, cable TV/Internet, and Satellite will suffer from signal reflections. In the US it is NEC requirement for coax to be grounded at or near the service entrance for cable/satellite and antenna (as it requires a rather large ground wire, typically 10AWG or larger). So if done right you should already be covered for outer conductor protection. Inner conductor protection suggest a high quality lightning surge protector rated for 1GHz with low insertion and return loss such as Tii Technologies 212FF75F225-21 (here, here) or if you can find it, Extreme Broadband Engineering BB1SP.

Have you identified what is using CPU resources in this VM? A lighter version of Ubuntu would be Xubuntu. It uses Xfce desktop which is lighter than Gnome/Unity and KDE and doesn't come with all the extras that Ubuntu does, but can be added.

From your log: Nov 1 14:36:02 homeNAS apcupsd[10300]: Power failure. Nov 1 14:36:03 homeNAS dhcpcd[1757]: eth0: carrier lost Nov 1 14:36:03 homeNAS kernel: e1000e: eth0 NIC Link is Down Nov 1 14:36:03 homeNAS avahi-daemon[10333]: Withdrawing address record for 192.168.1.152 on eth0. Nov 1 14:36:03 homeNAS avahi-daemon[10333]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.152. Nov 1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting route to 192.168.1.0/24 Nov 1 14:36:03 homeNAS avahi-daemon[10333]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting default route via 192.168.1.1 Nov 1 14:36:04 homeNAS ntpd[1815]: Deleting interface #2 eth0, 192.168.1.152#123, interface stats: received=133, sent=133, dropped=0, active_time=69257 secs Nov 1 14:36:04 homeNAS ntpd[1815]: 74.82.59.150 local addr 192.168.1.152 -> <null> Nov 1 14:36:08 homeNAS apcupsd[10300]: Running on UPS batteries. Nov 1 14:36:08 homeNAS sSMTP[4877]: Unable to locate smtp.gmail.com Nov 1 14:36:08 homeNAS sSMTP[4877]: Cannot open smtp.gmail.com:465 Nov 1 14:36:19 homeNAS apcupsd[10300]: Mains returned. No longer on UPS batteries. Nov 1 14:36:19 homeNAS apcupsd[10300]: Power is back. UPS running on mains. Nov 1 14:36:19 homeNAS sSMTP[5206]: Unable to locate smtp.gmail.com Nov 1 14:36:19 homeNAS sSMTP[5206]: Cannot open smtp.gmail.com:465 Nov 1 14:36:25 homeNAS dhcpcd[1757]: eth0: carrier acquired Nov 1 14:36:25 homeNAS kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 1 14:36:26 homeNAS dhcpcd[1757]: eth0: rebinding lease of 192.168.1.152 Nov 1 14:36:31 homeNAS dhcpcd[1757]: eth0: probing for an IPv4LL address Nov 1 14:36:31 homeNAS dhcpcd[1757]: eth0: DHCP lease expired Nov 1 14:36:31 homeNAS dhcpcd[1757]: eth0: soliciting a DHCP lease Nov 1 14:36:37 homeNAS dhcpcd[1757]: eth0: using IPv4LL address 169.254.251.87 Nov 1 14:36:37 homeNAS avahi-daemon[10333]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.251.87. Nov 1 14:36:37 homeNAS dhcpcd[1757]: eth0: adding route to 169.254.0.0/16 Nov 1 14:36:37 homeNAS avahi-daemon[10333]: New relevant interface eth0.IPv4 for mDNS. Nov 1 14:36:37 homeNAS avahi-daemon[10333]: Registering new address record for 169.254.251.87 on eth0.IPv4. Nov 1 14:36:37 homeNAS dhcpcd[1757]: eth0: removing route to 169.254.0.0/16 Nov 1 14:36:38 homeNAS ntpd[1815]: Listen normally on 3 eth0 169.254.251.87:123 Nov 1 14:36:38 homeNAS ntpd[1815]: new interface(s) found: waking up resolver Do you happen to have your Ethernet switch plugged into the 'Surge' only plug on the new UPS? After your UPS went on battery your Ethernet went dead. If power fails, or in the case of what looks like your plug-pull UPS test, the surge only outlets go dead. Also, whatever is plugged into the 'Master' outlet when turned off or goes to sleep/standby it will cause the two gray surge-only 'controlled by master' outlets to turn off as well. Another tidbit is to not plug in your gigabit Ethernet cable to the data protection ports. The ports are only rated for 10/100 connections.

I read some of your traffic in the UD topic and to me this may not be the best way to achieve what you are after. I'd suggest combining the two requirements (SageTV and Windows 10) into a single VM. You have minimum three pieces to a puzzle - Docker container, Windows 10 VM, and UD NFS mount. Trifecta of frustration in my book.

Is their some feature with this particular board you like? Not really the best choice for unRAID use, depending on what kind of configuration or expandability you are after. It has 3x PCIe x16 slots, one at x16, two at x4 so that limits HBA usage to one card at full bandwidth. It also uses the Killer E2500 chip for Ethernet vs. an Intel solution. I'd suggest if you are looking for a board with expansion capability then at least two PCIe x16 slots that run at x8 and also have an Intel Ethernet solution. A quick example would be the GA-Z270X-Ultra Gaming, but again not sure what features you care about or want.

Also agree, it was just strange the errors only occurred with the one script (repeatedly) vs. the other. Will do more testing when this first clear is finished.