[How to set up unRAID notification using Gmail SMTP settings]

Worked Great. Thank you.

[[Support] Linuxserver.io - Nextcloud]

UNRAID VER. 6.8.3 NEXTCLOUD VER. 15.0.2 UPDATE ISSUE. (SELF INDUCED)

 

Mistake 1

I thought that when I updated the nextcloud docker I was updating the Nextcloud Application. I was wrong. I am way behind in the version of nextcloud that i'm using.
I found a manual update method on one of "linuxserver.io" guides by using the unraid terminal and entered “docker exec -it nextcloud updater.phar”
It seems to have run…

 

Quote

Current version is 15.0.2.

Update to Nextcloud 16.0.11 available. (channel: “stable”)
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-16.0.11.zip

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[] Check for expected files
[] Check for write permissions
[] Create backup
[] Downloading
[] Verify integrity
[] Extracting
[] Enable maintenance mode
[] Replace entry points
[] Delete old files
[] Move new files in place
[] Done

Update of code successful.

Should the “occ upgrade” command be executed? [Y/n] n
Please now execute “./occ upgrade” to finish the upgrade.
root@StorageBox:~#

 

Mistake 2

I didn’t answer Y to the question. “Should the “occ upgrade” command be executed? [Y/n]”

Now I can’t figure out how to get back to run this script.

Is all lost? Is there hope of recovery? Should I delete this docker and start over?

 

Any help would be appreciated.

Thank you.

Kopyguy

 

Also as a side question is the Maria Database falling behind too? I've only done the docker updates on it. 

[cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null]

Thank you will do.

[cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null]

Hello all i'm currently using Unraid 6.3.0 but had this happening on the previous version. I 've been getting an email with the subject "cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null" and in the body of the text is "error: Ignoring tor because of bad file mode - must be 0644 or 0444." It looks like a permission issue that is stopping a cron job from running??? I have included part of a log that I think is relevant. Is this fixable?

Sys_error.pdf

[Unraid temporary licence]

Good stuff. Can i assume the same treatment for my permanent key?

[Unraid temporary licence]

I would like to reinstall me unraid system on my current usb stick that has a temporary licence. If I do reinstall will I be able to use my current temporary licence with its remaining time or will this USB be blacklisted and force me to use a different key? Thank you in advance.