Have you struggled to get crash plan to start?
Have you tried altering run.conf (with the service stopped, with the jail stopped, from the freenas shell.... hell have you even tried taking the hard drive out and changing the bits by yourself with a screw driver) only to turn it all back on, and BOOM... your changes are reverted.
Well this has been happening to me! and happening all the time... My Xms heap space was 6000m, I was advised to increase it because of some very large files.... well now crash plan since updating to 4.2.0 won't start... every time I tried start it I get this in the engine log..
only i can't change run.con as it reverts... Well AFTER HOURS of trial and error I have found the following file....
/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml
Inside this file was a reference to my 6000m.
I changed it... and now it starts just fine...
Thought I'd share..
Have you tried altering run.conf (with the service stopped, with the jail stopped, from the freenas shell.... hell have you even tried taking the hard drive out and changing the bits by yourself with a screw driver) only to turn it all back on, and BOOM... your changes are reverted.
Well this has been happening to me! and happening all the time... My Xms heap space was 6000m, I was advised to increase it because of some very large files.... well now crash plan since updating to 4.2.0 won't start... every time I tried start it I get this in the engine log..
Code:
Invalid maximum heap size: -Xmx6000m The specified size exceeds the maximum representable size. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
only i can't change run.con as it reverts... Well AFTER HOURS of trial and error I have found the following file....
/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml
Inside this file was a reference to my 6000m.
I changed it... and now it starts just fine...
Thought I'd share..