hpaar

Hi, there is a new version. Thank you for your great work

I moved this to the new thread: Just a hint: I moved my appdata-directories (the ones who are using sqlite) to an external drive using the "Unassigned Devices"-plugin. Normally appdata is on /mnt/disk1/. Upgraded from 6.6.7 to 6.7.2 and have no database corruption since. I do not have a cache drive. I think the database corruption must be something to do with array-functionality. I will downgrade tonight and move the appadata-directories back to /mnt/disk1 and then upgrade to 6.7.3-rc2.

Just a hint: I moved my appdata-directories (the ones who are using sqlite) to an external drive using the "Unassigned Devices"-plugin. Normally appdata is on /mnt/disk1/. Upgraded from 6.6.7 to 6.7.2 and have no database corruption since. I do not have a cache drive. I think the database corruption must be something to do with array-functionality. I will downgrade tonight and move the appadata-directories back to /mnt/disk1 and then upgrade to 6.7.3-rc2. Update 2019-07-28 After one day I got a database corruption with 6.7.3-rc2 Let me know what I can provide to help the troubleshooting.

Hi, I have my system downgraded to 6.6.7 due to the ongoing database corruption issue in 6.7.x I rebuilded the database (6.6.7) in Plex from the scratch and appdata is on /mnt/diskN/appdata from the beginning. Direct I/O is set to off. I do not have a cache drive. Docker Image is on /mnt/diskN/appdata. As soon I upgrade to 6.7.x I get a database corruption. Is there anything else I can do? Besides waiting for a fix so that I can upgrade. Thank you.

Hi, I just installed dnscrypt-proxy on my unRAID machine. (v6.6.4). As you mentioned, if you don't have IPv6, you need to edit the toml-file. I used the template from community applications and I set a mapping for "/config". But there is no toml-file that I can edit. So my docker-app/-image always shutdowns immediatly. Any help is appreciated. Thank you.

Here is work-around from the official Seafile Forum. https://forum.seafile.com/t/docker-automatically-terminates-after-a-minute-within-the-container-opt-seafile-seafile-server-latest-seafile-sh-stop/6575/2 I hope this helps

Thank you for wffort and support.

Hi, Seafile has updated the official Seafile Docker Image on which cmer seafile docker image is based on. More info if you click on the link. It allows now to stop the service so that you can do garbage collection etc. It would be kind if cmer could update his image. Regards

Hi, see my last post:

Hi cmer, I wanted to point that the seafile-docker from haiwen, which I think is part of your docker image, has been updated. This new version let’s you use docker command directly to run, stop and upgrade Seafile server. In other words, it works more natively with docker technology. Here is more https://forum.seafile.com/t/new-seafile-docker-is-ready/5856 Could you update your docker image? Thank you.

Hi, I would not recommend a garbage collection at startup, as it takes quite a long time depending on the size of the library. A possibility to run the script manually or at a specific time would be great. My question would be how can I deactivate that the docker container stops after stopping the seafile-server service. Any help is appreciated.

Thank you. I did manage to upgrade the database. It is quite difficult to achieve it in the amount of time the docker app starts up. By entering in the docker-bash "/opt/haiwen/seafile-server-'version_number_as entered_in_version''/upgrade/upgrade_6.1_6.2.sh", I achieved it. In my case I also had manually to enter Version "6.2.3" and not "latest" to receive the latest version. As this procedure is clocked by the docker runtime, it would be great if the process of upgrading the database could be done during the "normal" upgrade process in the docker app. Thank you again for your help and the effort to setup Seafile in Docker on unRAID.

Hi, I have a Seafile 6.1.2 installation with some data. -------------- I tried to update to the newest version available by entering "latest" to the environment variable "Version". But the update didn't run through. Here is the log from the startup procedure: -------------- Generating download URL for:VERSION: latestARCHITECTURE: x86-64EDITION: CommunityInstalling Community Edition...Downloading & Extracting https://download.seadrive.org/seafile-server_6.2.2_x86-64.tar.gz...Done!Using Community Edition...Installation path: /opt/haiwen/seafile-server-6.2.2Seahub is not runningDone.seafile server not running yetDone.seafile server not running yetDone.failed to run "ccnet-server -t"[11/20/17 20:04:13] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf[11/20/17 20:04:13] ../common/ccnet-db.c(142): Error exec query CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id): sqlite3_exec failed: table EmailUser has no column named reference_id. -------------- It seems the upgrade of the database hasn't take place. The problem is that the Docker App stops immediately after that message. Is there a way to upgrade the database manually? Any help is appreciated. Thank you.

Hi, thank you for quick answer. I did some attempts. Installing a fresh installation of Seafile 6.2.3 was OK with the posted nginx configuration suddenly worked. I could down- and upload files. So the problem is solved. Thank you.

Hi, I am succesfully running Seafile 6.1.2 with a nginx configuration. When I wanted to try to setup as a test instance the new Seafile 6.2.3, I can not get the uploading and downloading running. I always get a "FILE NOT FOUND". I am using the same nginx configuration (only a different subdomain) as with Seafile 6.1.2. I setup the Service_URL and FILE_SERVER_ROOT via database. The FILE_SERVER_ROOT is "https://url/seafhttp" Here is my nginx configuration with Seafile 6.2.3: server { listen 80; server_name url; location / { proxy_pass http://internal-ip-address:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_buffering off; } location /seafhttp { rewrite ^/seafhttp(.*)$ $1 break; proxy_pass http://internal-ip-address:8082; client_max_body_size 0; proxy_connect_timeout 36000s; proxy_read_timeout 36000s; proxy_send_timeout 36000s; send_timeout 36000s; proxy_request_buffering off; } } server { listen 443 ssl; server_name url; .......SSL Configuration location / { proxy_pass http://internal-ip-address:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_buffering off; } location /seafhttp { rewrite ^/seafhttp(.*)$ $1 break; proxy_pass http://internal-ip-address:8082; client_max_body_size 0; proxy_connect_timeout 36000s; proxy_read_timeout 36000s; proxy_send_timeout 36000s; send_timeout 36000s; proxy_request_buffering off; } } Any help is appreciated. Thank you.