rorton

forgot to mention, looking at my auto backups done within the app, they stopped some time in 2019 - so I think the corruption has been there for a good while

hi, yep, that works perfectly. At the moment, I have managed to install the 'older' docker container (5.13.32) and point it at my data and its working OK. My only problem is backups now. Every time I try to back up in the app - it fails. I can't seem to run 5.14 with my app data, so my logic was, work on 5.13, get it backing up, then build a new 5.14, and import the backup. I think I have corrupt db.

still struggling with the above, ive tried to remove the docker container, selected remove image also - then re added while pointing at my existing app data, and still the same problem with tomcat

got an issue today with the container, can't get to the web page: I get - HTTP Status 404 – Not Found looking at the log: _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [

I have a new version of LibreNMS which is an OVA file this time, and trying to get it running as a VM. As I understand it, the OVA is like a tar file, so I untarred the ova file, which gave me and OFV, and the vmdk image. -rw-rw-rw- 1 5 daemon 1.1G Apr 28 05:43 librenms-centos-7.7-x86_64-disk001.vmdk -rw-r----- 1 5 daemon 171 Apr 28 05:44 librenms-centos-7.7-x86_64.mf -rw-r--r-- 1 root root 1.1G May 14 16:03 librenms-centos-7.7-x86_64.ova -rw-r----- 1 5 daemon 6.6K Apr 28 05:43 librenms-centos-7.7-x86_64.ovf I tried to create a CENTOS vm,

id like to do similar, I have it running in a VM at the moment, if you get it running, be great to know how!

Ahh ok thanks. I did wonder if that happened. No point me doing what I’m doing then :)

I have LIBRENMS monitoring my Unraid using SNMP. I was looking at the discovered ports, and I have a number of interfaces listed as vethxxxxxxx (7 characters) Assume these are for the docker containers, but wondered if there is a way to see which veth is assigned to which docker container, so I can lable these up in the SNMP software I show 7 veth interfaces, but have 11 docker containers - 8 set to bridge and one of these is stopped at the moment, so im assuming its these bridged containers? Just need to know which veth belongs to which docker contai

Try this .. https://help.ubnt.com/hc/en-us/articles/215458888-UniFi-USG-Advanced-Configuration Once the contents of the file has been validated, save it by naming it config.gateway.json and placing it under the <unifi_base>/data/sites/site_ID directory stored on the Controller.

I use Mac OSX, and running 6.8 Unraid - noticed a strange thing today - if I click on the log icon on the menu bar, a new window pops up which asks me to authenticate using the new Unraid logon window. Once authenticated, I see the Unraid gui again. If I click on the log icon in this new window, it then shows me the logs. Only happens in the Safari browser - chrome works fine.

im on 5.12.35 now via the docker upgrade, is 5.11.50 the latests one you can go to? Either way, 5.12.35 seems OK

looks ok now - I'm getting no cert errors any more

I'm getting an ssl error when browsing the forum too

Downloaded an appliance image of Zabbix network monitor from https://www.zabbix.com/download_appliance I have the qcow2 image in my VM directory in a subdirectory called zabbix. Ive then tried to create a new VM, using Ubuntu as the template - xml below. The VM starts, but I can't seem to get a VNC connection to it, logs don't show any errors, so not really sure where to look? Log and XML for the vm are attached, I have another Centos VM running, and that seems ok, plus Windows 10 and OSX. vm.log vm.xml

have a read of this.. https://unix.stackexchange.com/questions/408308/why-are-vms-in-kvm-qemu-called-domains