wayner

Members
  • Posts

    343
  • Joined

  • Last visited

Everything posted by wayner

  1. And unRAID has a plugin to help manage the UPS.
  2. Is the data from 2013 or is that just the date of the original blog post?
  3. Thanks Bob - I will try that when I get a chance. Even with this I haven't really been having issues. I did have a crash or two when the system was first built a year ago but it has been pretty stable since then. The system went down one other time on Dec 30 but I am not sure if that was a crash or if something else happened. I was thinking that I didn't have any PCI cards but I think I do have a FireWire card to use for changing channels on my STBs. I think it is the older PCI rather than PCIe is that matters.
  4. The USB is from a Asus P8H67-M Evo Asus motherboard and has an i5-2500K CPU. The USB chipsets are: ASMedia® USB 3.0 controller : 2 x USB 3.1 Gen 1 port(s) (2 at back panel, blue) Intel® H67(B3) chipset : 12 x USB 2.0 port(s) (4 at back panel, black, 8 at mid-board) I am not sure which ports I am using but I am pretty sure it is the USB 2.0 ports. I do have two Hauppauge HD-PVRs plugged in as I use this system as a SageTV DVR/media server with the SageTV docker and the LibreElec DVB edition of unRAID. But I never plug things in or out, but it is possible that the HD-PVRs may go up or done that could cause it to behave as if I new USB device was plugged in.
  5. Did you ever fix this. I get this error message on my system although I am not sure that it is causing any issues. I had this under 6.3.5 and now under 6.4.1. On my monitor it also gives the Disabling IRQ 16 message. Feb 3 19:14:57 Hoylake kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Feb 3 19:14:57 Hoylake kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 4.14.16-unRAID #1 Feb 3 19:14:57 Hoylake kernel: Hardware name: System manufacturer System Product Name/P8H67-M EVO, BIOS 3602 10/31/2012 Feb 3 19:14:57 Hoylake kernel: Call Trace: Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: dump_stack+0x5d/0x79 Feb 3 19:14:57 Hoylake kernel: __report_bad_irq+0x32/0xac Feb 3 19:14:57 Hoylake kernel: note_interrupt+0x1d4/0x225 Feb 3 19:14:57 Hoylake kernel: handle_irq_event_percpu+0x39/0x3f Feb 3 19:14:57 Hoylake kernel: handle_irq_event+0x31/0x4f Feb 3 19:14:57 Hoylake kernel: handle_fasteoi_irq+0x8c/0xf3 Feb 3 19:14:57 Hoylake kernel: handle_irq+0x1c/0x1f Feb 3 19:14:57 Hoylake kernel: do_IRQ+0x3b/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: RIP: 0010:ip_sabotage_in+0x2b/0x31 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffff88061f203a60 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff9e Feb 3 19:14:57 Hoylake kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000101536f4c Feb 3 19:14:57 Hoylake kernel: RDX: ffff8805fe8a2090 RSI: 00000000fffffe01 RDI: ffffffff8150ba23 Feb 3 19:14:57 Hoylake kernel: RBP: ffff8805637c0e80 R08: 0000000000000001 R09: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: R10: ffff88061f2039a0 R11: ffff880602c150a0 R12: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: R13: ffff88061f203aa0 R14: 0000000000f00008 R15: ffff8801107ffae0 Feb 3 19:14:57 Hoylake kernel: ? ip_finish_output2+0x278/0x2c2 Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: ip_rcv+0x2f2/0x346 Feb 3 19:14:57 Hoylake kernel: ? ip_local_deliver_finish+0x1b8/0x1b8 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x6ba/0x733 Feb 3 19:14:57 Hoylake kernel: ? ip_output+0xc4/0xcf Feb 3 19:14:57 Hoylake kernel: netif_receive_skb_internal+0xbb/0xd0 Feb 3 19:14:57 Hoylake kernel: br_pass_frame_up+0x12d/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_port_flags_change+0xf/0xf Feb 3 19:14:57 Hoylake kernel: br_handle_frame_finish+0x429/0x459 Feb 3 19:14:57 Hoylake kernel: ? ipt_do_table+0x55f/0x587 [ip_tables] Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_hook_thresh+0x93/0x9e Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing_finish+0x268/0x27a Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? nf_nat_ipv4_in+0x21/0x68 [nf_nat_ipv4] Feb 3 19:14:57 Hoylake kernel: br_nf_pre_routing+0x2d8/0x2e8 Feb 3 19:14:57 Hoylake kernel: ? br_nf_forward_ip+0x32c/0x32c Feb 3 19:14:57 Hoylake kernel: nf_hook_slow+0x37/0x96 Feb 3 19:14:57 Hoylake kernel: br_handle_frame+0x2a0/0x2d3 Feb 3 19:14:57 Hoylake kernel: ? br_pass_frame_up+0x13a/0x13a Feb 3 19:14:57 Hoylake kernel: ? br_handle_local_finish+0x31/0x31 Feb 3 19:14:57 Hoylake kernel: __netif_receive_skb_core+0x463/0x733 Feb 3 19:14:57 Hoylake kernel: ? napi_gro_receive+0x42/0x76 Feb 3 19:14:57 Hoylake kernel: ? rtl8169_poll+0x49e/0x4bc [r8169] Feb 3 19:14:57 Hoylake kernel: process_backlog+0x8c/0x12d Feb 3 19:14:57 Hoylake kernel: net_rx_action+0xfb/0x24f Feb 3 19:14:57 Hoylake kernel: __do_softirq+0xcd/0x1c2 Feb 3 19:14:57 Hoylake kernel: irq_exit+0x4f/0x8e Feb 3 19:14:57 Hoylake kernel: do_IRQ+0xa5/0xbb Feb 3 19:14:57 Hoylake kernel: common_interrupt+0x98/0x98 Feb 3 19:14:57 Hoylake kernel: Feb 3 19:14:57 Hoylake kernel: RIP: 0010:cpuidle_enter_state+0xe0/0x135 Feb 3 19:14:57 Hoylake kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffad Feb 3 19:14:57 Hoylake kernel: RAX: ffff88061f220900 RBX: 0000000000000000 RCX: 000000000000001f Feb 3 19:14:57 Hoylake kernel: RDX: 000014814bafc212 RSI: 0000000000020140 RDI: 0000000000000000 Feb 3 19:14:57 Hoylake kernel: RBP: ffff88061f228600 R08: 000043fc5a01fd81 R09: 0000000000000018 Feb 3 19:14:57 Hoylake kernel: R10: ffffffff81c03ea8 R11: 0000000000000048 R12: 0000000000000001 Feb 3 19:14:57 Hoylake kernel: R13: 000014814bafc212 R14: ffffffff81c59138 R15: 000014814baf9ec5 Feb 3 19:14:57 Hoylake kernel: ? cpuidle_enter_state+0xbb/0x135 Feb 3 19:14:57 Hoylake kernel: do_idle+0x11a/0x179 Feb 3 19:14:57 Hoylake kernel: cpu_startup_entry+0x18/0x1a Feb 3 19:14:57 Hoylake kernel: start_kernel+0x3ea/0x3f2 Feb 3 19:14:57 Hoylake kernel: secondary_startup_64+0xa5/0xb0 Feb 3 19:14:57 Hoylake kernel: handlers: Feb 3 19:14:57 Hoylake kernel: [] usb_hcd_irq Feb 3 19:14:57 Hoylake kernel: Disabling IRQ #16
  6. I have it in bridge mode but I also had to forward UDP on port 3478 to deal with the STUN error. But that may now be fixed in the docker template. That said - when I upgraded to 6.4.1 on Saturday and update the firmware on my UAPs I noticed some STUN errors but they seemed to go away on their own. I may try switching to br0 mode and giving it its own IP address as that may negate the need to worry about ports as much. And then you will have fewer worries about port conflicts.
  7. I think it is fine the way it is, except I hate where there is support for multiple dockers that have nothing to do with each other in one thread.
  8. Does anyone else find that this plugin provides inconsistent results that are nowhere near what you get when you do a "manual" Speedtest? My "rated" service is 250/20. When I run speedtests by going to the web page I generally get results of approximately 320/21. But with this plugin the results are WAY lower. I run this daily at 6am when there should be very little traffic on my LAN or local node. My download speeds over the last few weeks have ranged from 22 to 284 Mbps. The average is 167Mpbs. That just doesn't seem right.
  9. Which one - this one by fanningert or the cheesemarathons one?
  10. Actually it turns out I am in the wrong thread anyhow - the support thread is actually here as I am using cheesemarathons docker:
  11. Presumably this is a poorly designed docker as others allow you to make config changes by changing config files in the appdata folder. I guess I will just blow away this docker and use an alternative.
  12. OK, then how do I edit the port in Cloud Commander as I would like to just use port 80. Strangely there are no files in the /appdata/cloudcmd folder - every other appdata folder has files in it.
  13. Yes - I already have an existing config.gateway.json file to set up OpenVPN server on my USG. I was just wondering if it is possible to do this DNS forwarding option through the Controller software as Unifi keeps expanding the functionality available through the web UI.
  14. Here is the Docker run command. @CHBMB - if the port mappings are irrlevant then does that mean that you can't change (for example) the http port for an Apache docker from 80? Or would you have to do it in the config files internal to the docker? root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='CloudCommander' --net='br0' --ip='192.168.1.82' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'TCP_PORT_8000'='80' -v '/':'/UNRAID':'rw' -v '/mnt/user/appdata/cloudcmd':'/root':'rw' 'coderaiser/cloudcmd'
  15. This docker does not seem to actually use the port numbers entered in the docker config. I am using this in unRAID 6.4.1 and I am using a network type of br0 and I have given the docker its own IP address of 192.168.1.82. I have set the port to 80 but I can only access the UI at port 192.168.1.82:8000. Shouldn't I be able to access the web UI at port 192.168.1.82:80?
  16. Oh, I forgot to ask initially - is there a way to enter this via the Unifi Controller software or does it have to be done via the CLI?
  17. I have a USG router and I had to enter these commands. The way that I did it was via an ssh session to the USG where I did the following commands: configure set service dns forwarding options rebind-domain-ok=/unraid.net/ commit save exit And it seems to work. But this setting will not survive a reboot of the USG. Is this a command that just has to be done once for the initial config or will this have to be redone upon reboot? And if so then I guess I will have to add it to the json config file.
  18. I love being able to assign dockers their own IP address in 6.4 - but how do I display the docker IP address on the docker page? I can see all of the port mappings but now I don't have to worry so much about port mappings as I can just use port 80 for the web UI for all of my dockers if they are on their own IP. If it matters I am on the Azure UI.
  19. I just happened to click on Edit Profile. I noticed that you can enter your username for MSN Messenger, ICQ and AIM. Are any of these services still alive? Is it 2001? Can I run these services in a docker in unRAID 6.4?
  20. The forums were "redone" a little under a year ago and it seems that this broke many/most/all of the links to posts in the old forum style.
  21. Nice to see some Led Zep in the unRAID error messages!
  22. I think I have a P5B mobo in one of my systems, but that has to be about a decade old now - I think it was release in 2006. If you are just using the system for file storage then you will likely be ok, but if you want to use it for VMs and run a bunch of dockers then you might want to bite the bullet and buy something newer. Especially since I believe this only supports up to 4x2GB of DDR2 memory. But do you really want to build a file server that you hope to be using for a long time with a 10 year old motherboard?
  23. Thanks - I am using Letsencrypt in the Letsencrypt/nginx docker for external access through reverse proxy.