OwnCloud add-on thread

Well, I've followed the instructions on slobberbone's website - and successfully updated my OwnCloud installation.
Since my previous installation did not contain a "data" subdirectory, I did not create the symbolic link; this was the only deviation from slobberbone's instructions. Ah, and yes - I did specify a different hostname since owncloud-latest.tar.bz2 is not really the latest version (I did use owncloud-4.5.5.tar.bz2 instead).

Maybe slobberbone could provide some insights (in English, please - on the website there are some French explainations but I'm unable to translate them) on the necessity to create the symlink.

Cheers, Wolfgang

Hello, I've updated my website to make the english version ;)
Effectively, the link with "latest" of the latest owncloud version, doesn't work, we have to specify the link of the version how we want ... all it says on my website ... i hope ;)

I've attempted this but each time I get to the point of executing the tarball I receive an error that there is no such file (I do replace the generic "latest version" with the correct name). At first I thought this was because the instructions are not specific to a Duo v1, but WSJ has had success with the same model. I'm obviously missing something but am not familiar enough with the unit (or Linux) to know what it is. I'm taking for granted that the download is saving to the folder I'm in at the time I do it (tmp) and the fact that there's no path stated in the instruction tends to back that up. Am I wrong on this? What can I do to get past this roadblock?

Hye, when you execute my script, where have you a problem ?

#!/bin/bash

cd /tmp
rm -Rf owncloud*.*
#wget http://mirrors.owncloud.org/releases/owncloud-latest.tar.bz2
wget http://mirrors.owncloud.org/releases/owncloud-4.5.5.tar.bz2
#rm -Rf /usr/share/owncloud_*
mv /usr/share/owncloud/ /usr/share/owncloud_save
#tar -xjf owncloud-latest.tar.bz2
tar -xjf owncloud*.bz2
mv owncloud /usr/share/
chown -R admin:admin /usr/share/owncloud/
cd /usr/share/owncloud/
ln -s /c/.owncloud/data/ data
cp -R ../owncloud_save/config/ ./
cp -R ../owncloud_save/.htaccess ./
cp -Rn ../owncloud_save/apps/ ./
chown -R admin:admin /usr/share/owncloud/
cd /etc/frontview/
apache-ssl -f /etc/frontview/apache/httpd.conf -k restart

from http://www.slobberbone.net/dotclear/index.php?post/2012/10/26/Mise-%C3%A0-jour-d-ownCloud-depuis-mon-ReadyNas-Ultra-4

Though I didn't realize this before, the problem starts at the first command: #!/bin/bash
which returns: "-bash: !/bin/bash: event not found"
I originally thought the # indicated a remark line and ignored this.

The next issue happens at: "tar -xjf owncloud*.bz2" (which I tried as provided but also replaced with "tar -xjf owncloud-4.5.6.tar.bz2" to see if I got different results)
It returns -
"tar: bzip2: Cannot exec: No such file or directory"
"tar: Error is not recoverable: exiting now"
"tar: Child returned status 2/"
"tar: Error exit delayed from previous errors"

Finally: "mv owncloud /usr/share/"
gives me "cannot stat `owncloud': No such file or directory"

I don't go beyond this as there doesn't seem to be any point to it after being told the files don't exist.

I am connecting via PuTTY as root and entering the commands one at a time, not as a script. I don't feel this changes anything for the errors I'm receiving, but it is possible this is where my error lies. If that is the case, is there a particular folder or share where the script needs to be?

Thanks very much for any and all help.

So If I understand all, you connect to your ReadyNAs Duo with Putty (ssh) and you pull all lines before one by on.

In bash all line with # is a comment.

I explain the first 10 lines :

#!/bin/bash

-> it's to specify in a script the shell used, in our case bash, the one you have probably when you connect with you putty

cd /tmp

-> go in the /tmp directory

rm -Rf owncloud*.*

-> remove old download packet of ownCloud

#wget http://mirrors.owncloud.org/releases/owncloud-latest.tar.bz2

-> comment

wget http://mirrors.owncloud.org/releases/owncloud-4.5.5.tar.bz2

-> wget is a tool that download the owncloud packet at this url (to adapt at the version you wish (you have to do that with all patches from the original provide by the ReadyXtra add-on)

#rm -Rf /usr/share/owncloud_*

-> comment, before I removed the old backup instance of owncloud, but by security, : comment ;)

mv /usr/share/owncloud/ /usr/share/owncloud_save

-> we make a backup of our owncloud instance

#tar -xjf owncloud-latest.tar.bz2

-> comment

tar -xjf owncloud*.bz2

-> wu untar the download packet of owncloud

After that, when all it's ok, continue my instructions, if necessary I explain you the rest of the script later !

Merci slobberbone pour l'aide. Je ne reussis pas à dépasser ça:

Backup-1TB:/tmp# wget http://mirrors.owncloud.org/releases/owncloud-latest.tar.bz2
--00:44:16-- http://mirrors.owncloud.org/releases/owncloud-latest.tar.bz2
=> `owncloud-latest.tar.bz2.1'
Resolving mirrors.owncloud.org... 50.30.42.17
Connecting to mirrors.owncloud.org|50.30.42.17|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://owncloud.org/releases/owncloud-latest.tar.bz2 [following]
--00:44:17-- http://owncloud.org/releases/owncloud-latest.tar.bz2
=> `owncloud-latest.tar.bz2.1'
Resolving owncloud.org... 50.30.42.17
Reusing existing connection to mirrors.owncloud.org:80.
HTTP request sent, awaiting response... 200 OK
Length: 9,188,594 (8.8M) [application/x-bzip]

100%[========================================================>] 9,188,594 1.22M/s ETA 00:00

00:44:25 (1.08 MB/s) - `owncloud-latest.tar.bz2.1' saved [9188594/9188594]

Backup-1TB:/tmp# tar -xjf ./owncloud*.bz2
tar: bzip2: Cannot exec: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
Backup-1TB:/tmp# tar -xjf owncloud-latest.tar.bz2
tar: bzip2: Cannot exec: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors



Any clue?

Well, it appears that I have no bzip2 pkg installed. And, of course, beeing on SPARC platform, I have APT neither :-). Working on it ...

beosro, I've just tested the wget and untar lines mentioned above, and all worked as it was supposed to.

I'm not sure why the # is appearing at the start of a couple of lines, but that's by the by, as that won't help anything AFAIK.

cd /tmp will move you into the correct working directly, which in this instance the writer wants you to use /tmp.

wget http://mirrors.owncloud.org/releases/ow ... .5.tar.bz2 will download Owncloud in to the /tmp directory you are in.

tar -xjf owncloud*.bz2 will extract the Owncloud to it's own new folder in /tmp. (E.G. owncloud-4.5.5)

If the last line fails I would check the permissions set on your /tmp folder. (Or where ever you are saving the files to if you are choosing your own preferred directory/folder.)

You are logging in as root I assume, when SSH'ing to the box?

EDIT - Seen you newer post. There is an addon for APT. Install that.

Once done, run this

apt-get update && apt-get install build-essential

The APT package is toward the bottom of the page HERE: http://www.readynas.com/?page_id=617

Once installed and the NAS restarted, run apt-get update, then apt-get install bzip2. That's as far as I've gotten so far, but I think that should do it. I often take for granted as a tech that my clients "just know" things because I'm so used to doing those things. I suppose it's the same when you're a developer. You don't always realize that most folks don't have all the goodies you have on your machine.

-------------------------------------------------------

Success!! Once the foundations were in place everything went smoothly. There was one other minor hiccup, in that during Apache restart, an error message indicated that the Servernam couldn't be identified. This did not stop the process from completing. Apparently, this should be specified in httpd.conf, and I may get around to adding that line, but only if I see that it's causing problems.

Many thanks for the help, and I hope my added info can help others.