benyanke

But I can't access the web gui....

Update: even upon restarting, the web gui won't respond. emhttp is a running process still, however. What debugging info do I need?

Bringing down the whole system (including containsers and VMs) when only a secondary management interface is really unfortunate... I hope this can be remedied at some point. The whole reason I went for a linux based system is to avoid things like this. Is there any timeline or plans to set up the service properly so it can be restarted like a normal linux service?

So what do you do if everything is running normally and emhttp hangs? It happens more than occasionally. This is linux we're talking about here. It's silly to bring down a system to restart a daemon.

#!/bin/bash # Stop existing emhttp kill `ps aux | grep "/usr/local/sbin/emhtt[p]" | awk '{print $2}'` # Restart emhttp echo "Restarting web interface" /usr/local/sbin/emhttp & disown sleep 1; # Output process list to visually check if running ps aux | head -n 1 ps aux | grep "/usr/local/sbin/emhtt[p]"; I tried restarting emhttp with the above script (it was still running, but not responding). I then received the following syslog error. Jun 27 18:17:47 pius-server emhttp: unRAID System Management Utility version 6.3.5 Jun 27 18:17:47 pius-server emhttp: Copyright (C) 2005-2017, Lime Technology, Inc. Jun 27 18:17:47 pius-server emhttp: shcmd (2): mkdir -p /boot/config/plugins/dynamix/users Jun 27 18:17:47 pius-server emhttp: shcmd (3): mkdir -p /boot/config/shares Jun 27 18:17:47 pius-server emhttp: shcmd (4): mkdir -p /tmp/emhttp Jun 27 18:17:47 pius-server emhttp: shcmd (5): mkdir -p /var/local/emhttp/smart Jun 27 18:17:47 pius-server emhttp: err: device_by_name: device_by_name: (sdh) not found

/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint bind (b02afe12d7e2bd9ea08cae7ad3bdeecab9609f8278418a8fb71f9a1ad042c6b1): Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use.

When I try to forward port 53/tcp and port 53/udp to a container, it triggers the duplicate port protections. Is this a known bug, and is there a workaround?

When the host ports are entered, there really ought to be checking for host port conflicts dynamically, so that you don't need to build the image to find the conflict...

I have some VMs with a very specific XML configuration file, and occasionally, if I click the wrong menu, it'll get messed with by UnRaid. There's really no instance that a hypervisor should be automatically changing VM configurations on VMs, at least VMs which have been marked as "locked" somehow... otherwise I'll have to move off unraid for my more unique vms. Is there a current way to set a VM's config to 'locked' so that unraid will never touch it? If not, I'd like to add this as a feature request. This would be for VMs with especially nonstandard configuration in their XML.

I have an idea for better managing docker containers: groups or applications. Many times, a frontend app has multiple components, such as an app server and a database instance. If they could be grouped together, and perhaps even restarted together, it would clean up the interface.

Here: https://gist.github.com/benyanke/6782e6a050be88c4797b52518ac23f4b

I'm also using the LE image as a proxy. Any idea where to start looking? I'm really loving the dockerized nextcloud, but if I can't figure out why it's being slow and not logging in, I'm going to need to move elsewhere...

Like Mavarazo, I've been getting a lot of timeouts too, on the desktop client, davfs, and even in the browser. Was there a bad update pushed, or is there something else going on? Restarting the container, my DBMS, and even the whole server didn't work.

Amazing, I will check that out!

I'm also having problems with this. Many database services require the standard port, and I'd like to run more than one database instance, for security. Has anyone figured out how to get extra IPs for docker containers working?