Posts Tagged ssh

Installing Unison on a Synology DS411j NAS

Posted by LAV in File sync on May 1, 2011

Since my full-tower 10 hdd raid5 server is apparently making too much noise and polluting the air in the room too much (can’t imagine why, just because it has 6 fans?), I bought a NAS as a first step towards replacing the server with something less.. bulky. I got a Synology DS411j NAS, and have spent the last 24h moving data around so that I could use 4 existing WD 1.5 TB drives in it. Seems to be working very well so far and the Synology web gui (DSM) is quite impressive. However, it doesn’t have Unison and if there is one thing I need it’s Unison!

Luckily it is possible to install it:

  1. Follow the Synology guide for installing ipkg/bootstrapping your NAS. (The DS411j has a Marvel Kirkwood mv6281 ARM processor.)
  2. Install the required packages with: ipkg install ocaml make gcc
  3. Now the tricky part, for me Unison didn’t compile initially due to errors in /opt/arm-none-linux-gnueabi/lib/libpthread-2.5.so. Somehow this library is not the correct version, but the correct version IS installed in /lib.
    Fix this by deleting the symlink /opt/arm-none-linux-gnueabi/lib/libpthread.so.0, and creating a new one to /lib using: ln -s /lib/libpthread.so.0 /opt/arm-none-linux-gnueabi/lib/libpthread/
  4. Then download the unison source code somewhere (eg /volume1/@tmp), go there and run: make UISTYLE=text NATIVE=false
  5. There might be some error messages, but in the end a functional unison binary is created!
  6. Copy the binary to for example /opt/bin. Set up SSH keys for the root account, and we’re all set!

, , ,

8 Comments

known_hosts for SSHKeychain

Posted by LAV in Other on October 30, 2009

SSHKeychain is, if you’re not familiar with it, a very convenient OSX app that sits in the menu bar and can create and maintain multiple automatic SSH tunnels, something I use a lot. I recently reinstalled my home server which caused its ssh fingerprint to be changed, so (because I’m lazy) I just deleted all my .ssh/known_hosts-files to stop SSH from complaining about it.

But for some reason SSHKeychain still refused to set up a tunnel to that server, with the unhelpful error message: “The tunnel has unexpectedly terminated repeatedly. It will not be restarted.” From the terminal I had no problem connecting to said server with SSH, so I couldn’t understand what was wrong.

But as it turns out, SSHKeychain uses the root account’s known_hosts, located at /var/root/.ssh/known_hosts on OSX. And since my server had the wrong fingerprint it refused to connect. Deleting said known_hosts file of course fixed the problem!

,

No Comments