Wednesday, 19 June 2013

SpiderOak 5.0.1 on CentOS 6.4 x86_64

SpiderOak is the best fit for backing up my life. First off they do security properly, (unlike the laughable "most popular" that I would "drop" in a heartbeat.) Secondly they seem like nice people, ( could go on...)

I wanted to add some of the files on my personal server that happened to be running CentOS 6.4 (the 64bit version). So I downloaded the RPM from the SpiderOak site and was hit with some cryptic python error[1]. ( I only have ssh access to that server, so I was only trying from the command line.) I expected that my version of python was missing something, so I tried to fix that. In the end I removed SpiderOak x86_64 and installed the 32bit version... and it worked![0]

Not sure why the 64bit version failed, but as long as it is secure I'm happy, (and when it "failed" it did so securely which is the most important thing.)


[0] well there were some errors:
Synchronizing with server (this could take a while)...
Error setting attribute: Setting attribute metadata::custom-icon not supported
Error setting attribute: Setting attribute metadata::custom-icon not supported
Error setting attribute: Setting attribute metadata::custom-icon not supported
Error setting attribute: Setting attribute metadata::custom-icon not supported


but after Ctrl+c
SpiderOak --include-dir=/var/lib/mysql
seemed to work
and 
SpiderOak -v --batchmode
did the job (the -v is useful to give you confidence as to what SpiderOak is doing. i.e. it is for you; SpiderOak will be fine without it.) 

[1]alexx@www ~$ SpiderOak --setup=-
Traceback (most recent call last):
  File "<string>", line 6, in <module>
  File "__main__.py", line 128, in <module>
  File "__main__SpiderOak__.py", line 12, in <module>
  File "ssl.py", line 60, in <module>
ImportError: libkrb5.so.3: cannot open shared object file: No such file or directory

No comments:

Post a Comment

About this blog

Sort of a test blog... until it isn't