PeterB

This is what you were referring to:

I would support your sentiments. I have always been keen to be involved in testing - usually jumping in at around beta3/beta4. However, I have refrained from installing 6.2 because of the unreliability of Internet connections here in Philippines. beta/rc versions always come with a "government health warning" and any user who knowingly installs such a release cannot hold LT responsible for any untoward results. Also, the onus is on any user, who gets involved in the testing phases, to keep abreast of all developments and reports, and revert/update as necessary in order to protect their data. On the other hand, I also understand that Tom feels a moral responsibility, despite the warnings, to minimise any ill-effects, and with this mechanism in place he can reduce the risks and support commitments.

Not if you have an average of 2 power cuts a day (four in the last seven hours). It's almost a year since I had a completed parity check.

That was a lot later than I ditched my last one ... I think that was about a decade earlier. Well, to be fair, the hardware had sat under a desk for several years - the prompt for actually dumping it was my emigration to Philippines - I really couldn't justify shipping the very heavy, steel, 6u 19" case half way around the world. However, I did power it up before it left the house - it still booted and ran! This was using my own modified versions of CCP/Z, BDOS/Z and a bespoke BIOS. I often reminisce about spending GBP500 on a used 5 MB SCSI Winchester disk drive! I ditched everything related - I'm not planning on going back there!

At long last - acknowledgement that not everyone has a machine running Microsoft (or even Apple)! Surprisingly we've gotten only a couple requests for that over the last few years. Probably because most Linux users are technically savvy enough to perform the required operations manually. Whatever the stimulus, it's a welcome addition!

I often wonder whether Gary enjoyed his round of golf on that day!

At long last - acknowledgement that not everyone has a machine running Microsoft (or even Apple)! When can we expect a CP/M version ? Sorry, I ditched my last CPM-80 machine in 2007! Perhaps you mean CP/M-86? But, to be serious, figures suggest that there are more than 15M users running Linux on their desktop, worldwide. I find it hard to believe that there were ever 15M users of CP/M.

At long last - acknowledgement that not everyone has a machine running Microsoft (or even Apple)!

I have just followed that procedure on binhex-emby (twice, once with CA 2016.06.12, and then with CA 2016.06.13). The problem still persists (and I note that it also affects the Apps tab). Edit to add: Okay, it seems that a reboot was required. All is back to normal after this afternoon's powercut.

I removed, and re-added, the emby docker. The dates/times of the xml files in templates/binhex have updated, but the problem is still present. The reported lineno refers to the DonateLink element in every case.

I have started to see a number of warning messages appear at the top of my Docker tab which seem to be related to the binhex dockers. This may have started when I had a play with the Emby docker a couple of days ago. What I see is: Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/teamspeak.xml, line: 48 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sonarr.xml, line: 67 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sickrage.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sickbeard.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sabnzbd.xml, line: 61 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/plex.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/nzbget.xml, line: 56 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/moviegrabber.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/minidlna.xml, line: 51 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/madsonic.xml, line: 70 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/get-iplayer.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/delugevpn.xml, line: 111 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/deluge.xml, line: 71 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/couchpotato.xml, line: 63 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sabnzbdvpn.xml, line: 107 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/jenkins.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/emby.xml, line: 56 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/plexpass.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/tvheadend.xml, line: 61 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/rtorrentvpn.xml, line: 115 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Application Author / Repo Version Port Mappings (App to Host) Volume Mappings (App to Host) Autostart Log Now, I'm not using all of the dockers mentioned in the messages, so I presume that this is something fairly general (to do with your PayPal link?). I'm running unRAID v6.1.9, if that's relevant.

That's a shame - I liked having a less 'cluttered' main menu bar! I just spent ages looking for CA - even removed and re-installed, before coming to look here!

A quick play suggests that iso shares via nfs are now working correctly! Many, many, thanks for all your hard work on this!

Thank you sir - much appreciated!

Well. I'm guessing that is the reason I'm not seeing the iso file share exported. I can access the share via smb, but not via nfs, and it doesn't appear in the exports file: root@Tower:~# cat /etc/exports # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. "/mnt/user/Downloaded" -async,no_subtree_check,fsid=110 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/ISO Library" -async,no_subtree_check,fsid=120 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Karaoke" -async,no_subtree_check,fsid=111 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Movies" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Music" -async,no_subtree_check,fsid=102 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Photos" -async,no_subtree_check,fsid=103 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/ReadyTorrents" -async,no_subtree_check,fsid=116 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Scans" -async,no_subtree_check,fsid=121 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Series" -async,no_subtree_check,fsid=106 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/Torrents" -async,no_subtree_check,fsid=109 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/UMC" -async,no_subtree_check,fsid=105 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/UserHome" -async,no_subtree_check,fsid=112 172.22.1.12(sec=sys,rw) "/mnt/user/Videos" -async,no_subtree_check,fsid=104 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/appdataX" -async,no_subtree_check,fsid=117 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/cache_only" -async,no_subtree_check,fsid=114 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/dnsmasqX" -async,no_subtree_check,fsid=119 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/hide" -async,no_subtree_check,fsid=118 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/mysql" -async,no_subtree_check,fsid=108 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/tftproot" -async,no_subtree_check,fsid=115 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/xbmc" -async,no_subtree_check,fsid=107 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/docker" -async,no_subtree_check,fsid=220 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) root@Tower:~# and I do have "Enable NFS export?" set to "Yes" in the Unassigned Devices Settings. Do I need to create a script in order for the nfs share to appear? That isn't necessary for a physical drive to be shared - eg /mnt/docker I do find it confusing that I have to click the button "Add Remote SMB Share" in order to add a remote nfs share!

