I did that through ssh. I stopped it through ssh last night as that's the only way I know how to stop it and stopping the webserver is one of the first things that the guide says to do.
Install Wordpress using nginx - turned to Nextcloud install
-
- OMV 5.x
- gelöst
- Nick0
-
-
Ah, I thought you were trying to update from within the GUI of nextcloud first as you now have a clean, new container running.
-
I think I've broken it so I am going to try my backup disk.
So, am I right that in order to do this, I just change the uuid in the docker-compose.yml file on the backup disk and then disconnect the disk that's problematic? Then I suppose I just format the problematic disk and set an rsync job up on the new disk to back that up.
-
Wait a second.
After you redeployed the nextcloud container, were you able to login to nextcloud?
-
No, I'm getting the 502 error.
-
What is log of the nextcloud container saying?
-
Then I rolled back what I did last night by renaming the new nextcloud directory to nextcloud-new, renamed the old nextloud directory from nextcloud-old to nextcloud
When you copied the folder, did you make sure the permissions are preserved?
-
What is log of the nextcloud container saying?
Here you go and thanks:
Code
Alles anzeigen[cont-init.d] 99-custom-scripts: exited 0., [cont-init.d] done., [services.d] starting services, [services.d] done., 210204 09:44:38 mysqld_safe Logging to syslog., 210204 09:44:38 mysqld_safe Starting mysqld daemon with databases from /config/databases, [s6-init] making user provided files available at /var/run/s6/etc...exited 0., [s6-init] ensuring user provided files have correct perms...exited 0., [fix-attrs.d] applying ownership & permissions fixes..., [fix-attrs.d] done., [cont-init.d] executing container initialization scripts..., [cont-init.d] 01-envfile: executing... , [cont-init.d] 01-envfile: exited 0., [cont-init.d] 10-adduser: executing... , usermod: no changes, , -------------------------------------, _ (), | | ___ _ __, | | / __| | | / \ , | | \__ \ | | | () |, |_| |___/ |_| \__/, , , Brought to you by linuxserver.io, -------------------------------------, , To support LSIO projects visit:, https://www.linuxserver.io/donate/, -------------------------------------, GID/UID, -------------------------------------, , User uid: 1000, User gid: 100, -------------------------------------, , [cont-init.d] 10-adduser: exited 0., [cont-init.d] 30-config: executing... , [cont-init.d] 30-config: exited 0., [cont-init.d] 40-initialise-db: executing... , [cont-init.d] 40-initialise-db: exited 0., [cont-init.d] 99-custom-scripts: executing... , [custom-init] no custom files found exiting..., [cont-init.d] 99-custom-scripts: exited 0., [cont-init.d] done., [services.d] starting services, [services.d] done., 210204 13:19:09 mysqld_safe Logging to syslog., 210204 13:19:09 mysqld_safe Starting mysqld daemon with databases from /config/databases, Caught SIGTERM signal!, [cont-finish.d] executing container finish scripts..., [cont-finish.d] done., [s6-finish] waiting for services., [s6-finish] sending all processes the TERM signal., [s6-finish] sending all processes the KILL signal and exiting., [s6-init] making user provided files available at /var/run/s6/etc...exited 0., [s6-init] ensuring user provided files have correct perms...exited 0., [fix-attrs.d] applying ownership & permissions fixes..., [fix-attrs.d] done., [cont-init.d] executing container initialization scripts..., [cont-init.d] 01-envfile: executing... , [cont-init.d] 01-envfile: exited 0., [cont-init.d] 10-adduser: executing... , usermod: no changes, , -------------------------------------, _ (), | | ___ _ __, | | / __| | | / \ , | | \__ \ | | | () |, |_| |___/ |_| \__/, , , Brought to you by linuxserver.io, -------------------------------------, , To support LSIO projects visit:, https://www.linuxserver.io/donate/, -------------------------------------, GID/UID, -------------------------------------, , User uid: 1000, User gid: 100, -------------------------------------, , [cont-init.d] 10-adduser: exited 0., [cont-init.d] 30-config: executing... , [cont-init.d] 30-config: exited 0., [cont-init.d] 40-initialise-db: executing... , [cont-init.d] 40-initialise-db: exited 0., [cont-init.d] 99-custom-scripts: executing... , [custom-init] no custom files found exiting..., [cont-init.d] 99-custom-scripts: exited 0., [cont-init.d] done., [services.d] starting services, [services.d] done., 210206 16:47:35 mysqld_safe Logging to syslog., 210206 16:47:35 mysqld_safe Starting mysqld daemon with databases from /config/databases,
-
When you copied the folder, did you make sure the permissions are preserved?
The guide says that you should rename the current nextcloud directory to something like nextcloud-old (which I did) and then upload the new nextcloud directory that you download from them.
I just scp'd it there from my desktop with scp -r /Users/nick/Desktop/NCupdate/nextcloud root@192.168.1.37:/srv/dev-disk-by-uuid-234ddefe-df8d-4d5e-91f9-8b0375a0d13f/appdata/nextcloud/config/www/ The guide didn't mention permissions.
Thanks,
Nick.
-
The log looks ok to me.
Can you go to the stack and stop it. Then restart the stack and check the logs of each container if there is an error.
Then check if you can access nextcloud.
-
The guide says that you should rename the current nextcloud to something like nextcloud-old (which I did) directory and then upload the new nextcloud directory that you download from them.
Ok, here seems to be a major misunderstanding.
The guide is not for docker. It is for installations of nextcloud on the OS without docker.
The nextcloud directory they are talking about is the directory where nextcloud is installed. That is something different.
-
/srv/dev-disk-by-uuid-234ddefe-df8d-4d5e-91f9-8b0375a0d13f/appdata/nextcloud/config/www/
Stop the stack, then you need to restore this directory.
All files should be owned by the user from your docker-compose file (UID: 1000) and by group users
Then start the stack again
-
The log looks ok to me.
Can you go to the stack and stop it. Then restart the stack and check the logs of each container if there is an error.
Then check if you can access nextcloud.
Thanks for looking at it for me. I can't seem to stop the stack as the checkbox to select it is greyed out. It says: "This stack was created outside of Portainer. Control over this stack is limited", when I hover over "Control/limited" for an explanation.
Ok, here seems to be a major misunderstanding.
The guide is not for docker. It is for installations of nextcloud on the OS without docker.
The nextcloud directory they are talking about is the directory where nextcloud is installed. That is something different.
Oh yes - well this would be typical me, wouldn't it. I had no idea that there would be different methods to update it.
-
Stop the stack, then you need to restore this directory.
All files should be owned by the user from your docker-compose file (UID: 1000) and by group users
Then start the stack again
That directory (/srv/dev-disk-by-uuid-234ddefe-df8d-4d5e-91f9-8b0375a0d13f/appdata/nextcloud/config/www/) is still there, it hasn't been removed. All I did was rename directories, i haven'te actually removed anything. We are talking still about fixing the broken version, not using the backup disk?
-
Did you change some of the settings of the container individually in portainer?
-
We are talking still about fixing the broken version, not using the backup disk?
Yes. Actually I do not understand what you mentioned in you post relating the backup
-
So, am I right that in order to do this, I just change the uuid in the docker-compose.yml file on the backup disk and then disconnect the disk that's problematic? Then I suppose I just format the problematic disk and set an rsync job up on the new disk to back that up.
Ah ok, you don't want to restore the complete disk, but swap them.
Why not just copying over the appdata folder of nextcloud? When doing this you have to make sure that you preserver permissions.
e.g using rsync with -a
-
Did you change some of the settings of the container individually in portainer?
No, I don't touch anything that i don't fully understand and docker, containers and stacks are still mostly an unknown territory for me.
-
Ah ok, you don't want to restore the complete disk, but swap them.
Why not just copying over the appdata folder of nextcloud? When doing this you have to make sure that you preserver permissions.
e.g using rsync with -a
OK, do you think that appdata is the only directory affected? The wierd thing is that I haven't actually deleted or overwritten anything. All I've done is rename one directory (nextcloud) and upload a new one and stop and start the server.
-
Worth a try. Rename it back. How do you rename?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!