lutiana

Members
  • Posts

    27
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

lutiana's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Awesome container, just found it and giving it a spin as a replacement for Plex. Some questions about the docker though, it looks like it only exposes the http port to the network, but none of the others. I am giving the container it's own IP and would like to use HTTPS to access it, but I am unclear on how I expose that port (8920) for clients to connect. I added it to the docker, but it does not show up and the connection is denied when I try to connect. I also want to open up the client discovery port (UDP 7359) so that my TVs and other such devices can find the server and make the setup easier. I edited the Docker, added the ports, matched their settings to the one already defined port and this did not work. So there is a step or something I am missing.
  2. Well I mean, I figured that, but what is the exact path that is in? Or does that vary from install to install?
  3. Is there a particular reason for this? I ask out of curiosity more than anything.
  4. Thanks! I installed the plugin, and created the script. I assume that I can put the authorized_keys file in the same place as the script and it won't be deleted or lost at a reboot? Also, how do I schedule this to run at boot? The only cron options seem to have to do with the array startup and spin-down.
  5. I have another server setup that I would like to do some daily backups of. It supports backing up via SSH. So I went through and setup the /root/.ssh/known_hosts file with the public key from the other server and it was all working great. But then I rebooted unraid and to my surprise the setup was completely gone and my backups started failing. So is there a way to make this change persist through reboots?
  6. I tried to look it up again, but most of what I found was years old (circa 2011) or referred to live migrating VMs from one host to another. So I decided to give this a go, but first I figured I'd delete the libvirt.img file (again, for like the 10th time). But this time I decided to turn off VM support, delete the downloaded ISO and the .img file. Then for the hell of it, I rebooted. When it came back up, I turned on VM support, and this time it started without issue. This is odd, since I did all of this two weeks ago with no luck, though maybe not in this exact order. For future reference, is there a way to get more detailed logs from libvirt on unraid?
  7. I was only running one before, it was a Ubuntu 18 VMs for DNS and DHCP. So this not coming back up caused some major issue and some very unhappy family members while I threw substitutes in place for it. I have not tried this, but it would be quite difficult to do, as that IP/subnet is no longer routable on my network. I am also not too sure what this would prove either. If it works, then that would imply there is a config file somewhere that needs tweaking, and if it does not, well then it tells us nothing really. I rebooted the server multiple times. I then disabled the VM engine, deleted the IMG file and re-enabled it, to no avail. I went digging through the configs to see where the port mapping was (but did not change anything), nothing mentions port 440. So I pulled the reports and read through them. Googled the error that comes up, with little success (there is *possibly* a RHL/LibVirt bug related to this, but I don't recall the date on that article and did not really understand the thread it was in). And then I posted here and on the FB group. Thank you for the apology. It is possible that the IP change was co-incidental. Though the timing would imply it's not. When I did change the IP I had to go in and change the internal subnet for Docker as it overlapped with my desired subnet. This was a simple change in a config file. No idea if that could be related to the libvirt issue or not, but I figured I'd mention it. Other than that, the rest of the system appears to be 100% functional (including my dockers). To get the log below, I turned off VM support, then clicked delete on the /mnt/user/system/libvirt/libvirt.img file. Then enabled it and clicked apply. 2020-05-21 00:11:03.848+0000: 12388: info : libvirt version: 5.10.0 2020-05-21 00:11:03.848+0000: 12388: info : hostname: Deepthought 2020-05-21 00:11:03.848+0000: 12388: error : virNetSocketNewListenTCP:440 : Unable to bind to port: Cannot assign requested address
  8. I tried that, no luck. How do I get help with this? No one here is answering, no one on FB has an answer and putting in a ticket with Unraid directly just results in crickets as well.
  9. Am I seriously the only one to experience this? There is really no one out there that can help me out?
  10. Here are the anonymized diagnostics. deepthought-diagnostics-20200521-1512.zip
  11. For the record there are no dockers installed that are using port 440. lsof -i -P -n | grep LISTEN Shows that there is nothing listening on port 440 on the server as well. So it does not appear to be a port conflict. The libvirtd.conf file in /etc/libvirt-/ shows that the listening IP is set to 127.0.0.1 I am not really sure where to go from here.
  12. Ok, found the libvert logs, here is the issue: 2020-05-20 00:47:26.603+0000: 9951: error : virNetSocketNewListenTCP:440 : Unable to bind to port: Cannot assign requested address So my questions are: 1. Why is this suddenly happening? 2. Why can it not bind to port 440? If something else is using it, what would that be (none of my dockers are using that port)? 3. How do I change this port to something else?
  13. This was working just fine until I changed the IP on my unRAID box. When I go to turn on the VM support I get this in the log: May 20 15:40:07 Deepthought emhttpd: shcmd (222): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 May 20 15:40:07 Deepthought kernel: BTRFS info (device loop3): disk space caching is enabled May 20 15:40:07 Deepthought kernel: BTRFS info (device loop3): has skinny extents May 20 15:40:07 Deepthought root: Resize '/etc/libvirt' of 'max' May 20 15:40:07 Deepthought kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 May 20 15:40:07 Deepthought emhttpd: shcmd (224): /etc/rc.d/rc.libvirt start May 20 15:40:07 Deepthought root: virtlockd is already running... May 20 15:40:07 Deepthought emhttpd: shcmd (224): exit status: 1 May 20 15:40:07 Deepthought emhttpd: shcmd (226): umount /etc/libvirt Are there any other logs I can look at to get a sense of why libvirt won't start?