suman
February 9, 2016, 3:02am
1
I think many in our community expressed interest in a Crashplan Rock-on. Thanks to @joshi for opening a pull request with this contribution. I haven’t tried it myself yet, but want to post here so everybody is aware and those interested can test it pretty easily and provide any feedback.
Follow these steps
ssh into your Rockstor box as root user.
mkdir -p /opt/rockstor/rockons-metastorecurl -o /opt/rockstor/rockons-metastore/crashplan.json https://raw.githubusercontent.com/joshiegy/rockon-registry/master/crashplan.jsonclick update button in Web-UI’s Rock-Ons screen. You should see CrashPlan. Proceed by clicking Install.
1 Like
joshi
February 9, 2016, 5:25am
2
A note on how to connect to crashplan afterwards.
ssh to Rockstor box as root
cd to the directory which you selected for config
open the “id” folder and run “cat .ui_info”
Copy that to your “.ui_info” on your own laptop or similar and run CrashPlanDesktop from there.
@suman - How do I add this info to the webui of Rockstor?
crashplan always crashes on me. It works at first, then when i access it remotely and set it up. I disconnect it from my mac and then it stopps working. and will not start back up. I have no idea why it does that. It is kind of annoying. My rock-on’s in general dont work the way i want them too. I feel like im beta testing sometimes.
henfri
February 20, 2016, 6:00pm
4
Hello,
last time I checked, this did not yet exist. So I build my own. Now that I want to share it, I find this post… That was unfortunate.
Anyway, here it is:
Hello,
here it is:
{
“CrashPlan”: {
“containers”: {
“Crashplan”: {
“image”: “gfjardim/crashplan”,
“launch_order”: 1,
“opts”: [
[
"–net=host",
""
]
],
“ports”: {
“4242”: {
“description”: “Crashplan Server Port. Suggested default: 4242.”,
“host_default”: 4242,
“label”: “Crashplan Server port”,
“protocol”: “tcp”
},
“4243”: {
“description”: “Crashplan Server Port. Suggested default: 4243.”,
“host_default”: 4243,
“label”: “Crashplan Server port”,
“protocol”: “tcp”
},
“4280”…
With my RockOn, you do not need to install Crashplan on your Desktop, but you access Crashplan on your RockOn via a built-in web-VNC.
Greetings,
jurgc11
February 22, 2016, 10:18pm
5
Hi Joshi,
I installed your Crashplan rock-on and it was all working nicely for a day or so. However, it’s now showing as stopped in the web UI and starting it again doesn’t work. I dug a little deeper and tried starting the container from the command line and got the following output (the container stopped immediately afterwards):
docker start 95b3a6761b51
================
Container written by Joshi Friberg
Crashplan is running with pid ..
Enter these parameters to /var/lib/crashplan/.ui_info, change 'RockStor-IP' to your 'RockStor-IP'
4243,c6597aa5-s101-4280-8802-9b45c0e9929f,RockStor-IP
Start time was: Mon Feb 22 21:27:33 UTC 2016
I also tried tailing /crashplan/crashplan/logs/* from within the container but I couldn’t see anything very illuminating. I’m totally new to docker (you probably guessed
Any ideas where I can go next? Or better yet, what the problem might be?
Thanks!
joshi
February 23, 2016, 12:13am
6
Hmm… Looks like Crashplan does not start at all in the container. You can lookbfor clues in your rockstor-servers logfiles since rockstor use syslog. You can also look at the Crashplan-logs under (config-dir-on-rockstor)/crashplan/crashplan/logs.
joshi
February 23, 2016, 12:15am
7
Hi,
Do you mean all CrashPlan installations or my container in perticular?
henfri
April 6, 2016, 7:45pm
8
Hello,
I wanted to try your rock-on, but unfortunately, the container keeps re-starting:
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: ================
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: Container written by Joshi Friberg
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: Crashplan is running with pid ..
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: Enter these parameters to /var/lib/crashplan/.ui_info, change 'RockStor-IP' to your 'RockStor-IP'
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: 4243,9c60473a-1f49-4b5b-9ede-54c261c4e1a6,RockStor-IP
Apr 6 21:38:55 homeserver docker/9962f342bfed[14304]: Start time was: Wed Apr 6 21:38:55 CEST 2016
Apr 6 21:38:55 homeserver systemd[1]: Stopped docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:38:55 homeserver systemd[1]: Stopping docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:38:55 homeserver systemd[1]: Started docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:38:55 homeserver systemd[1]: Starting docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:38:55 homeserver kernel: docker0: port 4(veth21123eb) entered disabled state
Apr 6 21:38:55 homeserver kernel: vethfc45388: renamed from eth0
Apr 6 21:38:55 homeserver NetworkManager[2492]: <info> (veth21123eb): link disconnected
Apr 6 21:38:55 homeserver NetworkManager[2492]: <warn> (vethfc45388): failed to find device 26 'vethfc45388' with udev
Apr 6 21:38:55 homeserver NetworkManager[2492]: <info> (vethfc45388): new Veth device (carrier: OFF, driver: 'veth', ifindex: 26)
Apr 6 21:38:55 homeserver avahi-daemon[30736]: Withdrawing workstation service for vethfc45388.
Apr 6 21:38:55 homeserver kernel: eth0: renamed from vethfc45388
Apr 6 21:38:55 homeserver NetworkManager[2492]: <warn> (vethfc45388): failed to disable userspace IPv6LL address handling
Apr 6 21:38:55 homeserver NetworkManager[2492]: <info> (veth21123eb): link connected
Apr 6 21:38:55 homeserver kernel: docker0: port 4(veth21123eb) entered forwarding state
Apr 6 21:38:55 homeserver kernel: docker0: port 4(veth21123eb) entered forwarding state
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: ================
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: Container written by Joshi Friberg
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: Crashplan is running with pid ..
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: Enter these parameters to /var/lib/crashplan/.ui_info, change 'RockStor-IP' to your 'RockStor-IP'
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: 4243,9c60473a-1f49-4b5b-9ede-54c261c4e1a6,RockStor-IP
Apr 6 21:39:06 homeserver docker/9962f342bfed[14304]: Start time was: Wed Apr 6 21:39:06 CEST 2016
Apr 6 21:39:06 homeserver systemd[1]: Stopped docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:39:06 homeserver systemd[1]: Stopping docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:39:06 homeserver systemd[1]: Started docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:39:06 homeserver systemd[1]: Starting docker container 9962f342bfed756dbab29b9cffb6e35e0351879a0b1d593fcb31a4ee6bda6126.
Apr 6 21:39:06 homeserver kernel: docker0: port 4(veth21123eb) entered disabled state
Apr 6 21:39:06 homeserver kernel: vethfc45388: renamed from eth0
Apr 6 21:39:06 homeserver NetworkManager[2492]: <info> (veth21123eb): link disconnected
Apr 6 21:39:06 homeserver NetworkManager[2492]: <warn> (vethfc45388): failed to find device 26 'vethfc45388' with udev
Apr 6 21:39:06 homeserver NetworkManager[2492]: <info> (vethfc45388): new Veth device (carrier: OFF, driver: 'veth', ifindex: 26)
Apr 6 21:39:06 homeserver avahi-daemon[30736]: Withdrawing workstation service for vethfc45388.
Apr 6 21:39:06 homeserver NetworkManager[2492]: <warn> (vethfc45388): failed to disable userspace IPv6LL address handling
Apr 6 21:39:06 homeserver kernel: eth0: renamed from vethfc45388
Apr 6 21:39:06 homeserver NetworkManager[2492]: <info> (veth21123eb): link connected
Apr 6 21:39:06 homeserver kernel: docker0: port 4(veth21123eb) entered forwarding state
Apr 6 21:39:06 homeserver kernel: docker0: port 4(veth21123eb) entered forwarding state
I don’t see any errors in the logs in the Crashplan Logs Folder.
Any Ideas?
Greetings,
) so i’m not sure if this is the way to go about debugging.