dollabillz
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dollabillz
-
-
Agreed, I update the docker image and it fails to update when it boots. That is the output and then it is stuck in maintenance mode. rolling back the image fails as well.
-
10 hours ago, Archonw said:
To get out of maintenance mode you can open a terminal and put this in:
docker exec -it nextcloud occ maintenance:mode --off
docker exec -it nextcloud occ maintenance:mode --off
wher "nextcloud" is the name of your nextcloud docker
thanks for the info I am now out of maintenance mode but the update still failed and the web interface says "Please use the command line updater because updating via browser is disabled in your config.php."
When I run "docker exec -it nextcloud occ upgrade" I get this error: Exception: Database error when running migration 28000Date20230906104802 for app core
Index name "rd_wopi_token_idx" for table "oc_richdocuments_wopi" collides with the constraint on table "oc_officeonline_wopi".
Update failed -
So an update failed, this is the output:
using keys found in /config/keys
Initializing nextcloud 28.0.0.11 (this can take a while) ...
Upgrading nextcloud from 27.1.4.1 ...
Setting permissions
Setting log level to debug
Updating database schema
Exception: Database error when running migration 28000Date20230906104802 for app core
Index name "rd_wopi_token_idx" for table "oc_richdocuments_wopi" collides with the constraint on table "oc_officeonline_wopi".
Update failed
Maintenance mode is kept active
Resetting log level
Initializing finished
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│ old date │ new date │ path │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2018-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf │
│ 2022-08-20 │ 2023-08-13 │ /config/nginx/ssl.conf │
│ │ 2023-06-23 │ /config/nginx/site-confs/default.conf │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.and now it stuck in maintenance mode
-
14 hours ago, iXNyNe said:
Also, I forgot to mention an important detail about the file integrity fix that has been released (entirely my bad!)
docker exec nextcloud touch /config/www/nextcloud/config/needs_migrationThen restart the container.
The reason is the fix is only meant to run when you upgrade from a previous version (which includes the migration process that moved nextcloud's files inside the container). This will make the container think it needs to perform an upgrade and cleanup the integrity check files, and nextcloud will recognize it's already up to date and carry on fine.
This worked for me. Thank you for the fix.
-
On 10/25/2022 at 4:14 PM, daveo132 said:
Hi all,
I'm having a horrid time trying to upgrade to 23.0.1
I keep on getting 504 Gateway errors when the update is trying to progress.
- Happens on Step 3 (creating the backup) but eventually will progress.
- Happens on Step 5 (Downloading) I had to download the zip and place in the updater folder to work around this.
Downloading
Parsing response failed.
Show detailed response<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.20.2</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
However, if I F5 the page, it then carries on like all was ok.
- Happens on Step 7 (Extracting) and that causes it all to fail and resets the update back to the start.
I've seen some stuff about trying to make sure the write permissions are correct by runningsudo chown -R www-data:www-data /mnt/nextcloudbut this just gives me an error of "invalid user www-data" which I understand should not be the case?I'm at a bit of a loss and reached the limit of my knowledge here with linux / unraid etc.
Looking into things, I think it might be working but the connection is being timed out.
It just failed again on extracting but refreshing the page gave me
"Step 6 is currently in process. Please reload this page later."
I've read somewhere that you can increase the default timeouts for this. But I don't know where or how.
EDIT:
Ok, I can confirm that my update does work but all the issues are being caused by 504 timeouts.
I am having the same problem as this but I am using NC 25.05. I get an error code in the update.log that reads "cant handle ZIP file. Error code is: 28. I looked at where the new update was downloaded and I see that it was unzipped.
Edit: ran the updater.php in the CLI and it seemed to go okay.
sudo -u abc php /config/www/nextcloud/updater/updater.phar
for me the user was abc but yours may be different.
-
Did a fresh install jellyfin and there is no place for me to enter in the GPU UUID. Did it get removed for some reason?
-
okay i got it up and runing but now i have new containers being made that say they are protonmail bridge. the newest is called "quirky_perlman" with an id of 3d528365e607. has any one seen this before?
-
On 5/21/2021 at 11:00 PM, ich777 said:
It looks like that the container is fully started and waiting for connections, how did you try to connect (IP - internal or external) and with which port?
Tried direct connection through launcher both IP and server name. Fixed it by doing a fresh install. new problem was BattleEye would not start. solved that by disabling it in server.cfg file.
-
1
-
-
On 5/10/2021 at 10:19 PM, ich777 said:
Can you please post some logs if the container is even fully started and waiting for connections?
How did you try to connect?
Here is the logs from the server. It looks like it is fully up and connected. Tried direct connection and search from in game as well as in launch menu.
-
Here is the logs from the server. It looks like it is fully up and connected. Tried direct connection and search from in game as well as in launch menu.
-
trying to get Arma3 server up, i left the template config stock w/ the exception of steam login and password. i change the server name in the server.cfg file but i still cant connect to it even if i do a direct connection. all i get is a ARMA3 splash screen. Has any one else had this problem and figured it out?
-
15 hours ago, tvd1 said:
Hey guys - Sort of a newbie here, but I have a question about my swag setup. I followed a great guide on how to get Emby and Swag to work on my Unraid server.. All is well with that and im happy.
However, I have another (physical) synology server that has services on the same domain. Those no longer work. Is there any guides or information about how I'd get "emby.mydomain.com" to resolve to my unraid swag setup, and "synology.mydomain.com:5000" to work on my synology box?
cant you just install Swag on both servers and port 5000 to your synology server?
-
So I set up the server to use a max amount of 20480M, at start its says it uses ~7GiB but when one person joins it shots up to ~20GiB. When more people join they quickly get a server time out screen on there end. Request help troubleshoot problem and hopefully steps to fix error.
-
I was wondering if some one could help me figure out where i had screwed up. I set up swag and nextcloud on the same custom network and port forward is working but when i go to mydomain.me I get "The page isn’t redirecting properly". This all started when i got a new domain, on my old domain it worked just fine. can anyone point me in the right direction?
after poking it the settings some more, i think it may be in the NGINX program because when i changed it from DNS/wildcard to http and only used one subdomain it worked. but when i put in the rest of the subdomains it stopped working again.
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
fixed the issue by moving the "oc_richdocuments_wop" to a back up folder. the data table was a old one from an uninstalled app. the data file can be found in the appdata file of your database app for me its mariadb.