dukiethecorgi

Seems kind of far fetched to me. It looks like they replaced a coupler that connects to the cache memory, but in that case each chip would only have access to a single bit, yet the article claims it contained a processor and network capability. I really don't see how that would work

manually copied from from /usr/local/emhttp/plugins/networkstats/vnstat.conf to /etc/vnstat.conf and it started working. (the b version) then saw the update to c version and still working Thanks!

same for me, still Oct 6 12:57:00 Tower vnstatd[23408]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting.

That's what I tried, removed old version and installed from scratch

Mine shows 2018.10.05

Still not working.... Installed latest version, after installation I see in the logs: Oct 5 21:42:57 Tower vnstatd[24665]: vnStat daemon 1.18 started. (pid:24665 uid:0 gid:0) Oct 5 21:42:57 Tower vnstatd[24665]: Monitoring: bond0 (2000 Mbit) eth0 (1000 Mbit) eth1 (1000 Mbit) The settings page says Stopped Try to start and the log says: Oct 5 21:46:44 Tower vnstatd[31073]: Error: pidfile "/var/run/vnstat.pid" lock failed (Resource temporarily unavailable), exiting. no PID of 31073 is running, but PID 24665 (vnstatd) is running /etc/rc.d/rc.vnstat status returns vnstat daemon is not running.

Here you go

OK installed the update, still not working, but /etc/rc.d/rc.vnstat start says it is running

Thanks!

Not starting for me either 😞

After upgrading to 6.6.0, I've been having issues connecting to the console from the Unraid page and also from docker containers. It sometimes works fine, but I often get a "502 Bad Gateway" instead. I can usually get it to work by closing the browser and then trying again, but sometimes I have to clear all cache in the browser for it to work. I'm using a chromebook with the latest Chrome version

Hello All- My Supermicro server has dual NIC cards. I recently reconfigured the network settings not to use bonding, so I have br0 and br1. In the docker settings I set "IPv4 custom network on interface br1:" to Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: 192.168.1.128/25 (128 hosts). I installed a LetsEncrypt container at 192.168.1.130 and it works without any issues, and I was able to set my router so that https://<external ip> is routed to the container. I wanted to use the SABnzbd container on 192.168.1.150, so I reconfigured it and it started up fine and I was able to connect to the container at http://192.168.1.150:8080. I ran into an issue at that point: none of my other containers (NZBHydra, Radarr, Sonarr, etc) was able to connect to the SABnzbd container. After some experimentation, I discovered if I reconfigured a container, say NZBHydra, to use an IP like 192.168.1.140, that it was able to connect properly. Is this expected behavior, or is there some routing rule I need to set to make this work? I recall reading something about some limitations using dual NIC container, but haven't been able to find details.

That worked, thanks!

I can connect to the container with VNC, but not with the web interface. The interface opens, but in the left corner it says "Putty" with a red X for server disconnected (error 1006). Connecting using Chrome

The easiest way is to use the 'Export Tools' addin for Plex https://github.com/ukdtom/ExportTools.bundle

Filebot does exactly what you want

I used high temperature epoxy found at Home depot to attach two little strips of wood to the heat sink, then screwed the fan to the wood strips. I suppose you could glue the fan directly, but you'll never get it off.

New Supermicro server build, 12C/24T and 48gb ram. Sata ports are 3gbs. Server will be 95% Plex and media serving, no VM's, just a few Docker containers. I was fortunate enough to end up with two Samsung 500gb SSD, and I'm wondering about the best way to configure them. The containers, Plex metadata, etc are about 200gb. I'd like to also have new content cached, that's about another 400-500gb. I really want this server to be Plex optimized, I'd like a very fast UI especially for new content. My first idea was to use one as cache, the other as an unassigned device. But having two separate volumes is a bit of an aggravation. I then saw that you can use a btrfs Raid 0 cache, which is nice as it presents a one large volume, but it doesn't seem like a btrfs Raid 0 is a set and forget sort of thing. I'd like to hear your opinions of how you would configure this for Plex

My server is using the built in Realtek 8111 card. It works Ok, but it often sees 90%+ utilization: - Deluge and sabnzbd downloads on a gigabit internet connection - Plex server reading disk, and serving clients - Moving large video files to local computers for encoding etc This is a simple /24 netwrok, no vlans, etc. Switch is a Netgear GS108T Will adding a second card add more network bandwidth?

Yeah, I get around 9200 Passmarks. Most of the clients using my server can use direct play, but there's a few that still need transcoding. unRaid and all the various containers don't seem to take much CPU at all, the only time I see high cpu usage is when something like SabNZBD extracts files from archives

Hey Everyone- For a Ryzen build that will be mostly for Plex, no video card needed, should I be looking for a B350 motherboard? I only need a single PCIe slot for a drive controller. Also, what's the advantage of going big on memory? In my existing unRaid box, most of the 16gb always shows as cached - is this disk caching?

I have a standalone AMD [email protected] Plex/Win10 box I'm using now that can handle 3, sometimes 4, transcodes. I'm thinking of building a new unRaid server and running Plex as a Docker container. I want to upgrade enough that I can serve 5-6 transcodes. I know the rule of thumb is 2K passmarks per transcode, just wondering what other peoples experiences are with various processors. I'm thinking that I'll need an i7 at the minimum, but I'm also considering a Natex dual 2730 board (powerful, but energy hungry) or a Rizen 7? What do you think?

Hey, got it working! The problem was the location of the GeoIP.dat file, it defaulted to /usr/share/GeoIP/GeoIP.dat so I created /config/geodata, changed the config, and manually downloaded the data

How would I configure this with the Plex server running on a different physical machine? What would I put for the path to /logs?

In looking at my network settings, I see that 'Enable Bonding' is set as Yes, even though I only have a single NIC. Is this correct? The bonding mode is set for active-backup.