KluthR

The syslogs are inside the appdata and changes during backup. That will cause an error. Either exclude they or change its location.

I would say, Warning is ok. It warns you, that it might be an issue, that some XMLs are missing. But I agree with the "not wanted" entry, that could go into the Info section. Maybe switching to error level for notifications is better for your setup? EDIT: I believe I got you wrong. Your setting IS errors only, right? There is a bug, that also sends warnings out. I'll fix that. @Flemming It starts tar again in vberify mode and compares the source against its just made copy. Any differences would be cause an error It logs the error, but inside another category (Info instead of Error) and even continues the process as it were successful. I dont work with it, I just noted it there. There is also a link, ponting to tars manual page This version backups the XMLs from the .img mount, not the img itself anymore Guessed right @kjames2001 Thats weird, that this is working now for you. Maybe I make the change permanent (any update will reset the manual change)

Ahh, thanks. I stick to CMK then.

Hey, I set up two ZFS Pools in Unraid. of of them reported a warning about unrecoverable errors this night (via CheckMK). But Unraid itself did not sent me any messages. Is this normal behavior? If I open up the device status for that pool, Unraid shows the zfs status output and displays the same warning. I wouldnt have that noticed without CMK. nas-diagnostics-20230812-0945.zip

Feels wrong. could you open up the archive and see what root (with one layer deeper) are inside?

You sure? The note regarding USB backup tells me you are using one of the older plugins.

Not sure. The backup only picks up /mnt/user/appdata/plex which seems correct. And that folder ist 25GB compared to 50GB for the plex.tar.gz??

The old plugin relied on the extra update plugin (I forgot its name).

Yep, never noticed that. I correct that within a next update You are right. And thats how the update check works here. It checks the image for update. Not sure if I forgot something - because I make it the same way Unraid does. I have to check, if Unraid behaves the same way or if Unraid handles that case. I will adapt the plugin accordingly

Hi! Unraid 6.12.3. Observed a weird behavior of docker... I use the DockerClient class for starting and stopping containers for the appdata.backup. Now, after a few days with my new setup server, I noticed, that my guacd container stays off after backup. The log says, that it could not be stopped, because "Code: " (no further code). This is the result straight out of stopContainer function. So I made a test: DockerClient->stopContainer always fails to stop guacd and hits the timeout. If I use "docker stop guacd" in the console, its stopping as wanted. Did anyone noticed this as well? I dont know whats the difference, both commands should talk to docker via the socket, right? Wait.. Just while writing this... I forgot to specify the -t parameter for "docker stop guacd". As soon as I specify -t, it does the same. With this knowledge, I solved my own problem during writing this thread (I still leave it here). docker stop hits the default 10 second timeout and KILLS the container without changing the output (just displays the container name, as usual). Obviously its something within guacd which ignores the SIGTERM. But the DockerClient->stopContainer returns an error if the KILL happened. I know that this is coming straight out the docker API. So I have to catch that case with a test.

Well, the postbackup is set to trigger after the main backup method is finished. Depending on how you set it, the container stop all, backup all and then start all OR single stop, single backup, single start, next one. And after that mechanism, the postbackup is run one time. That results in being started after the containers are back up, yes. I could change that behavior, but when to run the script in case of single stop, backup, start mode?

Managing issues within the Plugin thread is a mess. Is there any plan/disussion allowing sub-bugtracker per plugin inside the Unraid forum, managed by the dev? My current alternative would be using the github issue tracker

