xokia

I can recreate it after my latest batch of transcodes completes. But if the performance sucking "feature" is normal seems rather pointless.

If its normal it kills performance. I use handbrake on this machine and under normal condition HB would consume about 9GB of memory. With this setup HB was allowed 300MB of memory my transcodes slowed to a crawl. I am guessing swap disk was going crazy. Should probably just remove ballooning from the windows templates. It wont do what people want it to do. I've used this feature under proxmox and vastly different experience.

Thought I would share an issue I ran into recently. I have a windows11 and windows10 VM. When I set up the memory I set initial memory 4GB max memory 16GB expecting it to use more if it needed it. Well this does NOT work. At Idle on a fresh install of windows under task manager the machine was saying memory was utilized at 90% even though it showed 16GB of RAM available. Barely anything was running. This happened under both windows 11 and windows 10. It took me a while to even notice this. The machine ran hot under mild work loads bouncing off 90c. Also the performance was terrible. Once I set the initial memory to the same as max memory. This problem went away and it showed 8% memory utilization at idle. After changing this setting my cpu temp also went to 70c with cpu utilization at near 100%. I use this machine for transcoding. I went from 4-5FPS up to 20FPS. HUGE performance improvement.

So if you go one page back and look for my post I show how to configure this. It looks as though nextcloud also has an ngnix server installed which wasn't clearly documented. So you have to change the settings there to. I used a temp directory because I wanted to be able to upload very large files. Which if you dont use a temp directory it goes to RAM. Which is fine unless you are uploading massive files like me.

Yea that's what I assumed so what I have currently works. I uses DNS1 on the router to point to my adguards DNS inside docker. I have DNS2 (failover) pointing to a DNS provider outside my network. So when the system boots unraid gets DNS2 and is allowed to boot. once booted Unraid gets DNS1 which is the adguard DNS in the docker container.

at start up I get mv: cannot stat '/user/local/bin/mover' : No such file or directory Everything operates fine I just get this message at startup. I have tried uninstalling and reinstalling mover tuning no luck. How do I fix? create a soft link?

Be careful with cloudflare and your plex server. You can get banned if you use plex and their orange cloud under a free account. I have debated using cloudflare myself since they offer some nice additional security features. I only run nextcloud, homeassistant, and vaultwarden that are externally visible from outside. I have plex too but cloudflare wouldn't help with that. I have SSL setup through IONOS and SWAG proxy. Only port 443 and port 80 open with a redirect to 443. Hoping that's enough. Also have fail2ban enabled. 3 bad access attempts and the IP gets banned. I'd also like to figure out how to ban countries but havent figured out how to do that with out a paid account to DBIP or Maxmind. Cloudflare has that going for it. *edit* got DBIP and country ban working. Works as expected.

I have my unraid server behind a Asus router. The router DNS settings point to adguard running on my unraid server. There is an issue on the initial boot of the unraid server where the server has no DNS because adguard hasnt started. It seems to get stuck here maybe trying to check the license key? Not sure why it gets stuck but I assume its because it has no valid DNS and something is dependent on a valid DNS being available. If I enable DNS2 on the router to point to some valid DNS outside my network things boot fine. However I'd like unraid to use a bootstrap DNS initially and then switch over to the DNS it was assigned by the router, which points to a docker container running adguard. Possible?

trying to get fail2ban to work with swag and nextcloud. I can see my access attempts in /mnt/user/appdata/nextcloud/log/nginx/access.log However nothing in the log shows a fail or a success. I can see the IP its coming from but nothing about login success/fail /data/nextcloud.log -> nextcloud logging is not working /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php $CONFIG = array ( 'datadirectory' => '/data', . . 'tempdirectory' => '/nextcloud_tmp', 'theme' => '', 'loglevel' => 2, 'log_type' => 'file', 'logfile' => 'nextcloud.log', ); /data is a share on a disk so its not in my appdata root@88ecb2f1ef01:/# ls -l /data/nextcloud.log -rwxrwxrwx 1 abc abc 0 Nov 17 18:18 /data/nextcloud.log I resized the large file with truncate /data/nextcloud.log --size=0 -> after this it no longer logged data anyone know why logging is dead?

If I want to use a cache drive to transfer files I under stand this flow. Files hit cache drive first. Mover at some point later moves these files to HDD. All future access to those "moved" files will come from the HDD. Pretty much just speed up the initial data transfer. I have a second scenario that I dont know if it is possible. I want a frequently accessed file in cache. If the file is no longer accessed for some period of time it gets evicted to HDD. If another access to that same file happens I want it to move to cache again and new accesses to that file to happen from cache. -> Is this possible? I.e. use the cache drive like an actual cache? I have mover tuning installed but haven't been able to figure out how to make my second scenario happen.