2. Fixed in next release. Ah, that's made it work! My ISOs are in a directory called "ISO Libraries", and I couldn't get anything to mount! One point, though - since disk shares are disabled by default, and there is some potential danger in having them enabled, could/should the default mount point be changed? Perhaps it needs to be made a configuration option? Ah, I see that it gets shared anyway, but only by SMB, (not nfs?)! You have to turn on nfs sharing in the Unassigned Devices settings. "Enable NFS export?"? I already have that set to "Yes". The mount point cannot be changed from /mnt/disks/. So it is necessary to set "Enable disk shares:" to "yes" (ignoring all the advice not to do so) in order to access an ISO over nfs?

2. Fixed in next release. Ah, that's made it work! My ISOs are in a directory called "ISO Libraries", and I couldn't get anything to mount! One point, though - since disk shares are disabled by default, and there is some potential danger in having them enabled, could/should the default mount point be changed? Perhaps it needs to be made a configuration option? Ah, I see that it gets shared anyway, but only by SMB, (not nfs?)! Edit: I've just tried to change the mount point, and the change doesn't stick.

Why do the system stats (Temps and fan speed) only appear on the footer of the Settings and Docker tabs, and not on any other? Edit: Okay, I've seen them appear on some other tabs now, but not yet on the Main tab. I'm not sure whether this is a new phenomenon - I'm sure that they used to be reliably present on all tabs.

I have exactly the same problem with the update again: plugin: updating: dynamix.file.integrity.plg watcher not running! +============================================================================== | Skipping package inotify-tools-3.14-x86_64-1 (already installed) +============================================================================== +============================================================================== | Skipping package b2sum-20130305-x86_64-1 (already installed) +============================================================================== plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.integrity.txz ... done plugin: bad file MD5: /boot/config/plugins/dynamix.file.integrity/dynamix.file.integrity.txz ... but there is no file in /boot/config/plugins/dynamix.file.integrity/ so what corrupt file should I be deleting? CA update ran okay immediately afterwards. I seem to have some problem which is related only to the file integrity plugin!

2016.02.20 version has installed okay, but I had already tried the uninstall/reinstall with 2016.02.19b, which hadn't worked. I'd even used wget to fetch the .plg and attempted a manual install - it failed whichever method I tried, suggesting, to me, that I was receiving a corrupt file every time. The only other thing which might have been a factor - the server had been rebooted in between, due to a power cut.

I have a problem updating to the latest version: plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.integrity.txz ... done plugin: bad file MD5: /boot/config/plugins/dynamix.file.integrity/dynamix.file.integrity.txz root@Tower:~# ls -l /boot/config/plugins/dynamix.file.integrity total 0 I removed the plugin and tried to reinstall from scratch: plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.integrity.txz plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.integrity.txz plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.file.integrity.txz ... done Warning: simplexml_load_file(): /tmp/plugins/dynamix.file.integrity.txz:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 Warning: simplexml_load_file(): ?7zXZ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 plugin: xml parse error

Yes, my docker image is on a device which is automounted by UD. The config folders are on a cache-only share. I didn't go digging very far but either removing UD dismounted the device with the docker image on it, or removing UD messed with some other resource which docker requires. Either way, the advice to not reboot needs to be reconsidered. That's not what I said - I said that one should be cautious if expecting that a reboot is not necessary. Indeed - so, again. dlandon's advice needs to be treated with caution.

I followed this procedure - as soon as I removed the old version of UD, my Docker vanished. There was no Docker tab on the main UI screen, CA told me that Docker was not enabled (I checked Docker settings, and that told me that Docker was enabled), and docker ps returned the following: root@Tower:~# docker ps Get http:///var/run/docker.sock/v1.19/containers/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS? After re-installing UD, I rebooted and docker came back. I would suggest that the advice that a reboot is not necessary should be taken with a great degree of caution. In any case, I'm not convinced that the remove/re-install was necessary - it appeared, to me, that the switch from gfjardim's version to dlandon's and already happened automatically, a couple of days ago, when an update was offered to me and it picked up a revision list with 24 entries. At that stage, the author information changed from gfjardim to dlandon.

I think that I was still using gfjardim's version of this plugin - after months of inacctivity (September 19, I think) I've just installed an updated with a whole raft of changes (24 entries in the change log). Which version should I be moving on with - and do I need to take any action in order to achieve this? Welcome back, gfjardim. I have been missing your very valuable contributions to this community.

To confirm what others have recommended - I also have been using my own domain name for several years, even though I have emigrated from UK to Philippines. Originally (in UK) I relied on my ISP to host my domain and mail server but, since 2011, I have been using 5quidhost - relatively inexpensive but very reliable. However, I also run a mail server on my unRAID box - I created plugins for dovecot and mpop. This allows me to keep archives of all my emails without paying for a large amount of online storage, allows me to access all my emails even if the Internet connection fails, saves on Internet bandwidth and gives faster response (Internet here, like the electricity supply, is slow, unreliable and expensive). At the moment I am running mpop once every five minutes to check for new emails at 5quid - one day I will have a look at the possibility of having 5quid push my emails to me.