Community Developer
  • Posts

  • Joined

  • Last visited

Everything posted by PeterB

  1. I have a couple of plugins which I created years ago, to run dovecot and mpop on my unRAID server. I say 'years ago' - the dates on the files are from 2012 - 2014! If I remember correctly that was when unRAID went to 64 bit! They have been running without change and without problem for eight years. Last night I upgraded to unRAID 6.11 and those two plugins no longer startup. The output is as follows: I have reverted to unRAID 6.10.3 and the plugins run again. Other plugins I have created still run in 6.11 What has changed in 6.11 and what do I need to do to make my plugins fully compatible? Documentation on the plugin system is still seriously lacking!
  2. Undoubtedly good advice. However, I'm intrigued that two of us should encounter the same (or similar) issue, in the same week with, presumably, two different docker containers implementing the same application.
  3. I've just encountered this problem - CUPS is filling the docker image file with lots of temporary files. I deleted all these temporary files and the docker image file immediately returned to normal usage. My CUPS docker is from gfjardim's repository, but is identified as 'beta'. However, the files are created at around one every two seconds, each file is 38993 bytes and contains a list of *Font lines, eg: *Font Oklahoma-Oblique: Standard "(001.005)" Standard ROM *Font Oklahoma-BoldOblique: Standard "(001.005)" Standard ROM *Font Utah: Standard "(001.005)" Standard ROM *Font Utah-Bold: Standard "(001.005)" Standard ROM *Font Utah-Oblique: Standard "(001.005)" Standard ROM *Font Utah-BoldOblique: Standard "(001.005)" Standard ROM *Font UtahCondensed: Standard "(001.005)" Standard ROM *Font UtahCondensed-Bold: Standard "(001.005)" Standard ROM *Font UtahCondensed-Oblique: Standard "(001.004)" Standard ROM *Font UtahCondensed-BoldOblique: Standard "(001.005)" Standard ROM *Font BermudaScript: Standard "(001.005)" Standard ROM *Font Germany: Standard "(001.005)" Standard ROM *Font SanDiego: Standard "(001.005)" Standard ROM *Font US-Roman: Standard "(001.005)" Standard ROM The docker container was created 9 months ago but I cannot believe it has been creating these files for 9 months. Does anyone have any idea how to stop these files being created? The following processes run repeatedly: root 10559 25 0 18:03 ? 00:00:00 /bin/bash ./run root 10564 10559 0 18:03 ? 00:00:00 /bin/bash ./run root 10565 10564 9 18:03 ? 00:00:00 python -u /usr/local/bin/cloudprint -a /config/cloudpri root 10568 31 0 18:03 ? 00:00:00 sleep 1
  4. Some time ago, I reported a problem where DelugeVPN fails to reconnect following extended Internet connection outage. Yesterday, due to a strong typhoon , we suffered an Internet outage lasting more than 24 hours, plus a short power outage. When the Internet connection returned, as I expected, DelugeVPN failed to start. Before restarting manually, I remembered to capture the container's log. It was rather short: I'm not sure whether this directly relates to the failure to reconnect following Internet outage, without rebooting, but this is clearly what happens if the container starts and the Internet connection is not working. This logged activity was at 08:03 - I captured that log more than ten hours later and there had been no further activity from the container. The Internet connection had been live for more than three hours by that time. Hope this helps.
  5. The minidlna daemon doesn't appear to be crashing - it still has process id 80 and has consumed 34 seconds of cpu time, and no indication in the log from the container.
  6. I've just noticed multiple occurrences of this message appearing in my system log: Nov 8 21:35:58 Tower kernel: minidlnad[9980]: segfault at 20 ip 0000559ed8d47167 sp 00007ffd969bc770 error 4 in minidlnad[559ed8d1d000+2b000] Does this indicate an issue withing this container, or is the message coming from somewhere else?
  7. I went back to address this issue when I had more time available. The cause of my issue is that the default /etc/group which is provided by unRAID v6.10 now includes dovecot and dovenull groups, hence my attempt to create these groups in my install script was failing. My solution, for the time being, is to delete these two groups within my install script, before I create my own. This does beg the question, though - are we about to see dovecot provided as an integral (or even optional) service within unRAID. If not, why have these groups suddenly appeared in the group file?
  8. I have an old plugin which I created years ago, to run the dovecot mail server. It still runs perfectly well under v6.9.2. When I just updated to 6.10.0-rc2, I found that dovecot was failing to start. The system log shows that the plugin install script is executed, then the next line shows "retval: 6". I'm not sure whether this retval relates to the installation script or to something which happens after the script runs. The install script is: <!-- Here is the plugin installation script. This script is run every time upon system start-up and/or when the plugin is installed. --> <FILE Name="/tmp/dovecot-install" Run="/bin/bash"> <INLINE> <![CDATA[ # include our config vars source /boot/config/plugins/dovecot/dovecot.cfg # if dovecot doesn't exist, extract the tarball if [ ! -e "/usr/local/sbin/dovecot" ]; then ( cd /usr/local ; tar -xf /boot/config/plugins/dovecot/dovecot-2.2.13-x86_64-1pb.tgz ; # chmod 755 /usr/local/var/run/dovecot/empty # chmod 755 /usr/local/var/run/dovecot/login ) fi # # Add the next two lines for unRAID 6.9.0 groupadd -g 500 dovenull useradd -M -u 500 -g 500 -s /bin/false -d / -c 'Dovecot null user' dovenull groupadd -g 501 dovecot useradd -M -u 501 -g 501 -s /bin/false -d / -c 'User for Dovecot Mail Server' dovecot ]]> Is anyone able to identify why the plugin doesn't start or, at least, what "retval: 6" signifies? Oh, I was also caught out when I found that the installplg command no longer appears to be present! I guess that this now has to be done through the web interface.
  9. Okay, so I've just downloaded/installed 6.10.0-rc2. Indeed, all my nfs shares now are automounted with NFSv4. One little problem - all my NFS shares appear on my Linux Mint machine as protected. I'm told that I'm not the owner and cannot write to the share. My shares are all set as public and I used to be able to write to them under 6.9.2/NFSv3. Why the difference in behaviour and how do I resolve this? UPDATE: Okay, false alarm (I think). I rebooted my Mint desktop machine and all appears to be okay now. Although the files are shown as protected, I can still write/delete.
  10. This is such wonderful news! I'll wait for the official rc2, but I'm getting excited!
  11. I've already been running 6.9.2 for some time and have just encountered this problem today - all containers are showing version as "not available" Is there a new fix?
  12. Are you able to provide guidance on installing/using this docker? I'm getting fed up with having to reboot my clients every time the unRaid nfsv3 craps out. I still don't understand why there is such resistance to implementing nfsv4 natively on a file server OS. Perhaps someone can create an unRaid version of this docker, and include it in Community Applications.
  13. Is anyone here still using CouchPotato docker? I find that it is a lot of the movies it offers to download are either 'Unknown' or totally the wrong movie. Until a few weeks ago, it was still working pretty well with just th occasional 'Unknown' being offered. For instance "Marksman, The (2021)" is offering a download entitled "Zack Snyder's Justice League (2021)". As far as I am aware, the only connection between those two movies is the release year. This makes CP rather useless - does anyone know how to fix it? I use RARBG and ThePirateBay as my main search tools, both with and without Jacket.
  14. HELP! I was trying to get binhex-couchpotato to connect through binhex-delugevpn once again. I made edits as described in Q24, but couldn't find the 'VPN_INPUT_PORTS' env var. I believed that I had to delete the delugevpn container and re-install it, and tha this would pick up my old settings again. However, now when I go to the unRAID 'Docker' page I simply see a never-ending hourglass and there is no delugevpn showing. Oh, and binhex-couchpotato always says 'rebuilding' under the version column. What do I need to do to get delugevpn back (with all my settings)? Edit: I managed to get into couchpotato settings and blank the 'Extra Parameters'. This seems to have fixed the hourglass problem. I now seem to be in a position to re-install delugevpn with my original settings .... I will carry on and see where I get to ....... Further Edit: Ah, but I still don't have VPN_INPUT_PORTS .... still stuck .... ... and no, I don't have a container version specified in the repository.
  15. 6.8.3 to 6.9.0 was over a year ... don't hold your breath!
  16. One of my private plugins requires certain users to be configured in the /etc/passwd file. I used to achieve this be ensuring that the required users were present in /boot/config/passwd and, during system startup, that file was copied to /etc. Since upgrading to 6.9.0, this passwd file copy no longer seems to be happening. I don't remember whether I performed the copy, or whether the standard system was doing it. Has something been changed which would account for this?
  17. Possible, but why have I not seen it happen before? It was running for a full ten hours immediately after the reboot from the v6.9.0 update.
  18. Hmmm ... weird! I've just stopped/restarted the CP docker, and the reads appear to have stopped!
  19. I have just upgraded to unRAID v6.9.0. It appears that CP is now keeping all my media drives spinning permanently with around 2k reads per hour on each drive. This wasn't happening previously. Does anyone have a clue as to why this is happening and, better still, how to prevent it?
  20. Thanks for the response. Yes, I do have directory caching enabled. Researching possible conflicts, but not found any information yet. UPDATE: It appears that this issue is being caused by the BinHex Couch Potato docker.
  21. Just upgraded from 6.8.3 to 6.9.0 today. Now, none of my drives are spinning down. Openfiles doesn't show anything open on the drives I would expect to see spin down, but something is reading from them (~20k reads on each drive, in a little under ten hours). Turbowrite is disabled (Data drives spun down: script not running, Write mode: unraid determined). How do I identify what is accessing the drives in question? Should I revert to 6.8.3?
  22. I've just (ten minutes ago) loaded the latest update, and the AutoAdd plugin seems to be working once again.
  23. Is anyone else using the AutoAdd plugin? It used to work a treat for me but, sometime recently, it has stopped recognising new .torrent files. I don't think I have changed any settings but, in any case, changing settings shouldn't stop it recognising new files entirely. It cannot be an installation problem since AutoAdd is a 'standard' plugin - part of the Deluge distribution. I would love to have it working again - any ideas/suggestions?
  24. So why does mine keep creating (corrupt) .torrent files?
  25. I must be missing something - for the life of me, I cannot see where/what to set to use magnets.