This package still includes the update routines from 5.0.6 or below but also from the last package so you can update from any 5.x.x version to this one directly.
I have included a .htaccess file in the data folder because of BFGs post. It works fine for me.
Dropbox folder is up to date, repo will be as well.
Have fun with it, Eric.
Script:
#!/bin/sh
#--------ownCloud installer script
#--------package maintained at eg-blog.de
WEB=/var/services/web
preinst ()
{
exit 0
}
postinst ()
{
echo "$(date +%d.%m.%y_%H:%M:%S): ----installation started----" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
#migrate from old owncloud to new owncloud-eg package
if [ -d /var/packages/owncloud ]; then
#backup data folder
if [ -d $WEB/owncloud/data ]; then
mkdir ${SYNOPKG_PKGDEST}/../owncloud_data_migration
mv $WEB/owncloud/data ${SYNOPKG_PKGDEST}/../owncloud_data_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied old data folder into backup folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
#backup config folder
if [ -d $WEB/owncloud/config ]; then
mkdir ${SYNOPKG_PKGDEST}/../owncloud_config_migration
mv $WEB/owncloud/config ${SYNOPKG_PKGDEST}/../owncloud_config_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied old config folder into backup folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
# delete old owncloud installation
if [ -d $WEB/owncloud ]; then
rm -r $WEB/owncloud
echo "$(date +%d.%m.%y_%H:%M:%S): deleted old owncloud web folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
fi
# enter link and display types to the application.cfg DSM linkl file
if [ ! -z ${https} ]; then
echo "$(date +%d.%m.%y_%H:%M:%S): https link selected" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "protocol = https" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
echo "port = 443" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
else
echo "$(date +%d.%m.%y_%H:%M:%S): http link selected" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "protocol = http" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
echo "port = 80" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
fi
if [ ! -z ${external} ]; then
echo "$(date +%d.%m.%y_%H:%M:%S): External link selected" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "type = popup" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
else
echo "$(date +%d.%m.%y_%H:%M:%S): Embedded link selected" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "type = embedded" >> ${SYNOPKG_PKGDEST}/oc_dsmlink/application.cfg
fi
###install new owncloud version###
mv ${SYNOPKG_PKGDEST}/owncloud $WEB/
echo "$(date +%d.%m.%y_%H:%M:%S): moved owncloud files to web folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
if [ -d /var/packages/owncloud ]; then
#restore data folder
if [ -d ${SYNOPKG_PKGDEST}/../owncloud_data_migration/data ]; then
mv ${SYNOPKG_PKGDEST}/../owncloud_data_migration/data $WEB/owncloud
rmdir ${SYNOPKG_PKGDEST}/../owncloud_data_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied data folder back into owncloud folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
chmod -R 754 $WEB/owncloud/data
fi
#restore config folder
if [ -d ${SYNOPKG_PKGDEST}/../owncloud_config_migration/config ]; then
rm -r $WEB/owncloud/config
mv ${SYNOPKG_PKGDEST}/../owncloud_config_migration/config $WEB/owncloud
rmdir ${SYNOPKG_PKGDEST}/../owncloud_config_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied config folder back into owncloud folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
echo "$(date +%d.%m.%y_%H:%M:%S): delete old owncloud package files" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
rm -r /var/packages/owncloud
if [ -d ${SYNOPKG_PKGDEST}/../owncloud ]; then
rm -r ${SYNOPKG_PKGDEST}/../owncloud
echo "$(date +%d.%m.%y_%H:%M:%S): delete old owncloud files" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
fi
#create DSM link
if [ -L /usr/syno/synoman/webman/3rdparty/oc_dsmlink ]; then
rm /usr/syno/synoman/webman/3rdparty/oc_dsmlink
echo "$(date +%d.%m.%y_%H:%M:%S): delete old DSM link" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
ln -s ${SYNOPKG_PKGDEST}/oc_dsmlink /usr/syno/synoman/webman/3rdparty/
echo "$(date +%d.%m.%y_%H:%M:%S): created DSM link" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
#set folder permissions
mkdir $WEB/owncloud/data
chmod 770 -R $WEB/owncloud/data
chmod 777 -R $WEB/owncloud/config
chown -R nobody:nobody $WEB/owncloud/
echo "$(date +%d.%m.%y_%H:%M:%S): folder permissions set" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "$(date +%d.%m.%y_%H:%M:%S): ----installation finished----" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
exit 0
}
preuninst ()
{
exit 0
}
postuninst ()
{
#delete Web folder and DSM link
rm -r $WEB/owncloud
rm -r /usr/syno/synoman/webman/3rdparty/oc_dsmlink
exit 0
}
preupgrade ()
{
echo "$(date +%d.%m.%y_%H:%M:%S): ----update started----" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
if [ ! -d /var/packages/owncloud ]; then
if [ -d $WEB/owncloud/data ]; then
mkdir ${SYNOPKG_PKGDEST}/../owncloud_data_migration
mv $WEB/owncloud/data ${SYNOPKG_PKGDEST}/../owncloud_data_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied data folder into backup folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
if [ -d $WEB/owncloud/config ]; then
mkdir ${SYNOPKG_PKGDEST}/../owncloud_config_migration
mv $WEB/owncloud/config ${SYNOPKG_PKGDEST}/../owncloud_config_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied config folder into backup folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
fi
exit 0
}
postupgrade ()
{
#restore data folder
if [ -d ${SYNOPKG_PKGDEST}/../owncloud_data_migration/data ]; then
mv ${SYNOPKG_PKGDEST}/../owncloud_data_migration/data $WEB/owncloud
rmdir ${SYNOPKG_PKGDEST}/../owncloud_data_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied data folder back into owncloud folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
#restore config folder
if [ -d ${SYNOPKG_PKGDEST}/../owncloud_config_migration/config ]; then
rm -r $WEB/owncloud/config
mv ${SYNOPKG_PKGDEST}/../owncloud_config_migration/config $WEB/owncloud
rmdir ${SYNOPKG_PKGDEST}/../owncloud_config_migration
echo "$(date +%d.%m.%y_%H:%M:%S): copied config folder back into owncloud folder" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
fi
chmod -R 770 $WEB/owncloud/data
chmod -R 777 $WEB/owncloud/config
chown -R nobody:nobody $WEB/owncloud/
echo "$(date +%d.%m.%y_%H:%M:%S): folder permissions set" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "$(date +%d.%m.%y_%H:%M:%S): updated to version ${SYNOPKG_PKGVER}" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
echo "$(date +%d.%m.%y_%H:%M:%S): ----update finished----" >> ${SYNOPKG_PKGDEST}/owncloud_package.log
exit 0
}
Hi,
I had installed version 5.0.9 as described by you today. When I installed 5.0.10 via the Package Manager Update button, I was not able to access the Website anymore. All my files and the owncloud.db are gone. I had to restore a backup. Only thing I could find out was this line in the owncloud.log file everytime I tried to open the Website:
{„app“:“PHP“,“message“:“SQLSTATE[HY000]: General error: 1 no such table: oc_appconfig at \/var\/www\/cloud\/lib\/db.php#382″,“level“:4,“time“:1363353882}
Similar to this users experience:
http://www.synology-forum.de/showthread.html?43763-Achtung!-Owncloud-Update-5.0.9-2-%28SynoCommuntity%29-Update-l%F6scht-alle-Daten!&p=355279&viewfull=1#post355279
OK,
the „no such table: oc_appconfig“ was caused by the missing owncloud.db file in the data folder. I used the updated 5.0.10 directories and copied just the data files and owncloud.db file from the old 5.0.9 installation. After that I was able to open the Website, which showed the installation and DB upgrade progress.
May it helps someone else.
The same happenend to me. After updating from 5.07.x the owncloud web interface was not reachable. I restored (by rsync) the data folder from a previous backup. After this I could reach the owncloud web interface again. It showed the same message about updating was mentioned by Dominik.
Thank you Dominik for the post. It surely helped me to save a lot of time searching for a solution.
Hi,
I’m experiencing severe problems, which just started after yesterdays update of DSM (4.2->4.3). Before that I had Owncloud 5.0.10 installed and working. This morning, I noticed, that my Owncloud cannot be reached, just a blank page appears. After reinstalling the package, I get a message that the permissions are wrong. After I changed the ownership of the folders, once again only a white page appeared as before. In the owncloud.log file, I found this error:
{„app“:“PHP“,“message“:“Du besitzt keine Leseberechtigung f\u00fcr dieses Adressbuch. at \/volume1\/web\/owncloud\/apps\/contacts\/lib\/addressbook.php#159″,“level“:4,“time“:“2013-08-28T11:29:20+00:00″}
Did the apache-user change with DSM 4.3? Is it a problem with UTF-8 (locale on DS-Shell shows en_US.UTF-8).
Am I the only one, experiencing that problem? And most important, how can I get my Owncloud back up and running (without losing data – backup existing)? Any help is much appreciated!
Hi,
I have a similar problem as Jan:
After problems with the updating process, I decided to reinstall the whole package from the „eg-blog“-source.
I created an admin-account an am able to log-in to the newly created owncloud instance.
Everytime I try to import my (exported) user-instance-.zip from the former owncloud-install it gives me a not very descriptive error „Error migration Invalid import file“.
WTF? When I look into the export-.zip created by owncloud there is a huge .xml-file (dbexport.xml) with all the data in it as well as a „export_info.json“.
Can I do anything to get my calendar- and contact data back out of the .xml and my owncloud back running?
There is a strange overwrite flag in the data-.xml set to „false“, should I set this to true (see below)?
/volume1/web/owncloud/data/owncloud.db
true
false
Thanks in advance for all infos or help!
the code-sample should look like:
„database“
„name“ /volume1/web/owncloud/data/owncloud.db „/name“
„create“ true „/create“
„overwrite“ false „/overwrite“
where all “ are either
ah, damn: the “ should be replaced by xml-element-brackets: arrow-left/arrow-right
Hi, I got the same error (unreachable Owncloud Link) after the DSM Update to 4.3. Is there a workaround for repairing that current install and hopefully keep the data?
I was able to solve my problem by deinstalling and reinstalling the package, restoring the /data folder from my backup and modifying the config.php to use the php-database.
Probably there was no problem with OC/DSM but rather with browser data. I ran into a blank page again yesterday and found out, that it only happened with Firefox on my desktop pc. So it is probably a good start to check OC with another browser, before working on your OC installation.
For German speakers, there’s a thread on the issue in the Synology-Forum:
http://www.synology-forum.de/showthread.html?44253-Hilfe-owncloud-%F6ffnet-sich-nicht-mehr.&highlight=owncloud
Perfect!
Update to 5.0.10 cleared all my data, owncloud.db has got 0 (zero) bytes and the daily backup already overwrote all previous backups. Hence no valid backup now -> all data lost :-((
Michael
no problems, when updating from 5.0.6. to 5.0.10 (manual installation with dropbox package)
(DSM4.2)
NB: Any change to get rid of this message
„setting locale to en_US.UTF-8\/en_US.UTF8 failed. Support is probably not installed on your system“
did someone sucessfully update to DSM 4.3 without reinstalling Owncloud?
just updated to DSM 4.3, and so far no problems when going to the http://myserver/owncloud webpage and accesing contacts and calendar. I guess that was sth, which was already not working for Björn etc…
BTW: The error „setting locale to en_US.UTF-8\/en_US.UTF8“ is also gone! gr8 – cheers Alex
Hi all, my feeling is that there should be a warning in this blog with respect to the update to 5.0.10. As mentioned by Dominik, several people have lost their data already. This should be mentioned…
Just a short message to confirm I aso had the bad surprise toloose all my date when upgrading from 5.0.9 to 5.0.10. I had a not too old backup of the 5.0.9, I’ll try to put it again, export a backup and try to import into a clean/blank installation of 5.0.10.
It would be nice to advice users of this problem. Maybe even to suspend the automatic upgrade through synology package manager to avoid other people to face the same situation.
Anyway, it is the first time I face such problem, so a big thanks for making this package available for our synology NAS. It is really agreat service you provide us.
The blog contains a BIG warning if you upgrade from an old version by using the DSM update feature, due to some naming problems with a other owncloud distribution.
My update from 5.0.6 to 5.0.10 worked without any problems! Beside: Never update without backup!
@Alex: the issue some have been talking about is the upgrade from 5.0.9 to 5.0.10. There is *no* warning that this can fail. The surprising element is that it comes once you think you have navigated around all the mess with the 2 different packages successfully. And then it hits you 🙂 Of cause your remark regarding upgrade is pertinent… 😉
This helped for me – so far:
Open up the shell and go to directory of the owncloud installation „/volumeX/web/…./“
Copy all data from backup to data folder: cp -r /volumeX/backup/owncloud/data/* ./data/
Adapt owner: chown -R nobody: ./data/*
Thanks to Joesix. Hope this is all to do ….
After updating oc from 5.0.9 to 5.0.10 I LOST all my DATA with no available backup. BUT today I found all of my lost oc data stored in a migration folder in /volume1/@appstore/owncloud_data_migration/data/. I copied all files back to the oc folder and everything went well.
Now OC 5.0.10 and all my recovered data works fine 🙂
Hallo,
ich möchte von der 5.0.7. auf die 5.0.10 aktualisieren , bekomme jedoch stehts die Meldung „Paketmanagement nicht verfügbar“. Kann es sein dass es daran liegt, dass der Paketname der 5.0.7 „owncloud“ ist, während der Paketname der 5.0.10 „owncloud-eg“ ist ? Was muß ich tun, um auf die 5.0.10 aktualisieren zu können?
Gruß und Danke, E.Arens
Hello at all!
Sorry my english is not so good! I installed a new ds112j a few minutes ago. update the DSM to 4.3 3776, activate mysql and webstation, install phpmyadmin and as the last Programm owncloud (from file after downloading from here: http://www.cphub.net/index.php?id=37).
Now i click on the owncloud Icon and a blank tab in my browser opens… that was it. I read her copy this to there … but what should i do if i have nothing to copy? Any Ideas??
no koment
Hi,
I have tried to install owncloud 5.0.10.-27 several times on my synology DS211 (DSM 4.3). But every time i get the same message after i created the new admin user: „upgrading filesystem cache“ in an empty owncloud screen (the menu items on the left are there, but thats all i can see). Clicking on an other menu item, lets say calendar, it takes minutes before the screen is changed. Clicking on menu item „files“ brings me back after minutes to the same message: „upgrading filesystem cache“.
Can anyone see what i am doing wrong??
Thanxx in advance,
Wyl
Incredible points. Great arguments. Keep up the amazing spirit.
My web page – St-Aquinas.org
I really just wanted to destroy the toxic mold spores that were
deep in my carpets in which i was successful.
Make a decision by taking into consideration the efficiency
and prices of their expert services. If you can provide
the elbow grease, and clean up the most visibly obvious cause of odors, the Bio3Blaster can do the rest.