Joly0

Hey @grtgbln I tried to install daps-ui and only get this in the logs: Skipping virtualenv creation, as specified in config file. [Main][2025-01-07 10:20:52,510][INFO] = LOG LEVEL: INFO Traceback (most recent call last): File "/code/main.py", line 24, in <module> db = Database(logger) File "/code/DapsEX/database_cache.py", line 13, in __init__ self.initialize_db() File "/code/DapsEX/database_cache.py", line 23, in initialize_db with self.get_db_connection() as conn: File "/code/DapsEX/database_cache.py", line 17, in get_db_connection conn = sqlite3.connect(Settings.DB_PATH.value) sqlite3.OperationalError: unable to open database file Updating group appgroup GID to 100 Updating user appuser UID to 99 Running main.py as 99:100 I do not have kometa and posters, so i removed the requirement for those paths and changed the uid and gid, but is that the reason it fails to start?

Hey, i think mover tuning plugin breaks the new feature "empty disk" When i run mover start -e disk2 |& logger & i get this output in syslog: Dec 12 00:14:16 Tower root: mover: started Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs unmount 'cache/backup' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs destroy 'cache/backup' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs mount 'cache/backup' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs unmount 'cache/filerun' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs destroy 'cache/filerun' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs mount 'cache/filerun' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs unmount 'cache/nextcloud' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs destroy 'cache/nextcloud' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs mount 'cache/nextcloud' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs unmount 'cache/safe' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs destroy 'cache/safe' 2>&1 Dec 12 00:14:16 Tower shfs: /usr/sbin/zfs mount 'cache/safe' 2>&1 Dec 12 00:14:16 Tower root: mover: finished Though when i run mover.old start -e disk2 |& logger & it works and empties the disk: Dec 12 00:19:31 Tower root: mover: started Dec 12 00:19:33 Tower root: move: /mnt/disk2/.... Success Dec 12 00:20:09 Tower root: move: /mnt/disk2/.... Success Dec 12 00:20:10 Tower root: move: /mnt/disk2/.... Success Dec 12 00:20:54 Tower root: move: /mnt/disk2/.... Success Dec 12 00:21:30 Tower root: move: /mnt/disk2/.... Success Dec 12 00:21:30 Tower root: move: /mnt/disk2/.... Success

Hey @ich777 @datarepos i have the same ugreen NAS but havent noticed this issue, though i have my ugreen now in a separate room that i rarely look into and i have just restarted my ugreen, therefore cant replicate this issue now. I will try to leave it powered on for a few days and will report back, if i notice the same issue

Hey guys, maybe some can help me. So i have purchased a green cell 2000va ups on german amazon. I installed the nut plugin and let it detect the driver. It suggested the "nutdrv_qx" driver, so i tried that first, but i noticed in the dashboard, that "Battery Charge" and "Runtime Left" were missing. So i switched to the second recommendation "blazer_usb". Now "Batter Charge" is shown aswell, but the "Runtime Left" is still missing. The detect function suggests a third driver "nutdrv_atcl_usb" but that is not to be seen anywhere on the selection. Should i try that driver and if so, how can i do so? Or is there another reason, why the runtime left is not showing up?

Btw, this has been resolved. The amp template should be visible again in the CA

I have requested to remove the dupliacte flag here you could react to it maybe to raise importance for this (maybe even ping squid)

Hey, the APP "AMP" in the Repository by "CorneliusJD" is no longer visible. I can see, that this repo is marked as a duplicate here https://github.com/Squidly271/Community-Applications-Moderators/blob/1e509047f02e05fbabbb5a357a766d84e50d56a8/Repositories.json#L611 I think this is an error, because the image thats in the CA and the now hidden repo use different images and different settings. They work quiet differently and also the now visible AMP image had a bug in its release and wasnt updated for over a year til recently. So i personally would prefer the AMP image from the CorneliusJD repo Also the Image by MitchTalmadge is the more "Official" one, compared to the one by ImageGenius

It looks like the repo has marked as duplicate and therefore is hidden https://github.com/Squidly271/Community-Applications-Moderators/blob/1e509047f02e05fbabbb5a357a766d84e50d56a8/Repositories.json#L611 I think this is a mistake

Any issue with the recently added tab in CA? I see every app is new, except all the language plugins. All entries in the CA are listed as add on "15.08.2024". I see entries that are months old on the first page of the recently added tab.

Hey guys, since the new version i receive this message now from fix common problems: Jul 5 04:47:30 Tower root: Fix Common Problems: Error: Old version of SSD Trim Schedule According to the changes i guess this has something to do with this: Added: Check for incompatible cron file created by Dynamix SSD Trim plugin But i dont have that plugin installed. How am i supposed to fix this issue now?

Hey guys, i might have found a bug. Not sure though. So i was trying to build this project: https://github.com/ZeppelinBot/Zeppelin/tree/b28ca170edc39ec2248801c50bb42c2d2411f5f5 using this documentation https://zeppelin.wiki/setup/operating-systems/linux-docker It is important to run git checkout b28ca17 after git clone command. I renamed the docker-compose.standalone.yml to docker-compose.yml and the .env.example to .env. I added a docker compose project to the cloned folder and configured the docker-compose.yml to be the newly renamed one. All looked good. When i started the project, i noticed, that somethign was odd and that it was trying to read the 3 other .yml files aswell. I also noticed, that the migrate container was not buioldign and running. I only got this fixed, after deleting all three additonal .yml files and leaving only the renamed docker-compose.yml behind. So i assume, there is some kind of bug in the docker-compose plugin, or in docker-compose it-self, that results in loading the additional .yml files (for whatever reason) and tries to run them or so. I am really not sure.

