Zack Pollard

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Zack Pollard's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hey, wanted to add my own experience to this as I am having a very simlar problem and don't want to raise a duplicate bug report. I am trying make the unraid web UI accessible to docker containers by including the docker0 interface in the Include Listening Interfaces section, I do this so I can make the web panel accessible externally behind a second layer of auth for protection, as well as automate some other bits and pieces. On reboot, I experience the same issue as OP, I must remove and re-add the interface to the list in order for it to actually apply this setting. A fix for this would be appreciated, if you need any other information just let me know!
  2. Starting the server without any plugins works fine, so i'm wondering if there's an easy way to test all the plugins without having to do many... many reboots
  3. Hey, I'm upgrading my server to 6.7.2 and i'm having problems with it not being able to start up properly. Everything worked fine on my previous version (6.6.7). Upon startup, it makes it most of the way through the boot up and then I see the following errors (see image below). Has anyone seen something like this before? Cheers for any help people can give!
  4. Will have a look into that later, for now i've reverted to 6.6.7 and got it booting again. Will investigate plugins later and see if I can single one out
  5. I managed to extend the console to get some more lines (albeit a bit squashed) and this is what I now have, does anyone have any idea what's going on here?
  6. So, I downloaded the 6.7.0 zip and installed it again, and getting the same error. Could this be to do with plugins? I did update all of them to their latest version before doing the install.
  7. Well that should be a fun time, this is running in a datacentre, was a lot of fun to get it installed in the first place Will give it a go...
  8. Updated from 6.6.7 to 6.7.0 this morning and rebooted the server. The server never came back up and upon inspecting the screen output I can see the following (however cannot scroll to get more information): I'm not sure what's broken and what the next steps are but it seems to me like a bug with the updater as it's now not in a bootable state after this update was performed.
  9. I agree, and run both of these tools. However I still believe it's useful for light users of docker to have a tool that provides them with a simple overview of the container, which this would if divided by the pinned cores.
  10. Could just make it configurable in docker settings, or just put it in the help section on the page.
  11. Yea I think this makes the most sense for the reasons you mentioned. Yea that would be ideal but unsure how easy that'll be considering that unraid don't provide support for isolation in the panel currently (although I hope they do soon). This would be great though if it could be done for container's that aren't pinned :)
  12. Also dividing it by system cores or pinned cores, which makes more sense? Or provide the option for both? I'm unsure which would be more useful really
  13. So a further update on this, going to be submitting it as a bug report. It seems this may affect more people than just me, but they may not realise it. I've narrowed it down to only the latest version of unRAID causing this bug. There's a similar (although slightly different) issue over at coreos seen here https://github.com/coreos/bugs/issues/2457 when using the same kernel version as 6.4.3 uses. 6.4.2 does not have this bug so for now i'll be reverting back to that and submitting a bug report with all the information I have on this issue to the core team.
  14. On further investigation using iperf to measure the connection between this server and another one in a nearby datacentre, the server can pull the full gigabit speeds. Unsure if iperf might be multithreading the download which could help with that. Also attaching diagnostics from just after running a wget of https://www.feral.io/test.bin which when booted into the debian recovery OS yields 110MB/s download, however only yields 14MB/s download on unRAID. maeve-diagnostics-20180725-0504.zip
  15. So just setting up my third unRAID server and i'm having some very strange issues regarding network speed. Using a gigabit NIC which is displaying as gigabit in the panel and when testing on debian it can pull the full gigabit from two different file servers on the internet. However, when running inside unRAID, it only manages to pull 350Mbps from one file server, and 150Mbps from the other. I eventually put this down to an issue with the realtek drivers as apparently realtek has already been a bit of an oddball in unRAID, so I installed an intel NIC and have the exact same problem. I have no idea what is going on and am out of ideas. If anyone has any of their own ideas please let me know and I will try them. Similarly if you need any logs or diagnostic information tell me what to provide and I will. Thanks for any help you guys can provide!