tmchow

Given the latest confirmation about the way it works for seamless upgrade, CrashPlan Business seems like the right way to go to support unlimited data. Spideroak and others have limits. My crashplane home subscription goes until Nov 2018, but wonder if I should just upgrade now to lock in the 75% discount.

Looks like SpiderOak just unveiled a deal for crashplan refugees giving 30% off their monthly and yearly plans: https://spideroak.com/lifeboat-one-crashplan-rescue/ However, unclear whether they support running in a docker and/or unraid.

My understanding is the 75% discount is only for first year. Do we know the pricing beyond first year yet?

It’s $5 per month more per machine.

I've got same issue. 2017-04-26 00:44:29,940 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47766644101704 for <Subprocess at 47766644075408 with name nzbget in state STARTING> (stdout)> 2017-04-26 00:44:29,940 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47766657681024 for <Subprocess at 47766644075408 with name nzbget in state STARTING> (stderr)> 2017-04-26 00:44:29,941 INFO exited: nzbget (exit status 127; not expected) 2017-04-26 00:44:29,941 DEBG received SIGCLD indicating a child quit 2017-04-26 00:44:32,945 INFO spawned: 'nzbget' with pid 53 2017-04-26 00:44:32,949 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-26 00:44:32,950 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-26 00:44:32,950 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47766644101704 for <Subprocess at 47766644075408 with name nzbget in state STARTING> (stdout)> 2017-04-26 00:44:32,950 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47766657680808 for <Subprocess at 47766644075408 with name nzbget in state STARTING> (stderr)> 2017-04-26 00:44:32,951 INFO exited: nzbget (exit status 127; not expected) 2017-04-26 00:44:32,951 DEBG received SIGCLD indicating a child quit 2017-04-26 00:44:33,952 INFO gave up: nzbget entered FATAL state, too many start retries too quickly

#description=Clean up docker log sizes on your system echo "" echo "<font color='red'><b>Before:</b></font>" echo "=====================================================================================================================================================================================" du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 | grep .log echo "=====================================================================================================================================================================================" echo "Cleaning Logs:" logs=$(find /var/lib/docker/containers/ -name '*.log');for log in $logs; do cat /dev/null > $log;done sleep 6 echo "...<font color='blue'>cleaning complete!</font>" echo "" echo "<font color='green'><b>After:</b></font>" echo "=====================================================================================================================================================================================" du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 | grep .log echo ""

Having a weird issue using the "description" variable. In the Clean Docker Logs script, I killed the description file and moved it to a variable with this as the first line of the script: #description=Clean up docker log sizes on your system However, this doesn't work and the user scripts UI tells me no description is present I removed one word at a time to see what was breaking it, and it wasn't until I removed the words "on your system" that it worked: #description=Clean up docker log sizes This isn't about line length since other scripts I'm using descriptions that are much longer, such as #description=This script will display the size of your docker logs, so you can see if runaway logging is contributing to your docker.img file filling up What am I missing?

Just tried installing this from lukeadair's repo and am getting this error: Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: archive/tar: invalid tar header any ideas? Ignore this, got it to work by just retrying twice. Another issue right now is Unraid isn't' telling me there's any port mappings. I'm new to creating my own port mappings for docker in unraid. I tried to add a custom port, but there are no fields to specify container vs host port which I find confusing. Anyone have a quick tip?

Scratch my last comment. If i set network type to "Bridge" instead of "Host", Home Assistant "Discovery" does not work for some reason. None of my devices cannot be discovered like sonos. I had to also remove the port mapping since it's in host mode since it's not necessary. Default port of 8123 works fine to load webui

Thanks for this tip. Installed with no issues and could load Web UI.

Something has happened and now the WebUI doesn't load again.. had this issue months ago but now it's back. In the docker logs, I'm seeing piles of lines like this: "$TARGETDIR/lib/com.backup42.desktop.jar:$TARGETDIR/lang" com.backup42.service.CPService > /config/log/engine_output.log 2> /config/log/engine_error.log

You can also just run update_cron to update the from schedules for changes in /boot/confit/plugins

Started using this to try it out so I could get a UI for Cron, as well as a way to run scripts one-off if I wanted. I wish the folder structure to add scripts wasn't like the way it was with a sub-folder and 2 separate files. I think a better approach would be to just use a single file that had comment markup within the scripts that provided the description that the plugin used. IOW, I'd like to have a script called /boot/config/plugins/user.scripts/scripts/delete_dangling_images.sh instead of /boot/config/plugins/user.scripts/scripts/delete_dangling_images/script. Benefit is that the script purpose is easier with the filename, rather than a name of "script" and needing to rely on the folder it's in to understand context (or looking at the script itself). I think it would reduce friction in adding new scripts too. Question about scheduling: how does the scheduling actually work? When I choose "Daily" or "weekly" there doesn't seem to be options for what time or day of week. Does it just choose the same time to run all scripts or is there something else going on that I'm missing?

