CS01-HS

Members
  • Posts

    475
  • Joined

  • Last visited

Everything posted by CS01-HS

  1. The ordering bug (?) only affects containers with no group assignments. Regardless, you should group these. Where container B depends on container A: without groups: A is stopped for backup which may cause errors with B, before B is stopped for backup with groups: B is stopped, then A is stopped, then both are backed up, then A's started, then B's started
  2. That's how I had it initially: But I haven't used this script in years (I eliminated the USB drive) so much may have changed. If it works, it works!
  3. Re: Warnings for non-existent volumes: There's the xml template, or is that backed up even if the container's skipped? That and consider the case of a container that doesn't use volumes: We set it to skip A subsequent version does use volumes We won't know not to skip it until it's too late Backup Order In the new version with Backup type set to stop, backup, start for each container For grouped containers: They're stopped in reverse of Start order (good) They're backed up in reverse of Start order (fine either way) They're started in Start order (good) For un-grouped containers They're stopped, backed up, started in reverse of Start order (bug?)
  4. Oh, I didn't realize. I was going off the debug output in test mode. I tried a real run (now with full paths) and it works. Thanks!
  5. File-exclusion works as expected but folder-exclusion only excludes the folder itself, nothing under it. e.g. given the folder structure: MyShare/KeepOnCache/ File1.txt File2.txt And this entry in the exclude file: /mnt/cache/MyShare/KeepOnCache the find command (with sed evaluated) look like this: > find "/mnt/cache/MyShare" -depth | grep -vFx "/mnt/cache/MyShare/KeepOnCache" /mnt/cache/MyShare/KeepOnCache/File1.txt /mnt/cache/MyShare/KeepOnCache/File2.txt So File1.txt and File2.txt are not excluded from mover. Is that intended and if so what's the point of folder-exclusion?
  6. Okay let's set that aside. Exact match (-x) means folder exclusion can't work because while the folder will match none of the files within it will.
  7. I noticed folder exclusion using the File list path option stopped working. Enabling test mode I see this in the find command (where my exclude file is exclude.txt) grep -vFx -f <(sed 's/\/*$//' '/boot/extras/mover_tuner/exclude.txt') I don't see how this can work with the -x option: -x, --line-regexp Select only those matches that exactly match the whole line. For a regular expression pattern, this is like parenthesizing the pattern and then surrounding it with ^ and $. Even files in exclude.txt won't satisfy the exact match unless they're prefaced with the cache path, e.g. /mnt/cache/sharename/file.txt vs simply sharename/file.txt, which used to work. Am I missing something?
  8. Yes. By default I think only subtitles save to the library directories but you can disable that. And consider this to synchronize watch state between the two: (It's not in the app store so you have to install manually) https://github.com/ArabCoders/watchstate But backup your watch states beforehand because a misconfiguration could reset it.
  9. In my case the half a dozen times it happened were all triggered by SMB operations. Never happened in any other case and since the new implementation where cache-only shares bypass shfs (and the majority of my SMB use is cache-only shares) it hasn't happened since.
  10. I didn't see it mentioned (maybe my search was insufficient) but it'd be handy if a share's recycle bin were emptied automatically when "free" dropped below a certain value or %, in case of emergencies. I'm in the process of standardizing my media library with unmanic so lots of churn, which made me think of it. I could do it with a simple user-script but that only solves it for me, and it's not as clean. Something to consider if you end up with too much free time!
  11. If I'm reading this right: one of the two connectors may offer 4 ports from the JMB585.
  12. I've fixed it (until the next reboot) with a symbolic link: ln -s /usr/local/bin/move /usr/local/sbin/move Seems to be running properly but hasn't finished yet.
  13. Getting a strange error: Jun 13 15:02:32 NAS root: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 214: /usr/local/sbin/move: No such file or directory Which makes sense because move is in bin, not sbin. which move /usr/local/bin/move It's a simple fix but I wonder if it indicates something more serious if I'm the only one seeing it. age_mover was last modified May 23: ls -l /usr/local/emhttp/plugins/ca.mover.tuning/age_mover -rwxr-xr-x 1 root root 23309 May 23 09:01 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover* My plugins are updated/running 6.12.0-rc8 EDIT: I see the age_mover in this post also references sbin. Huh. EDIT 2: It appear all scripts in /usr/local/emhttp/plugins/ca.mover.tuning reference sbin/move, which doesn't exist. Maybe the recently-released RC8 moved it from sbin to bin.
  14. Similar problem with 9p (which I use for a VM) in that it's not transparent. Still I'd appreciate some way to override it - I have a share that was exclusive in rc6 and now because of one subdirectory mounted over NFS (that worked fine) no longer is. Sure I can hardcode paths but the biggest problem - that I access the share from my Mac over SMB where every access risks triggering an shfs bug that takes down the array – is difficult to work around. Worst case I'll disable NFS and mount it some other way.
  15. 6.12 offers a partial solution with cache-only shares bypassing shfs (if you can restructure your workflow to use them.)
  16. If I remember right 127* doesn't work, you have to use the LAN IP. I've run mine like that for years. I also have these tweaks in config/go: # Put syslogs in system/logs (web ui only allows share root) cp /etc/rsyslog.conf /etc/rsyslog.conf.orig sed -i -e 's/\/mnt\/user\/system\//\/mnt\/user\/system\/logs\//g' /etc/rsyslog.conf # name logs by hostname instead of IP sed -i -e 's/FROMHOST-IP/FROMHOST/g' /etc/rsyslog.conf # Apply changes /etc/rc.d/rc.rsyslogd restart With the corresponding change to logrotate (along with other tweaks) in a user script set to run At Startup of Array – for some reason they didn't work in config/go. #!/bin/bash # update logrotate with non-default syslog location cp /etc/logrotate.d/rsyslog.local /etc/logrotate.d/rsyslog.local.orig sed -i -e 's/\/mnt\/user\/system\//\/mnt\/user\/system\/logs\//g' /etc/logrotate.d/rsyslog.local # add compression sed -i -e 's/missingok/missingok\n compress\n delaycompress/g' /etc/logrotate.d/rsyslog.local # make sure log size doesn't exceed 10MB (setting to 10MB unintuitively allow up to 11MB) sed -i -e 's/size 10M/size 9M/g' /etc/logrotate.d/rsyslog.local # not sure this is necessary /etc/rc.d/rc.rsyslogd restart exit 0
  17. I didn't remake anything as far as I know. This morning I spotted and deleted a leftover NerdPack directory in plugins - I can't imagine I mistakenly cleared templates-user but the timing seems too close for coincidence.
  18. I compared the backup to the boot drive and the only difference is the missing user templates. Copied them over and all's back to normal. Strange.
  19. root@NAS:/boot/config/plugins/dockerMan/templates-user# ls -l total 0 root@NAS: Huh, well that explains it. As it happens I ran the new Appdata backup overnight and they're present in the flash backup... will investigate.
  20. I wanted to change a container setting but when I clicked edit the template was blank. Thought that was strange and a reboot might fix it – Apparently it's made it worse, now there's no edit option in the menu: Same behavior in Safari and FF so it's not a browser cache issue. Any ideas? nas-diagnostics-20230424-1411.zip
  21. I noticed in /boot/config/plugins a leftover directory from NerdPack, a plugin I'd uninstalled a while ago. It made me wonder if there's a standard method for cleaning up the plugins dir or the flash drive generally. A sort of "based on your settings here's a list files that by default shouldn't be there."
  22. I use it, great plugin. But because it stops my containers for about 15 minutes I only run it weekly. Even if you run it nightly, what I'm proposing would allow a simpler (2 click) up-to-the-minute-it rollback.
  23. Before updating sensitive containers I'll typically stop the container, tar up its appdata dir, then apply the update. This makes it easy to rollback in case something goes wrong. It'd be handy if this process were automated – present a Backup and Update menu option when an update's available, and Rollback and Delete Backup menu options when a backup's detected.
  24. Happened again, my first time with rc3. Failed creation of a new folder on a share from my Mac (possibly duplicate name) produced this in the log (I use syslog sever.) Apr 19 08:25:28 NAS emhttpd: read SMART /dev/sdd Apr 19 08:25:57 NAS emhttpd: read SMART /dev/sde Apr 19 08:34:54 NAS shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed. Apr 19 08:34:54 NAS rsyslogd: file '/mnt/user/system/logs/syslog-nas.log'[9] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Apr 19 08:34:54 NAS rsyslogd: file '/mnt/user/system/logs/syslog-nas.log': open error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Apr 19 08:34:54 NAS emhttpd: error: get_filesystem_status, 7380: Transport endpoint is not connected (107): scandir Transport endpoint is not connected Shares inaccessible. Had to stop everything and reboot. I have to treat every file operation over SMB as though it might take down the array. That's a serious inconvenience.
  25. I gave up on unraid time machine (I now use a time capsule) so my comment's not based on experience with the recent versions but it seems to me the later samba versions made MacOS less compatible generally – search doesn't work out of the box, folders don't always refresh when their content changes (which sometimes causes fuse errors that take down the array.) I'd be tempted to blame MacOS but I have an old Raspberry Pi running samba 4.9.5 that works just fine.