Please share the _exact_ value of the setting You are the first for me Dont stop -> No: Stops it (default). Dont Stop -> Yes, leave them running. Maybe I adapt the wording in a future update. Never noticed it, I'll check this, thanks! Ah, okay - then it seems you need some exclusions. Please still share the settings. Please determine which volume mappings could be ignored during backup and set them as exclusion. General: Sorry for late response time, still busy with things outside Unraid. To top it all off, my productive Unraid server crashed and needed to make the overdue server replacement. I will look into all issues and features the next weeks. P.S.: Someone posted issues regading notifications sent when they should not. Could not reproduce that on my new system with my own plugin. P.P.S.: The next plan is to open up github issue page. I lost the overview of the issues here. I need a better way of organize issues. Its a mess to deal with issue tracking within one thread. Maybe Unraid opens up the bug tracker within the forum for plugins but until this, I would switch to Github Issues. I also plan to change the way debug logs get shared with me: The next version offers an one-click solution which uploads your config and debug log to me. You receive a unique ID for you to post which enables me to view your (maybe sensititive) log for debugging purpose.

Please try this: Open /usr/local/emhttp/plugins/appdata.backup/pages/content/settings.php. Scroll down to line 214, saying "<form id=abSettingsForm>". Just after that line, insert this: <input type="hidden" name="csrf_token" value="<?=_var($var,'csrf_token')?>"> Save it and reload the settings page and try to save. What is happening now?

Yes but manual configuration is not that easy. I got no feedback yet on the CSRF thing I asked internally. Did you tried another browser? Mobile phone? Anything in the system log in that case? The mechanism works the same, its just the order of execution that changes, so no difference here. I cant tell whats the issue here. File owner is root and I assume the rights are "rwxr-xr-x", so I add a permission fix in a later update.

Is there any comparison chart somewhere between Unraid parity and pure ZFS in CPU usage?

No it was not anyway. The new server is already here I had just no time to replace it. Now its time

My server just stopped working. It was still on, but no network comms, no HDMI display signal, no reaction to inserted keyboard, nothing. Only way for me was to force a reset - then it started working normally. Since the logs are not stored ynwhere, is there any file on the boot drive that holds some kind of data for me to check what was going on?

You have to select the parent folder that holds the ab_ folders.

@quiksilver2 and @jcofer555 Please share the debug log or the view for Internal volumes of the container sections. It feeld like all volume mappings are treated as external because incpmplete Appdata sources configuration. Note the help block for that field.

@PeteAskingCant tell. The compression is at default settings. Only the T setting is set to 0 to use all cores. Setting the compression level is something for the wishlist

Which old one? From squid or my fork of the previous appdata?

The stop mechanism is exactly the same for all options. Have to test this later then. Currently Iam not at home.

No. The attached log mentions errors coming out of docker daemon. One friend had similar issues and they were gone after switching fo ipvlan. No idea if that matters. If you setup your Unraid notification correctly, you should have received an email for every error line. This is already possible. See per container settings. Any reboot since then? Sure. This is related to the common Plex backup issue: Some files inside Library/ApplicationSupport could not be backed up. It seems we have to collect common excludes for plex related apps. Please try to exclude "Library/Application Support" - if that doesnt matter for disaster recovery. Interesting, since I got another user (or was it you?) with the same issue recently. CSRF Token are handled by Unraid as far as I know. I have to check this later.

How is the notification setting set? Please share the debug log. Same: How is the notification set? Could you set the settings back, backup and share a debug log? Currently yes. But I have plans to improve restore experience. Restoring XML is not the same as restoring docker containers. After restoring XML, they are available in the template dropdown. I have plans to add container creation to restore function. You excluded /mnt for Krusader resulting in failing verification. Please remove the exclusion or skip the whole container. tar: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Logs/: Cannot savedir: Input/output error; tar: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Plug-in Support/Data/com.plexapp.system/: Cannot savedir: Input/output error; tar: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Metadata/TV Shows/3/495d21813339e6542d1713ccc0ed51d7c636e14.bundle/Contents/_combined/seasons/3/episodes/: Cannot savedir: Input/output error; Cant tell. Maybe some exclusions for these folders may help. I never found out this special cases why tar wont work with plex internal folders. @spiderben25Please share a debug log. Any lines occuring in the system log while trying to save? You did not set the Allowed sources correctly. Instead of setting every single container appdata path, just type in /mnt/user and /mnt/cache. Your containers have /mnt/user share paths and get sanitized because the plugin treats them as external volume.