guruleenyc

My docker setup and logs attached:

Thanks for pointing that out; I first checked this docker menu and in the community apps section for this app and there was no link to the unraid thread and support link points to http://www.crushftp.com/support.html , which noted a discontinued support forum: Also I searched the unraid site and found other CrushFTP app posts about issues, so I posted in the same area as those.

I just installed CrushFTP and the only thing I changed was the webUI port from 9090 to 9191 and the webUI will not load. I do not see any errors i this dockers log either....Any ideas?

I noticed as today that my pre-existing speed limits for uploads are no longer enforced. Is this a known issue from a recent update?

I'm trying to get the Wazuh virtual appliance working as a Centos vm. I've extracted the VMDK and mounted it in a new vm. But it boots up and then hangs at a log mount error after a disk io error. Centos, Q35, sata Anyone have any ideas? Sent from my SM-N960U using Tapatalk

THANK YOU! Following these steps exactly got me passed the import of Wazuh VMDK "kernal panic fatal error'. It is now booting! :-) Now onto configuring it hopefully.

Good morning all! When I attempted to start this docker today, it would not start with this error in the logs: Removing docker/image and reinstalling it fixed it for now. But is this going to come back? I generally leave the docker stopped and only run it when I'm doing scans.

Thank you for making this available.

Greetings! I did a quick search and did not come across anything; I currently monitor unRAID using the Grafana/InfluxDB using this dashboard https://github.com/gilbN/theme.park#graforg. It does a very nice job for Docker CPU and RAM usage monitoring. Is there a similar solution for monitoring VM performance running on unRAID?

Upgraded from 6.7.0 with no noticeable issues. Thank you!

So for me the issue is only with Organizr docker. If I restart Organzr the issue goes away temporarily. Any idea what the long-term fix might be? The Organizr docker log in unraid UI shows no issues. But the log in the Organizr webUI shows: "OMBI Connect Function - Error: cURL error 7: Failed to connect to 172.16.1.5 port 3579: Connection refused [Execution Time: 01.30s | 1308ms]" UPDATE: after restarting Organizr docker all seems fine for a few days now.

This just happening on my unraid 6.70 a few days ago, before that it was fine. Any fix for this?

Greetings all! I am noticing that my Sonarr docker is averaging 60% cpu usage, but all other dockers average only 0-2%. I do not use any remote SMB paths in Sonarr and its also pinned at 1 cpu core like all my other related dockers. Any tips/tweaks to address this?

I just successfully upgraded from 6.6.7 to 6.7 with 3 vm's with multiple NIC's passed-through and approx 20 dockers. THANK YOU! Sent from my SM-N960U using Tapatalk

I searched, but can't seem to find a solution to the webUI not responding in a browser on port 5000. I edited the proper .pem file and followed above install instructions. I am not sure what I am missing...?

When I try to go to the webui of Influxdb docker on port 8083, I get page is not working/404 in Chrome. How do I get around this to set retention policy?

Thank you for this tip! Mine looks like this now: append vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream,multifunction iommu=pt vfio-pci.ids=8086:105e initrd=/bzroot

This works method works very well for me:

I followed this guide and it was on point! http://tinyurl.com/yygmajs9 Thank you @panzerschreck !!!

@thomas Thank you!!!! I del the SophosUTM 9 VM and rebuilt it as generic Linux, machine type: i440fx-3.0, increased hdd to 30G sata and changed VM settings interface model type: "<model type='e1000-82545em'/>" in form view after creation. The VM is up and running with once NIC/br0, now I need to see what I am going to use as a WAN NIC for it.

So the problem has not yet returned and I have not changed anything other than rebooting the 2x it occured after approx. 24hr and starting back up a Win2012 VM. Uptime 4d 21h and log is:

I am also seeing this error and I am on unraid 6.6.7 and just use Ombi site-conf file. All appears to be working though, but I am concerned about performance and security. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

Update: I decommissioned my unraid VMDK and went bare metal. Pleased with added performance and Unraid's VM capabilities. This thread can be closed.

I have a similar problem with an APC Smart-UPS 2200 tower model using serial cable, but I see correct stats, date/time in bottom of page UPS details section. In unraid it is set to APCSmart. Any idea or fix for this? UPDATE: I fixed this by going to /dev and performing a 'ls -la', then looked for serial device. Mine was /dev/ttys0. I added that for Device and restarted apcupsd and now I am good! Thank you @guru69

I am now seeing this as well. The only workaround for me so far was a reboot of unraid. I have tried the extra parameter in adv docker settings, but it threw an error on my docker and I had to reinstall the docker. The middle gauge was 100% and all dockers and VM's were hung. Current uptime 1d 37h.....