misterbeetz

The old NordVPN container seems to have stopped working for me so I managed to transition to the new Nordlynx container. One thing that is bugging me though is that the icon for the docker container is not getting populated like it should. Instead I am just seeing a grey question mark. The old NordVPN container apparently was doing this as well over the past few months. Is anyone else seeing the same behavior? Is there a fix? EDIT: I should mention that the easiest way for me to get the private key was through MacOS. I initially tried to get it using an Ubuntu VM and I was running into too many issues. Here is the video I followed in case anyone would like to do the same:

In the meantime I found another option which is by using a docker container to run the IPMI Java viewer applet. With this approach one can avoid mucking up their own desktop in order to get this abomination to work. A preconfigured docker for this task already exists and I was able to confirm that it works for my setup: https://github.com/solarkennedy/ipmi-kvm-docker In this instance the console output is complete, meaning that I can see all the messages that Unraid produces during startup which is useful for troubleshooting a hung (and headless) system: Now this makes me wonder why the SOL (serial-over-lan) approach only shows up to the boot menu options and stops once Unraid starts the boot process... : Maybe someone will be able to point out what I am missing here. The SOL approach is much faster and cleaner so it would be nice to use that method instead of relying on docker containers and abandoned Java applets...

Is anyone here familiar with getting Unraid to redirect console output using SOL (serial-over-lan)? I built my system awhile back with an Asrock E3C224-4L mobo with the hopes that the included IPMI would make it easier to maintain as a headless setup. Recently I finally got the IPMI to work however this mobo was designed to use Java applets as a means to view that console output and those frankly have been a nightmare to try to get working on a modern desktop without tripping over a myriad of security issues. Along the way I stumbled across an alternative approach by using ipmitool and SOL to view that output: https://www.truenas.com/community/resources/how-to-use-ipmitool-sol-with-asrock-motherboards-alternative-to-jviewer.51/ So far it has been working great however at the moment I am only seeing the bios side of things, meaning that if I boot the server while viewing the redirected output using SOL/ipmitool then I only see the bios related messaging and the boot menu options. Once the boot countdown starts and Unraid boots then there is no further output that I can see. I have been combing through the forums and unfortunately I have not found much on this topic. The best I could find is one thread that discusses something similar albeit using a locally connected null modem cable: https://forums.unraid.net/topic/61027-guide-how-to-access-your-unraid-console-via-a-serial-port/ This thread also has some overlap: https://forums.unraid.net/topic/26551-supermicro-ipmi-view-and-ikvm-setup-blank-kvm-terminal-solution/#comment-244508 Between these two threads I have tried various combinations of appending " ... respawn:/sbin/agetty -L ttyS0 ... " or " ... respawn:/sbin/agetty -L ttyS1 ... " to /etc/inittab however nothing seems to have changed. Any help here would be much appreciated. For reference here is the out output for dmesg | grep tty: [ 0.142976] printk: console [tty0] enabled [ 0.433035] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A It appears that the SOL console redirection settings on my motherboard mention a COM1 and a COM2. My understanding is that COM1 is meant more for a locally connected serial cable while COM2 is meant more for SOL redirection. COM2 is what I currently have enabled and it allows me to view the bios messaging on boot up. What confuses me however is how COM1 and COM2 are supposed to correlate to ttySO and ttyS1 in Unraid. What I have read so far suggests that the dmesg output should be mentioning a ttyS1 but I am not seeing it....

Thank you for clarifying, this is great information. To wrap this up I am going to reference the comment that inspired me to start this thread for my own informational purposes. Suppose you encounter someone outside of these forums who is familiar with Unraid and has used it previously. Suppose they come along and say the following: "[you can safely use the faulty memory in your Unraid system going forward] as memory is not used for any RAID activity, so unless you are mounting this as non volatile cache disk I can't see any of your data damaged or compromised " What would your response be in that instance? Are they possibly getting mixed up with a different raid-like system where such a statement could be true?

