wirenut

Members
  • Posts

    201
  • Joined

  • Last visited

About wirenut

Converted

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

2332 profile views

wirenut's Achievements

Explorer

Explorer (4/14)

9

Reputation

  1. Well... thanks again. I removed the container, deleted the app data folder and installed fresh. The whole process took about 10 minutes to complete but it installed and is no longer showing update ready. I'll see how goes it as time passes. Attached is the info from the install command window if it may be of some use to you? And again, Thank You! binhex-krusader install 2024.03.18.txt
  2. Thanks for the suggestion, but its been there a few days with over 100 views showing and not one reply. I see you mention a couple posts up about a new build coming. I guess i will wait for that and see if it changes anything for me.
  3. I also have a docker that is persistent with this issue. I have posted in the docker support thread and was assured that the container is fine and this may be an unraid docker engine related problem and to post the issue there. I did this two days ago but have not yet received any feedback. Maybe my post details aren't clear? They are here if you wouldn't mind taking a look: Thanks in advance!
  4. I posted in the container support thread and was advised to post it here: Got notification docker auto updated overnight during regular schedule for this action. Then received fix common problems notice this morning there was a docker update available, checked docker tab and sure enough said there was. Manually updated, finished successfully. Still shows update available. Pulling image: binhex/arch-krusader:latest IMAGE ID [1269367198]: Pulling from binhex/arch-krusader. IMAGE ID [ba79b0a00404]: Already exists. IMAGE ID [014829145dc4]: Already exists. IMAGE ID [8981650a5ede]: Already exists. IMAGE ID [3e6f6e9c14bc]: Already exists. IMAGE ID [21c1cc086e6b]: Already exists. IMAGE ID [d61b27411559]: Already exists. IMAGE ID [6bed959144b4]: Already exists. IMAGE ID [867955bafe2a]: Already exists. IMAGE ID [af760b31737e]: Already exists. IMAGE ID [b91d01ffc1e9]: Already exists. IMAGE ID [b8db4f2655a2]: Pulling fs layer.Downloading 100% of 3 KB.Verifying Checksum.Download complete.Extracting.Pull complete. IMAGE ID [5f904db18c50]: Pulling fs layer.Downloading 100% of 1 KB.Verifying Checksum.Download complete.Extracting.Pull complete. IMAGE ID [c6b8e095478d]: Pulling fs layer.Downloading 100% of 684 MB.Verifying Checksum.Download complete.Extracting. TOTAL DATA PULLED: 684 MB Stopping container: binhex-krusader Error: Removing container: binhex-krusader Successfully removed container: binhex-krusader Command executiondocker run -d --name='binhex-krusader' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-krusader" -e 'TEMP_FOLDER'='/config/home/.config/krusader/tmp' -e 'WEBPAGE_TITLE'='Krusader' -e 'VNC_PASSWORD'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:6080]/vnc.html?resize=remote&host=[IP]&port=[PORT:6080]&autoconnect=1' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/krusader-icon.png' -p '6080:6080/tcp' -v '/mnt/user':'/media':'rw' -v '/mnt/cache/appdata/binhex-krusader':'/config':'rw' 'binhex/arch-krusader' bf494d6710cd0ba84e94b716483ae787bbb08c3aead77f316918569d68ccf692 The command finished successfully!
  5. Interesting, I have been away a few days and was looking to address this today based on binhex last response to me and saw your post. I tried manually again to see if i had same issue you describe, and it appears I do. @binhex my repository is correct as you directed to check, should I still post the issue at https://forums.unraid.net/forum/58-docker-engine/ ?? Pulling image: binhex/arch-krusader:latest IMAGE ID [1269367198]: Pulling from binhex/arch-krusader. IMAGE ID [ba79b0a00404]: Already exists. IMAGE ID [014829145dc4]: Already exists. IMAGE ID [8981650a5ede]: Already exists. IMAGE ID [3e6f6e9c14bc]: Already exists. IMAGE ID [21c1cc086e6b]: Already exists. IMAGE ID [d61b27411559]: Already exists. IMAGE ID [6bed959144b4]: Already exists. IMAGE ID [867955bafe2a]: Already exists. IMAGE ID [af760b31737e]: Already exists. IMAGE ID [b91d01ffc1e9]: Already exists. IMAGE ID [b8db4f2655a2]: Pulling fs layer.Downloading 100% of 3 KB.Verifying Checksum.Download complete.Extracting.Pull complete. IMAGE ID [5f904db18c50]: Pulling fs layer.Downloading 100% of 1 KB.Verifying Checksum.Download complete.Extracting.Pull complete. IMAGE ID [c6b8e095478d]: Pulling fs layer.Downloading 100% of 684 MB.Verifying Checksum.Download complete.Extracting. TOTAL DATA PULLED: 684 MB Stopping container: binhex-krusader Error: Removing container: binhex-krusader Successfully removed container: binhex-krusader Command executiondocker run -d --name='binhex-krusader' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-krusader" -e 'TEMP_FOLDER'='/config/home/.config/krusader/tmp' -e 'WEBPAGE_TITLE'='Krusader' -e 'VNC_PASSWORD'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:6080]/vnc.html?resize=remote&host=[IP]&port=[PORT:6080]&autoconnect=1' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/krusader-icon.png' -p '6080:6080/tcp' -v '/mnt/user':'/media':'rw' -v '/mnt/cache/appdata/binhex-krusader':'/config':'rw' 'binhex/arch-krusader' bf494d6710cd0ba84e94b716483ae787bbb08c3aead77f316918569d68ccf692 The command finished successfully!
  6. Same issue for the last two days. Is this an issue on my end or the update side? I am not sure how to troubleshoot this.
  7. Got notification docker auto updated overnight during regular schedule for this action. Then received fix common problems notice this morning there was a docker update available, checked docker tab and sure enough said there was. Manually updated, finished successfully. Still shows update available. any idea why?
  8. New build on my radar for this year. I've saved it in my wishlist and hope it's still available when I am ready
  9. Hmmm Looks like just what I am looking for also. If you pull the trigger, please make sure to leave your thoughts once you have it in hand.
  10. Have you looked at the 'mover tuning' plugin? I currently use it for this very purpose. If parity check is running, mover doesn't start.
  11. Hmmmm, Damn. it is and now have added Processes to kill before Array is Stopped: ssh,bash My error and not a bug, this is a good thing . Thanks ljm42!
  12. I am one who has had an unclean shutdown after upgrading. I followed the instructions for the upgrade to 6.12.3. I did have to use the command line instruction, upgrade went fine and server was up for 6 days, this morning i needed to reboot server. I spun up all discs I individually stopped all my dockers and my VM. I hit reboot button. it is about 4 hours into unclean shutdown parity check with no errors, log repeated this while shutting down: Jul 22 08:34:04 Tower root: umount: /mnt/cache: target is busy. Jul 22 08:34:04 Tower emhttpd: shcmd (5468228): exit status: 32 Jul 22 08:34:04 Tower emhttpd: Retry unmounting disk share(s)... Jul 22 08:34:09 Tower emhttpd: Unmounting disks... Jul 22 08:34:09 Tower emhttpd: shcmd (5468229): umount /mnt/cache Jul 22 08:34:09 Tower root: umount: /mnt/cache: target is busy. Jul 22 08:34:09 Tower emhttpd: shcmd (5468229): exit status: 32 Jul 22 08:34:09 Tower emhttpd: Retry unmounting disk share(s)... attached diagnostics captured from reboot. not sure what/why it happened. tower-diagnostics-20230722-0834.zip
  13. I've had syslog server set up for some time now and it has been doing its job just fine. I have recently made a change (approx 24 hours ago) to the settings to enable log rotation due to current log file size of 471,511,591 bytes and to see how it works. The rotation to a new file has not occurred yet. I though maybe making a settings change would enable the check but that didn't happen. What is rotation file size check schedule, daily, weekly or monthly?