Thanks for the answer. Imo it makes sense, how its done atm according to your explanation, but i (and probably others) still think, that the script should be run as is and let the user implement their ways of signal handling using trap and such things. That would make that feature easier to understand and use in my opinion. I am not sure if most people know, that if you abort a background script, the script actually doesnt really "abort". Ofc changing that would be quite a hassle, but it makes the feature quite hard to use manually, when you have to run a long lasting command and want to interrupt it if needed.

I mean, if you run a script in foreground, you can close/stop it and the processes stop aswell and i would think that if you run it in background and you abort it, the same would happen. Atleast from searching this topic for this "issue" others seem to think the same. Abort should stop the script and the execution of any processes

I mean, that makes kinda sense, but why doesnt userr scripts "simply" run the scripts itself? Wouldnt that make more sense? Aborting would then send a sigterm/sigkill/whatever signal to the script, which the script could handle. Imo that would make way more sense, atleast imo

Yes, but this cant be intended behaviour. Why would you want to abort a background script, just for the processes in the background to keep running. Imo this doesnt make much sense. But maybe @Squidcan give his opinion on this and maybe clarify it.

@AmaneI really think something is bugged with the "Run in background" option. I have another very simple script that looks like this: #!/bin/bash # Define the target folder for the files target_folder="/mnt/user/filme" # Define the desired owner of the copied files desired_owner="99" # Add the paths to the files to be copied here file_paths=( ) rsync -zvvP --bwlimit=300 --partial-dir="$target_folder/.rsync-partial" --chown="$desired_owner" "${file_paths[@]}" "$target_folder" And when i run that in background and abort it, the rsync process just keeps running. So how am i supposed to stop it then?

Hey, thanks for the recommendation. I thought so aswell and tried that already, but as you can see in the screenshot, it doesnt work. If i abort the script, the command in the container is still bein executed:

If you havent found a solution yet, i would advice adding a volume from the containers /tmp directory to somewhere on your host

Hey guys, i have some issues running a script. The script connects to a docker container using docker exec and runs a command in it. But the problem is, that these commands take a very long time to run and i want the ability to stop them when needed. So i was able to rewrite it, so i can run it in foreground mode and it stops, when i X the window. But as soon as i run it in background mode and abort the script, the commands just keep running forever. Maybe someone knows why this is and here is the current version of the script: #!/bin/bash # Variables CONTAINER_NAME="LANCache-Prefill" # Function to clean up child processes cleanup() { echo "Cleaning up..." pkill -P $$ pkill -f "docker exec -u prefill $CONTAINER_NAME" kill `ps aux | grep "prefill --force" | awk '{print $2}'` exit 1 } # Trap termination signals to trigger cleanup trap cleanup SIGINT SIGTERM # Execute commands in Docker container sequentially docker exec -u prefill $CONTAINER_NAME /bin/bash -c "cd /lancacheprefill && ./SteamPrefill/SteamPrefill prefill --force" & PID=$! wait $PID docker exec -u prefill $CONTAINER_NAME /bin/bash -c "cd /lancacheprefill && ./EpicPrefill/EpicPrefill prefill --force" & PID=$! wait $PID docker exec -u prefill $CONTAINER_NAME /bin/bash -c "cd /lancacheprefill && ./BattleNetPrefill/BattleNetPrefill prefill --force" & PID=$! wait $PID # Clean up if the script finishes cleanup

Hey guys, how are the excluded folders working? I have this in my custom folders for exclusion ".Recycle.Bin, .filerun.thumbnails" (without the quotes) but today i got this in my logs Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/my-Pihole-DoT-DoH.xml is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/my-homeassistant.xml is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/my-AMP-Controller.xml is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/backup.log is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/my-AMP.xml is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/chuwi1-flash-backup-20240318-0000.zip is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/AMP-Controller.tar.zst is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/Pihole-DoT-DoH.tar.zst is corrupted Apr 3 11:49:42 Tower bunker: error: BLAKE3 hash key mismatch, /mnt/disk3/backup/.Recycle.Bin/Chuwi_Backup/ab_20240318_000001/config.json is corrupted Why are those files being checked? Shouldnt they be excluded?

Hey guys, could you try going into advanced mode while editing the container, remove both variables for nvidia devices and replace the argument in "extra paramters" with this "--gpus=all" That worked for me. If you guys get it to work aswell, i will update the template Atleast with these settings my gpu is used Also when i created that template, the settings where working, so looks like ollama changed something

You might be right, adding and testing all those webui´s is a hasle, but at the same time, not everyone can write a bash script. Also i think just a few here know, this method using the custom scripts exist or that your repo with custom scripts exist. Might be a good idea to add some kind of testing environment, so the scripts can be tested more or less automatically after a new release/commit

I have it in my fork already. I am quite close to creating a pr which adds webui-forge and also running all of the webui´s with amd gpus. If you want to test my fork, you can text me and test, if forge works