Thanks for the response. The server crash aspect would certainly be a concern. Suppose however that in this (hypothetical) instance the server appears to be consistently stable and is not crashing. Would there still be an increased risk in data corruption on the protected array as a result of the faulty (non-ecc) memory module?

I am currently in process of building an additional Unraid server out of spare parts and noticed that one of the two memory modules that I intended to use is failing memtest. I have heard conflicting opinions on this issue as to the type and severity of the risks associated with using such a failed module regardless with Unraid. Can someone who is knowledgeable on this topic be able to comment on these risks? For example would the chances of file corruption increase on the protected array in this scenario? For reference the memory I have in mind is of the non-ecc variety. One 8gb sticks fails memtest while the other 8gb stick passes memtest. Recently I have heard comments that I should be able to use both sticks of memory with Unraid without causing an increased chance of file corruption on the array. Is that true?

I just stumbled across something called RetroNAS recently. It's an open source project to allow people to have an easier means of streaming their game backups from a centralized server to various game consoles & retro systems with network capability. I personally love this idea since I think it is a better alternative to buying a larger storage media for each individual console or system. Keeping storage at the console level also generally means having no parity protection which is a bummer. I think the key selling point of RetroNAS is to simplify the setup of the various tools and protocols required to facilitate the communication between server and the various game consoles/systems however many of these protocols are older and insecure. In this instance I think that keeping something like RetroNAS containerized would be preferable. At the moment there is a lot of interest in getting this packaged up as a docker container for use on systems such as Unraid, QNAP, Synology however the developer for RetroNAS does not have personal experience with such systems. Does anyone know how feasible it would be to make this as a container for Unraid? For reference here is a link to the project on github along with a video introduction by RetroRGB: Github: https://github.com/danmons/retronas Youtube Video:

Interesting! I need to educate myself on this. Thanks again for looking into it.