Raising this old thread from the dead. After looking at this, there are a few options for managing Cron jobs: 1. Manually using crontab. Not really recommended given other better options. 2. Manually add in scripts into /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly or /etc/cron.monthly. Not recommended, this is not easier than other options. 3. Put cron scripts into /boot/config somethere (e.g. /boot/config/plugins/custom_cron/). These scripts are all automatically loaded on system start into /etc/cron.d/root/. If you make changes and want them applied, just run the command update_cron which reloads all the custom crons in /boot/config/plugins/custom_cron/). 4. Use the User Scripts plugin. This creates a folder /boot/config/plugins/user.scripts/ with a sub-folder called scripts. For each script, you create a sub-folder in /boot/config/plugins/user.scripts/scripts/, containing 2 files: Description and Script. Description is the 1 line description of the script that shows in the UI. The Script is the actual script. There is then a UI in the Unraid WebUI that allows you to run it one-off in foreground or background and supports custom scheduling using cron syntax. Best of every world. This is the best option and works even for the latest version of unraid (6.8.0 as of my last edit)

When you schedule scripts to be run, how are they scheduled? I expected through crontab, but when i show all cron jobs with "crontab -l" i don't see it.

As mentioned my crash plan client is working again. However I notice backups stop midway with the message "waiting for connection". In settings it says it can't reach crashplan central. However I know it's able to connect periodically since the outstanding backup payload is decrementing. Any ideas why it can't get connection? Sent from my iPhone using Tapatalk

FYI my crash plan is now working. No more black screen not sure what changed. Sent from my iPhone using Tapatalk

For those saying it is working now, did it ever stop working in past few weeks? Or was it always working? Sent from my iPhone using Tapatalk

still broken for me. Going to webUI, VNC session shows me black screens still.

Welcome to the club... For me it always has "connection" issues and after wasting many hours trying to make it work to no avail, I had to quit. I hope a new more serious version will come out one day. Some extra info on this. turns out that crashplan was reporting that my server was backing up. So even though there was no UI when I tried to view the "WebUI" launching from unraid docker screen, it looks like the engine was running. I've tried to connect to my server port 4280 using two different windows VNC clients (VNC Viewer and TightVNC) and both get rejected with an error close to "connection closed unexpectedly".

I've had crashplan working in docker container for months, but I just connected to add some new backup folders, and found out that it hasn't backed up in almost 7 days. Says there was an error connecting to the crashplan service. I stopped the container and restarted it, but now when I try to access the WebUI like I had in the past, I get a black screen where the crashplan UI used to show. I still get the chrome around it which says "Connected (unencrypted) to: CrashPlan", which I think is the VNC UI. I have tried to force update the container but still no luck. Any ideas?

hmm.. did the uninstall and delete but still no luck. Makes me think I may have built the package wrong. All i did was download the lftp zip from the source, then executed a make <pkg-name>. Was i supposed to do anything else to correctly build it like specify any configuration options? I use a slack build script and latest source. You have to install a bunch of packages to build it also. Ugh sorry for the run around. I must've done something wrong with the build then. Would really appreciate it if you could build and update the master branch with latest 4.7.3 pkg! Sent from my iPhone using Tapatalk No problem, I'll try and compile it here in a bit Thanks so much! Got the new package and it works. Would be great for you to post instructions on compiling new packages somewhere so we can help contribute (properly) in the future

hmm.. did the uninstall and delete but still no luck. Makes me think I may have built the package wrong. All i did was download the lftp zip from the source, then executed a make <pkg-name>. Was i supposed to do anything else to correctly build it like specify any configuration options? I use a slack build script and latest source. You have to install a bunch of packages to build it also. Ugh sorry for the run around. I must've done something wrong with the build then. Would really appreciate it if you could build and update the master branch with latest 4.7.3 pkg! Sent from my iPhone using Tapatalk

hmm.. did the uninstall and delete but still no luck. Makes me think I may have built the package wrong. All i did was download the lftp zip from the source, then executed a make <pkg-name>. Was i supposed to do anything else to correctly build it like specify any configuration options?

I assume you're on 6.1. I would have to compile it when I get a chance unless someone else does it. Then push it to the package repo. 4.7.3 is available now for 6.2. Yeah I'm on 6.1.9 still. I'm totally unfamiliar with slackware and linux in general (Mostly a windows guy) otherwise I'd volunteer to compile it. Thanks for compiling it. I merged your PR for 4.7.3 lftp fur 6.1 Hmm.. i updated it but now my system can't find lftp anywhere. Any tips/tricks to getting a package to work again after updating?