generalz

nice, now thats some service

correct. freenas guys are having the same problem with the bsd jail (similar to docker) I haven't looked into it. its worse when the program has an internal database for settings or usage because then you get into a situation where the db is newer then the program.

well for one the changes are not saved when you stop and start the container again and it goes through the update process again. the java updates stop the services and since the containers dont start services like a normal *nix box it breaks.

Crashplan is pushing java updates out. will probably break this container in the next few days if it hasn't already.

this is working as intended per crashplans instructions. if you want to use the UI without ssh you need to modifiy my.service.xml in your appdata\crashplan\conf change it from 127.0.0.1 to 0.0.0.0 <serviceUIConfig> <serviceHost>127.0.0.1</serviceHost> <servicePort>4243</servicePort> <connectCheck>0</connectCheck>

you need to create a crashplan share without cache drive usage and map that in the container setup. then change the default destination on the crashplan server to go to that share for incoming backups

You can change the umenu port to mine runs on 81

I wonder... Is it even doable? Can we pass the tuner to the container? For people with a network tuner. IE hd homerun

I'm not sure, maybe for a new install. As an existing user i mapped /mnt/user/:/mnt/user/:rw so that crashplan would continue on like nothing happened.

take the # out from the port should look like this. I use 4200 as per crashplans faqs'

If you never complain, it never gets fixed.... I think I fixed it. Please try again. i did, just in the wrong area http://lime-technology.com/forum/index.php?topic=33965.msg323085#msg323085 I removed and re-added and move some files around and it seems to be stable this time, thanks!

is there a way to get the time set right in the logs? using the extended config addon for unraid and bind time is checked but the time is still way off

dropbox. one that has a template does not work.

must be based on location. mines not using much of any cpu and it maxing out 15mbps

im sure there is a command line for docker to do that.. but you can go into the settings of crash plan and tell it how much cpu to use.

yea thats what I do. create a share called "crashplan" and set "Use cache disk: NO" then on your docker config map /crashplan to your host /mnt/user/crashplan

ahh. that's what i thought, I disabled spindown when 13 came out. just wanted to make sure that it wasn't something else. crashplan pretty much keeps all my drives up anyways.

what isn't working other then spin down? Im running 3 m1015's flashed with p13 (p14 was released after I flashed them). I am running on 5.0Beta12. I can confirm from experiance that betas 13 & 14 do not work with LSI cards.

im using the Bri10 on 14, i have spin down turned off. so if your not partial to spin down it should work ok

That sounds like the problem spinning up the drives all the LSI owners had with beta 13 & 14, which is why beta12a is recommended. Which version did you have problems with? thank you. looks like beta 11 did the trick. spin up and down is working with my BRi

That sounds like the problem spinning up the drives all the LSI owners had with beta 13 & 14, which is why beta12a is recommended. Which version did you have problems with? i started having it in 12, i'm going to try to go back to 11 and see if that helps.

BR10i spin down is not working fyi. unsure about the m1015 the drives spin down fine but when something goes to write to a drive that spun down it does not wake up the drive and the errors start piling up in syslog and then unraid disables the disk and you have deal with drive reconstruction and a parity sync