Thank you again for the response. I am not sure if I can explain it to the level of detail that you are looking for but it is a tool that extracts the contents of .iso image files so that they can be run on a modified game console with a custom dashboard. I am not a programmer or anything but I don't think that this would be considered a script. It's a little piece of software written in C. I grabbed the source from the github repo (https://github.com/XboxDev/extract-xiso) and compiled it to run on Linux 64 bit using the instructions on the repo main page. Hopefully I understood your question correctly.

Thank you for the response. Here is the result: -rwxrwxrwx 1 app users 61400 Jun 16 03:17 /output/extract-xiso

Is anyone here using event scripter? I am trying to make a script that will run a unix executable upon download completion however Jdownloader is giving me an error that it does not see the executable. Here is the basic script I am trying to test (the unix executable is "extract-xiso" and is located in the output directory): var extract = "/output/extract-xiso"; var file = "/output/test.iso"; callSync(extract, file); extract-xiso is designed to extract the contents of a .iso file however I get the following error when I test run this script: "java.io.IOException: Cannot run program "/output/extract-xiso": error=2, No such file or directory" Does anyone have an idea on what I might be doing wrong? I have confirmed that extract-xiso is exectuable as I can execute it directly from Unraid terminal.

I am going to put this out out there for posterity for any folks who have a similar question. I ended up buying two different docks however only one of them present the serial number of the drive. Thanks to a tip from SpaceInvaderOne in one of his videos I can confirm that the Sabrent EC-DSK2 seems to do the job properly: https://www.amazon.com/gp/product/B07415KV63/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 Unfortunately prior to that I was unaware of this serial number issue and ended up buying a unit that does not properly present HD serial numbers. This one happens to be the StarTech SDOCK2U33EB: https://www.amazon.com/gp/product/B00KILQOG0/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 My only gripe is that the Sabrent does not also have eSata capability however I guess I can live without that. Hopefully this information may be of some use to others in the future.

Is there a recommended model list somewhere that we can refer to for docks/enclosures? Or perhaps could you recommend a model? I would like to get a dual-bay toaster style one with USB. If it had USB + esata then that would be even better.

Thanks! Worked like a charm.

Got a funny error with updating the Plex docker after going from 6.1.9 to 6.2-rc3... anyone know how to fix this? IMAGE ID [latest]: Pulling from limetech/plex. IMAGE ID [6ffe5d2d6a97]: Already exists. IMAGE ID [f4e00f994fd4]: Already exists. IMAGE ID [e99f3d1fc87b]: Already exists. IMAGE ID [a3ed95caeb02]: Already exists. IMAGE ID [ededd75b6753]: Already exists. IMAGE ID [1ddde157dd31]: Already exists. IMAGE ID [8d7d45a813c4]: Pulling fs layer. Downloading 100% of 771 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [eeb36e73ebd8]: Pulling fs layer. Downloading 100% of 117 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [9c89f037a839]: Pulling fs layer. Downloading 100% of 564 B. Verifying Checksum. Download complete. Extracting. Pull complete. TOTAL DATA PULLED: 117 MB Error: layers from manifest don't match image configuration

Thanks Squid! I have narrowed it down to the Sickrage plugin that I have. I have also determined that the destination IP is one of the lesser known usenet trackers that I have enabled to search from. Oddly enough the packets seem to go through fine when the source IP is that of the unraid machine. They don't go through though when the source IP is 172.17.0.4 ... The only difference I see with the 172. packets is that they are TCP-RA rather than TCP-S. The other trackers I use do not trigger this behavior. Any ideas why source IP would flip flop like this?

Just a quick question for the unraid wizards out there. My router setup allows me to track and block unapproved network connections and I see that there is one curious source that attempts outgoing connections on a regular basis from my unraid machine to the same IP in Europe. Normally I would expect the source IP to be the one I had assigned to the unraid box during setup ( i.e. 192.168.x.x) however the source IP in this case is always 172.17.0.4 I currently have a 6.1.6 setup with a handful of dockers (CP, SB, Plex etc), but no vms. Given that I am not a networking/IT guru... Does anyone know of a way that I can dig deeper and find from where these attempts are coming from?

So I recently have gotten the itch to beef up the security on my network using OSSIM/OSSEC. In order to make this more effective I should install the agent software on all client machines and servers. Has anyone here put OSSEC on their Unraid box before? I've been spoiled by the dockers and plugins so its been awhile since I have installed something manually on Unraid. I encourage everyone to take a look at OSSEC if you are unfamiliar with it. It a great way to gain visibility of security related events in your network. Once installed OSSEC reports security events back to a centralized server (Alienvault, OSSIM, Security Onion etc.) so you can keep tabs on all machines on the network. Some examples of what OSSEC does: - integrated log analysis - file integrity checking - Windows registry monitoring - centralized policy enforcement - rootkit detection - real-time alerting and active response On top of that OSSEC is free and open source. Here are some links for further reading: en.wikipedia.org/wiki/OSSEC ossec.github.io/

So PMS version 0.9.12.8 is the latest public release as of August 7th. I am restarting the limetech docker however it is not updating ... all it does is remain at 0.9.12.4 ... I'm confused. Edit: So deleting the docker and reinstalling made it go to 0.9.12.8 as expected ... not sure what happened there.

Great success on the ZM docker! All feeds run in HD as expected. Thanks for your hard work!

I also had some issues when switching over. You may want to try a new local config directory and start fresh. This is what ultimately worked for me...

From within the docker tab make sure you click "update repositories" next to the search box. I didn't see the new stuff until I did that.

I seem to have trouble getting this new ZM docker started. I wiped the config folder clean but no luck. It basically never starts so I don't get a log to see what is happening. Is this one confirmed to work with rc5? (I haven't tested it with rc4 yet. I will be away for the next few days so I will try again when I come back.)

Any luck with that ZM docker? I'm ready for another round of testing

This thing is really cool. I just got it working. I guess the trick here is to realize that pfsense typically sends out those logs to a specific port by default however the docker suggests a different one which is probably smart. I should also mention that graylog is another amazing docker that can be used to capture logs from pfsense in addition to anything else you would want (desktop syslogs, unraid main syslog etc.) It's in sparkly's beta repo.