Closed aronovgj closed 8 years ago
The oc_trusted_servers
was introduced with ownCloud/Nextcloud 9. So it can't already exists before you started the migration. This also explains while the same error happens on the next table if you drop oc_trusted_servers
. It sounds like for some reasons the migration script tries to create the new tables multiple times... Never saw this before.
It may be that I forgot to restore the db after the upgrade failed the first time, when OC9 was just released. That was quite a long time ago, so I don't remember. If we can just ignore the exceptions (as said in the oc issue that I linked), then so be it. There is this calendar and contacts problem though that really prevents me from upgrading. If you need more info, please tell me.
The problems with upstream sent invalid status
is likely caused by your NGINX config, please update it to match the required one for Nextcloud / ownCloud 9. That should solve your issue.
Please use https://help.nextcloud.com if you require more help on that.
Thats my config now: the error in the log is still the same and I still can not access calendar or contacts.
upstream php-handler {
# server 127.0.0.1:9000;
server unix:/var/run/php5-fpm.sock;
}
server {
listen 80;
server_name localhost;
# enforce https
return 301 https://$server_name$request_uri;
}
server {
listen 443 ssl;
server_name localhost;
ssl_certificate /etc/apache2/ssl/apache.crt;
ssl_certificate_key /etc/apache2/ssl/apache.key;
# Add headers to serve security related headers
# Before enabling Strict-Transport-Security headers please read into this
# topic first.
# add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Path to the root of your installation
root /var/www/nextcloud/;
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
# The following 2 rules are only needed for the user_webfinger app.
# Uncomment it if you're planning to use this app.
#rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
#rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json
# last;
location = /.well-known/carddav { return 301
$scheme://$host/remote.php/dav; }
location = /.well-known/caldav { return 301
$scheme://$host/remote.php/dav; }
location /.well-known/acme-challenge { }
# set max upload size
client_max_body_size 512M;
fastcgi_buffers 64 4K;
# Disable gzip to avoid the removal of the ETag header
gzip off;
# Uncomment if your server is build with the ngx_pagespeed module
# This module is currently not supported.
#pagespeed off;
error_page 403 /core/templates/403.php;
error_page 404 /core/templates/404.php;
location / {
rewrite ^ /index.php$uri;
}
location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) {
deny all;
}
location ~
^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|ocs-provider/.+|core/templates/40[34])\.php(?:$|/) {
include fastcgi_params;
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param HTTPS on;
#Avoid sending the security headers twice
fastcgi_param modHeadersAvailable true;
fastcgi_param front_controller_active true;
fastcgi_pass php-handler;
fastcgi_intercept_errors on;
#fastcgi_request_buffering off;
}
location ~ ^/(?:updater|ocs-provider)(?:$|/) {
try_files $uri/ =404;
index index.php;
}
# Adding the cache control header for js and css files
# Make sure it is BELOW the PHP block
location ~* \.(?:css|js)$ {
try_files $uri /index.php$uri$is_args$args;
add_header Cache-Control "public, max-age=7200";
# Add headers to serve security related headers (It is intended to
# have those duplicated to the ones above)
# Before enabling Strict-Transport-Security headers please read into
# this topic first.
# add_header Strict-Transport-Security "max-age=15768000;
# includeSubDomains; preload;";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
# Optional: Don't log access to assets
access_log off;
}
location ~* \.(?:svg|gif|png|html|ttf|woff|ico|jpg|jpeg)$ {
try_files $uri /index.php$uri$is_args$args;
# Optional: Don't log access to other assets
access_log off;
}
}
Nginx told me however that it does not know the directive fastcgi_request_buffering
. I had to disable it.
unknown directive "fastcgi_request_buffering" in /etc/nginx/conf.d/default.conf:93
To me it seems like a Mysql issue.
Also I don't feel like the forum is very helpful: https://help.nextcloud.com/t/several-issues-known-from-oc/565
I'm also having this issue, I'm really confused by it.
I upgraded successfully from OC 8.2.5 to NC 9.0, and as part of that the Calendar and Tasks apps got upgraded. I had this working perfectly right after the upgrade last night, but now I'm unable to access any of my calendar/tasks data through the web app this morning. For some reason I can still access it all normally through my DAV clients.
Would this have anything to do with these apps being merged into the core? I'm just really confused why it was working for me and then stopped. I was thinking this was a part of those apps themselves getting upgrades, before remembering that they were working OK after they were upgraded.
Luckily I still have my OC instance and don't have much new data in NC, so I'll try to run the upgrade again and try to figure out what causes it to stop working.
Is there a proper way to migrate those two apps over? I was reading about the occ
commands for dav:migrate-calendars
and wasn't sure if that might have been something that I need to do. I ran that and it didn't seem to have any effect.
I upgraded successfully from OC 8.2.5 to NC 9.0, and as part of that the Calendar and Tasks apps got upgraded. I had this working perfectly right after the upgrade last night, but now I'm unable to access any of my calendar/tasks data through the web app this morning. For some reason I can still access it all normally through my DAV clients.
In case of calendar: Have you marked the calendar as active on the left by clicking on it?
Do you mean activating the app in the Admin Apps panel? I did re-enable all my apps after the upgrade. Unless you're referring to clicking to show the calendars within the app? I can't see my calendars to do that, all I get is the loading icon.
migrate-calendars
did not help me, already tried it.
Any news on this topic? I've been wanting to upgrade to a newer version as well, but I have been reading up on this topic and the contacts/calendar apps are just not working after upgrading 8.2.x to a newer oc or nc (thus I'm still on oc 8.2.7).
Also the newer contacts/calendar apps lack basic functionality and are pretty much unusable. I did a writeup and gave ample feedback here https://github.com/owncloud/contacts/issues/435, but have been ignored and shot down by the oc devs.
@tessus The non-solution was to export contacts and calendar, delete the whole database, setup a fresh nextcloud, recreate the database by syncing everything to the server and import calendar and contacts. That was possible because only 3 users are using it.
@aronovgj Unfortunately I don't have that option. I have to many users.
I also tried (for testing purposes) to export from oc 8.2.7 into a vcf file and import it on nextloud 10.0.1. The result was a mess. The names are mostly correct, but the addresses are screwed up, so this wouldn't even be a solution, if I had only one user.
Steps to reproduce
Expected behaviour
Everything should work properly, especially files, calendar and contacts
Actual behaviour
I'm running into several issues that I already had upgrading to owncloud 9. The whole story chronologically further below.
Server configuration
Operating system: Mint 17.3
Web server: nginx 1.4.6 (in test environment but 1.11.1 in productive environment. No difference)
Database: MySQL 5.5.49
PHP version: PHP 5.5.9
Nextcloud version: (see Nextcloud admin page) 9
Updated from an older Nextcloud/ownCloud or fresh install: Owncloud 8.2.5
Where did you install Nextcloud from: https://download.nextcloud.com/server/releases/nextcloud-9.0.50.zip
Signing status (Nextcloud 9.0 and above):
List of activated apps:
The content of config/config.php:
/etc/nginx/conf.d/default.conf
Are you using external storage, if yes which one: local/smb/sftp/... no
Are you using encryption: yes/no no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/... no
The story
After doing all the "steps to reproduce" stuff I do this:
sudo -u www-data php /var/www/nextcloud/occ upgrade
I get errors looking much like here: http://github.com/owncloud/core/issues/23867I tried to drop the tables that are mentioned in the exception but then it just throws the same exceptions on other tables. I just ignore it as suggested on github.
Next thing is this: http://github.com/owncloud/core/issues/23610
After doing this I can access my files:
MySQL looks like this afterwards:
select * from oc_appconfig where configvalue like '%appinfo%';
After activating calendar app I get this when i try to access it:
Thats how it looks like: http://www.pic-upload.de/view-30937703/2.png.html the circle won't stop spinning.
After activating contacts I get this when I try to access it:
Thats how it looks like: http://www.pic-upload.de/view-30937702/1.png.html
The calendar/contacts issue looks similar to other issues but not quite the same. For example some can not see only one calendar. I can't see any calendars at all.