blaine07

Is this container not kept updated with docker? I see this in logs; i have tried to run it but can't seem to figure out the proper way to handle this? Any help?

Sorry for the confusion; thank you! I apologize...

As above mentioned, seeing this in log too and not sure if I should attempt to manually do anything, or not?

Hey Sanjay, please skim the contents and the Original Post. I think you’ll have no problem locating the answer. 🙂 (No, it doesn’t survive Server Reboot)

Will it be updated with unraid or with AppStore plug-in thing in unraid?

Thanks for sharing!

Well, anyone have verdict on 25.0.3; is it safe to upgrade? Everything good?

I’ve been wanting to play with this. Maybe sometime this weekend or upcoming week I can find time to play with this! Thank you!

Random Q; with unraid has anyone figured out to prune/shrink DB size?

So it appears my huge backup and maybe all my issues were caused by recently famed Kasm(& I evidently installed around same time as I went v2 to V3) everyone has been talking about lately. Evidently it’s huge. Later today I’ll switch back to V3 and give this a go again. Finally got a clean backup on V2 though today. 🤞🏻

I did find two more logs that may help mate: Just ran across the logs in the file and thought maybe it would help. Also notice backup images are HUGE. Like 70gb compared to a normal ~15gb. (No disk isn’t out of space) Log 1 Log 2 Hopefully this is somehow helpful 🤞🏻

Cron jobs are irrelevant; they’ve never “crossed times” before now. This backup has always finished by 330-0400. I’m not sure what’s taking so much longer than normal either though 😞

So i kinda remembered why containers may be running already once I am cancelling backup and going it's going to start containers back up like before backup started. A long time ago I had issues with containers so I have a few cron restarting certain containers BUT I have always ran my backups at 135am and the cron have NEVER conflicted with Appdata being backed up until now, it's always completed backup before any cron jobs I had were set to run. Cron Jobs(Your getting a picture because I don't know how to show you any other way, sorry): Backup Logs: HERE If you need clarification; let me know.

Here is where I got with last nights backup:

I couldn't even tell you which ones weren't running prior to backup kicking off to be honest. No, I do NOT have docker auto update enabled though. I would say only 10-15 weren't running previous to it kicking off. Backup starts at like 230AM; its usually done when I get up around 4-5ish. Today at 530(hey I over slept don't judge me) I noticed nothing was running. I finally had to come to backup status tab and "STOP" it because it was still trying to do whatever. You should see me telling it to stop itself towards end of log.

Hopefully there is nothing user identifiable? Pastebin of LOGS

I disabled Verifying as mentioned above; then this time it ran backup didn't/couldn't finish at all and containers never restarted...ever. 😞

Today I got errors about my backup— pardon my idiocracy but where exactly do I need to check to see what went wrong? Never had backup issues before so this is a new game of hide and seek for me 😩

Can someone tell me what this is about? I don’t understand how I wouldn’t get more Password App updates; I am on NC 25.0.2, latest Unraid with PHP 8. What does this mean?

It probably won’t work saying that will it?

@mgutt I removed the post arguments as we discussed and it’s “back at it again”. Any last ditch efforts? It’s network related I just am unsure what else at this point to do?

Updated my Second instance of Nextcloud; same thing. Had to change "UKNOWN" owner to "nobody". Something isn't going right somewhere; just no idea if a Nextcloud thing or Unraid issue. 😞 EDIT: I just hope I am not ruining my life later by now changing the permissions to "nobody" despite that appears to be what they always have been/should be?

I had to change Owner of folder to "nobody" as well to get it to install. Issue now is the same-- Not sure what to do now... sigh: EDIT: anyways, I did have to change permissions on the nextcloud* appdata folder..and once I restarted container again it seems the cron thing sorted itself out..It's updating in similar time frames and other NC instance I have and not red anymore? Edit 2: more I think about it the more I think that folder shouldn’t be having ownership problems. Not sure at what point ownership should get changed to “nobody” but it appears that failing to happen, for whatever reason, was what the issue was. When at installation is it supposed to handle that itself? Change ownership of install folder. Is that a Nextcloud or Unraid issue?

@mgutt I haven’t had time to edit my Post Arguments yet but I just want to say thank you. Thank you for all the help you provide all of us in this thread. I can see it’s daunting. Good work mate; thank you!

I can’t confirm yet I’ve resolved my issue but it’s likely my own idiocracy. See my post above about post arguments.