one issue I had after downloading this container is I had a lot of errors in the nextcloud log file about richdocumentsscode I had to run occ app:install richdocumentscode in the nexctcloud terminal to fix it. ###################### Now my main issue which has been really annoying me. I am unable to upload larger then 1GB files via chrome web browser. If I upload larger then 1GB I just get "unknown error" in nextcloud. The only thing I have found is this https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html I've tried all of that and still no luck. I created a share that all 3 have access to nextcloud_tmp/ I can see the files in all 3 consoles. /mnt/user/appdata/nextcloud/php/php-local.ini memory_limit=2048M upload_max_filesize=70G post_max_size=70G max_input_time=6400 max_execution_time=6400 output_buffering=0 upload_tmp_dir =/nextcloud_tmp file_uploads =On /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php 'tempdirectory' => '/nextcloud_tmp', /mnt/user/appdata/swag/nginx/proxy-confs/nextcloud.subdomain.conf add_header X-Accel-Buffering no; proxy_buffering off; client_max_body_size 0; client_body_in_file_only on; client_body_in_single_buffer on; client_body_temp_path /nextcloud_tmp; fastcgi_request_buffering off; fastcgi_max_temp_file_size 0; ################# EDIT ####################### I think I finally figured it out. But maybe someone can explain it to me because I do not understand it. I have been trying to modify /mnt/user/appdata/swag/nginx/proxy-confs/nextcloud.subdomain.conf to make this work because swag is the proxy server. however after I modified /mnt/user/appdata/nextcloud/nginx/site-confs/default.conf # display real ip in nginx logs when connected through reverse proxy via docker network set_real_ip_from 172.18.0.0/12; real_ip_header X-Forwarded-For; # https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html#nextcloud-in-the-webroot-of-nginx # set max upload size and increase upload timeout: client_max_body_size 0; client_body_temp_path /nextcloud_tmp; client_body_timeout 6400s; fastcgi_buffers 64 4K; proxy_buffering off; fastcgi_request_buffering off; fastcgi_max_temp_file_size 0; add_header X-Accel-Buffering no; It started working as expected. How does modifying the nginx file within the nextcloud container solve this? I assumed this was just an example file? Does this build have its own nginx server?

I'd like to backup my plex_database and zip it monthly so if I lose my database I can restore to some prior time that would make recreating it easier. I run my plex database exclusively in cache so it has no protection. I know we have a utility for app data backup. Does a similar such utility exist we can point to a specific folder to back up?

is 1.32.6.7557 safe to update too? They had the fiasco that broke HW transcoding previously. Afraid to update now.

No.....If I set it to yes then I can click move now and it moves the files. If its set to no and I click move now nothing happens. Alternatively With it set like I listed above which is to move daily (with disable mover tuning set to no) exactly like pictured above. Nothing gets moved files just sit on the SSD. When I finish with my latest transcode I will circle back to this.

Not sure you follow the issue with mover tuning enabled, mover does not run. With "Disable mover running on a schedule" set to yes. I could get mover to run as expected.

This is probably an issue with my config. I downloaded mover tuning Even if I click Move now nothing happens it also does not run daily. If I disable "disable mover running on a schedule" and click Move now it will run mover. So it appears the issue is with mover tuning. These are the default settings when you download mover tuning. I must not be understanding something in mover tuning. What am I missing?

This is probably an issue with my config. I downloaded mover tuning Even if I click Move now nothing happens it also does not run daily. If I disable "disable mover running on a schedule" and click Move now it will run mover. So it appears the issue is with mover tuning. These are the default settings when you download mover tuning. I must not be understanding something in mover tuning. What am I missing?

motherboard and RAM replaced. Fingers crossed but so far no more crashing.

I added HD homerun to Plex. Wondering folks know where the recordings get saved to and if they can be moved?

I did not see a way to assign an unassigned drive to the syslog server. I did not try making it a cache drive. I will try that when I get my new MB and RAM. If I recall correctly I only saw assigned drives show up as options to be assigned to syslog server. The other thing that is kinda useful with writing it to the same drive as the OS is that is formatted in fat. So it can be removed and placed into a windows machine to read. I do not think that is possible with these other ways being discussed.

The mirror to USB drive is a little bit dangerous if you fill the drive. I have run into it corrupting the drive. What I have found effective is to use a second usb drive on the same machine and create a syslog server pointing back to itself and point to the second USB drive. Then I can set the log files to split on a specific size. This prevents the log file from growing to large to open. This has happened with me for random seg faults. The only issue I see with this plan is you have to add the drive to the array. Which then gets added to parity check. And then when you want to remove it you have to create a new setup 🙃 Might be a feature that might be useful in the future. Having a second USB drive that can be configured to only write syslog to would be beneficial in a lot of ways. Or is there another way to set the same thing up I am missing? If that were possible I'd probably just always leave the USB drive in to preserve syslog. Then something to delete old files or overwrite old files once the drive fills.

sent both the motherboard and the RAM back for replacements. Everything except these two items has been swapped. Dont know what else to try.

I dont think its a cache in any sense of the word. I think its probably the best term they could come up with to kind of describe what it is. Just makes it difficult for those that understand what a cache is to understand what this is 😄

I guess do not understand the purpose of your implemented "cache" drive then. Its a "cache" but not really, seems more a temporary storage. It will speed up data transfers (which seems to be the primary purpose) but also contribute to data loss since its unprotected data space. If you intend to run programs out of cache then you have to not run mover on that data period. I'm not even sure I understand the point at which you fill up your cache the data gets moved to the HDD but then nothing will move it back. So you will be using the spinning HDD and not cache if you ever fill it. Only new data will get stuck in "cache" so performance could degrade over time unless you catch that you had a fill event and then move it back manually. Seems wacky but I'm sure I am not understanding something. Do you folks have some additional tutorials or documentation explaining the details of this feature and how to use it to get the most out of it?

My cache drive was a 2TB NVME I can just use the NVME as disk1 of the array and run all the appdata and VM's out of the NVME. I do also have a 1TB SSD drive that I will repurpose as a cache drive to speed up network transfers. This assumes I am understanding things correctly.