Jump to content

unevent

Members
  • Content count

    852
  • Joined

  • Last visited

Community Reputation

26 Good

About unevent

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Ohio

Recent Profile Visitors

904 profile views
  1. unevent

    [ 6.6.0-rc4 ] NFS crashes

    I use NFS with ubuntu and also on unRAID between a Nextcloud VM and a share for data folder. Only time I had a crash like what you describe is when removing a share or creating a share while also dorking with the share folder on the cache drive via telnet/ssh. Ended up having to reboot to get SMB and NFS shares back. If not doing that, how are you mounting the shares in ubuntu?
  2. unevent

    access docker UIs via DNS

    For static DHCP to work you need a static MAC address to associate with the IP. Once you have static MAC assigned to a Docker you then assign the Docker a fixed IP as mentioned above in the Docker config page. In your router, set up a static DHCP map for the MAC/IP combo and give it a hostname and associate with whatever is used for DNS server on your router. To set a static MAC for each container I just set whatever each running container currently had for MAC address as the permanent then restarted the container. You can determine the MAC address of a container in a few ways. Easiest way is to use unRAID terminal at the top of the unRAID GUI (or console, telnet, etc.) issue the following command, replacing the bracketed text with the Docker container name: docker inspect <container name or id> |grep MacAddress|tr -d ' ,"'|sort -u I run Linux on another PC so another method is after assigning the Docker a fixed IP in the Docker config restart the container and then ping it from your Linux PC then do "arp -a" from a terminal to see the MAC. Once you have your fixed IP and MAC address to use, go to the Docker configuration and turn on the advanced view. In the 'Extra Parameters' box add --mac-address=<container_mac> ...replacing the bracketed text with the MAC address reported from the docker inspect command or arp -a used above (ex: --mac-address=02:02:02:02:02:02). If you have other commands in the that box just use a space to separate. Then procede to your router to set up a static DHCP map and register the static map in the router DNS. I use pfSense so almost fall-down easy. Go to DHCP Server, add a static map, enter the IP and MAC address and a desired hostname. Save and Apply. If not already done, under DNS Resolver make sure "Register DHCP leases in the DNS Resolver" is ticked. I use the Resolver, if using Forwarder (why?) Google is your friend, but probably same/similar. I use 6.5.3 unRAID. Earlier versions (like 6.3.5) you can use Pipework to accomplish the same thing by specifying MAC/IP combo in the command added to the Extra Parameters box for pipework method. After all that, you can access your Docker using the hostname you assigned. (ex: sabnzbd:8080) instead of using IP:port.
  3. unevent

    USB suspend

    I see some oddities in the log. Have some cables/power cords loose? Sep 12 04:10:56 Server apcupsd[3365]: Power failure. Sep 12 04:11:00 Server apcupsd[3365]: Power is back. UPS running on mains. Sep 12 05:55:33 Server kernel: usb 2-1.3: USB disconnect, device number 4 Sep 12 05:55:33 Server kernel: usb 2-1.3: new low-speed USB device number 8 using ehci-pci Sep 12 05:55:33 Server kernel: hid-generic 0003:051D:0002.0005: hiddev96,hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 1500 FW:601.3.D USB FW:1.5] on usb-0000:00:1d.0-1.3/input0 Sep 12 05:55:40 Server apcupsd[3365]: Communications with UPS restored. ... Sep 12 12:08:13 Server kernel: e1000e: eth0 NIC Link is Down Sep 12 12:08:14 Server ntpd[1640]: Deleting interface #2 eth0, 192.168.1.20#123, interface stats: received=123, sent=124, dropped=0, active_time=59418 secs ... Sep 12 12:08:25 Server apcupsd[3365]: Power failure. Sep 12 12:08:25 Server apcupsd[3365]: Power is back. UPS running on mains. Sep 12 12:08:26 Server apcupsd[3365]: Power failure. Sep 12 12:08:27 Server apcupsd[3365]: Power is back. UPS running on mains. Sep 12 12:08:41 Server kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx ... Sep 12 12:09:33 Server kernel: e1000e: eth0 NIC Link is Down ... Sep 12 12:09:35 Server apcupsd[3365]: Power failure. Sep 12 12:09:40 Server apcupsd[3365]: Power is back. UPS running on mains. Sep 12 12:10:01 Server kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx ... Sep 12 13:21:56 Server kernel: usb 2-1.3: USB disconnect, device number 8 Sep 12 13:21:56 Server kernel: usb 2-1.3: new low-speed USB device number 9 using ehci-pci Sep 12 13:21:57 Server kernel: hid-generic 0003:051D:0002.0006: hiddev96,hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 1500 FW:601.3.D USB FW:1.5] on usb-0000:00:1d.0-1.3/input0 Sep 12 13:22:04 Server apcupsd[3365]: Communications with UPS restored. Sep 12 13:22:05 Server apcupsd[3365]: Power failure. Sep 12 13:22:05 Server apcupsd[3365]: Power is back. UPS running on mains.
  4. unevent

    USB suspend

    Port your diagnostics file, located in the GUI - Tools - Diagnostics.
  5. unevent

    USB suspend

    Checked mine and none have suspend enabled so I would agree it is disabled by default. Lots of Google hits to be found with communication issues/commlost errors with solutions that vary depending on the cause. What UPS and UPS monitor are you using and the setup configuration?
  6. unevent

    Sad to see ...

    Just a passing comment, the jitterbug theme takes some getting used to. Not sure if different browsers render the site differently, but looks like my grandma's jitterbug phone. Not complaining as I am here for the content, but 80% on Firefox 62/Linux with 24" 1920x1080 brings it in line with most other forums. I like the black, the font/size is what I notice.
  7. unevent

    Working mumble server

    The .ini file is not brought out to appdata, it is located within the container in the '/etc/' directory. So you have to edit it every time you start/restart the container. Coppit version still works, but not available through CA unfortunately. I still have template though.
  8. Within Sab you have some settings that can tame the CPU and drive I/O demand. Look under Config - Switches for the Nice, IONice, and ExtraPAR2 parameters in the Post Processing section. The linked Sab Wiki will explain what they are and offer defaults to start with. If the ExtraPAR2 doesn't work (-t0), you can limit the number of cores to the Sab Docker to 1 or 2 as alternative.
  9. Probably best and easiest to set up a router in a multi-WAN config to load balance the two Internet connections. Can be done with pfSense and probably some higher-end consumer routers that market as such or those that can run multi-wan tomato or equivalent(?) dd-wrt firmware. PfSense probably has the best documentation to do such a task and will probably give you finer balancing controls. You won't be able to get a since connection that is 220Mbit wide, rather it will work in a round robin scenario with each new connection in concert with your load balance controls (weights and rules).
  10. unevent

    Plex Hardware Transcoding on AMD help please

    AMD GPU on Windows only last I heard. Intel CPU with Quick Sync on most platforms. edit: https://forums.plex.tv/t/amd-for-hw-transcoding-or-intel-nvidia-only/234695/5
  11. unevent

    [DOCKER] Pipework

    I believe pipework is just a shell script. Pipework is not as popular these days due to Docker including more network support in their later versions. I still use it, but I am on 6.3.5. All my Dockers have their own IP accessible to/from anything I want. I do think going virtual machine will get you what you want and be a lot easier. Rather simple to do in Virtualbox, but getting that running on unRAID is not a simple click and go process. KVM should support what you want to do, but my experience with it is limited since it has limitations in the unRAID implementation that prevent me from using it over virtualbox for my use case. That link I posted in the other thread had instructions for a Debian vm with four tuners and tvheadend. There are probably many more Google hits with instructions since the law change was recent and seems to be a rather big deal for those in Germany. Good luck.
  12. unevent

    multiple network interfaces for a docker

    If open to something besides a Docker, use KVM or Virtualbox which will make the networking easier. Virtualbox definitely will, but not standard with unRAID and the plugin has not been updated for latest build yet. I haven't messed with KVM much, but should have same/similar capability. Using a Fritz!Box 6490 as Tuner for Tvheadend
  13. unevent

    [DOCKER] Pipework

    Might work with a patch like the link below shows: Support assigning multiple IP addresses to one interface · Issue #166 ... What is use case, if I may ask? Might be other/better ways to accomplish.
  14. unevent

    I need a Plex transcoding beast!

    Might want to find out why it is transcoding and see about reducing the transcode requirements for your library.
  15. unevent

    UPS Help

    Suggest taking your numbers and plugging them into the size/runtime calculators at APC, Cyberpower, Tripp-Lite, etc. and see what it recommends for you. Stick with a sine wave output UPS or one with sine wave output for use with PFC power supplies for best experience/performance.