Beiträge von Joseph885412

    Were you able to find a solution?

    Hi Snakyjake,

    That was almost 2 years ago. I don't remember if I've found a solution or not. I think I simply recreated the VM from scratch... (It was a test VM so not much settings had been fiddled with).


    Maybe someone could backup the settings somehow, create a new OMV VM from scratch and restore the settings? It looks like there isn't an easy way to do this.


    Zitat

    olivercer

    ·2 yr. ago

    The easiest thing? Make a video recording while browsing the web GUI and write down your configuration. I've done it already a couple of times and came up with a huge doc/wiki about my install!


    https://www.reddit.com/r/OpenM…tm_medium=web2x&context=3


    Zitat

    Can I backup or restore an existing openmediavault configuration?There is no regular backup/restore procedure, but yes, in some way: keep the file /etc/openmediavault/config.xml for references purposes if the option is to go for a clean re-install.

    https://openmediavault.readthedocs.io/en/latest/faq.html



    How to backup using openmediavault-backup plugin:

    I have written quite a few posts about how to restore. This is probably the best one - How to restore from an omv-backup?


    I hesitate on making anything much better because someone would try to cut & paste and make their system worse.


    RE: How to backup and restore OMV configuration ? BMR Plan - howto?

    I have this working fine with the following. The backup is operating normally, since yesterday.




    Your container goes to the webUi, but it doesn't show you the login screen. When it works normally, we see the login screen right away.

    I've tried the following and it's the same problem ([CrashPlanEngine] starting... over and over again)

    StorageTest folder didn't exist before. It's Docker who created it. And weirdly if gives owner and group to root user.


    But for the Config__CrashplanPro folder, which Docker also created (and which didn't previously exist either), it gives owner to dockeruser and group to users:


    Isn't that odd?

    I did create a new "config_crashplan" folder on the root of the data drive and did set: Owner:dockeruser rwx, Group:users rwx, Other rwx.

    Then created a new docker like this:

    Crashplan doesn't want to start with this.


    Permissions of the config folder:


    If I look at the permissions of one of the folders (bin) inside config_crashplan folder: (This was created by docker)

    OK,

    This the root of my Data drive. I didn't set or change those permissions myself. It's probably OMV GUI who did it when I first setup OMV. Or maybe a change happened after that. I don't know.


    What's the root of data drive supposed to have for permissions?


    Even if I create a "crashplan_config" folder on the root of the data drive, with User:dockeruser rwx, Group:users rwx Others:r-x, and I tell Docker to save the config over there, Crashplan docker doesn't show me the login page.

    Weird... when I create new users, they've always been assigned incrementally from 1000... so for me to get to 2028, I'd have to have over 1k users (misspoke on the 2k, but the point still stands)


    The fact it works on the home directory, but not the data drive... makes me suspect there is a permission issue.


    Is your Home directory on the Data drive? Otherwise if you have a small OS drive, you may fill it up quickly.

    Yes I guess it's weird.


    How do I check for permission issues exactly?


    My Home directory is on the the OS drive, which is 250GB (98% free).


    Here's the permissions for my main Data drive:


    Everytime I create a new shared folder from OMV GUI on that drive, the owner is always root rwe, Group: users rwe, Others: rw.

    OK I've managed to make it work like this:

    I can absolutely live with this.

    I thinks it's weird though, that I can store the config in the Home folder but not on one of the storage drives. Don't you?

    What does not work? Which error do you get?

    I don't get the CrashPlan login screen. If I look at the log, it's stuck on :

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,


    Here's the full log:

    Hi macom,

    Tried that and it didn't work. User 2028 is "dockeruser".


    The folder /srv/dev-disk-by-label-NVMe500GB/CrashplanPro_Docker was created by the docker. Here's what the permissions look like:

    Hi there,


    I was having some hard time creating a CrashPlan Pro docker. CrashPlan would start. I've troubleshooted and found that if I didn't specify any Volumes in the Compose file, CrashPlan would start OK. Good.


    Then I've tried specifying a storage volume. It works. Crashplan starts. It created it's own config folder here by itself:

    /var/lib/docker/volumes/4345af57db0eb193671b1872ec653b97e1d553332ca0c8460019a6bb01ab26de/_data


    But If I try to specify the /config volume, CrashPlan doesn't start.


    So this works:

    But this doesn't work (only difference is the additional volume):


    I didn't create the ../Settings/CrashplanPro_Docker folder at first. I wanted docker to create it by itself. Which it did. But CrashPlan doesn't want to start.


    At the end of the log, we see:

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,

    [CrashPlanEngine] starting...,



    Any ideas why this wouldn't work?