New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.6.3+ boot error #173
Comments
I don't have this issue. Are you using your own encryption key? |
Yes, I am. But I've been using the same custom encryption key for quite a while now (at least more than a year) |
The issue seems related to the CP version 6.9.4. Can you verify with CP support team if this is a known issue? I will try to reproduce on my side... |
So I tried to reproduce by configuring a device with a custom encryption key, without success. Where you able to contact the CrashPlan support? |
Sorry for not responding earlier, it's been a bit hectic :)
I've got in contact with them, but once I told them it was running on a
docker container, they immediately 'set me aside', as it is not one of
their supported platforms. :(
…On Tue, 7 May 2019 at 01:45, Jocelyn Le Sage ***@***.***> wrote:
So I tried to reproduce by configuring a device with a custom encryption
key, without success.
Where you able to contact the CrashPlan support?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALGAUV6EMRIFNSAS6T2ASTPUDGJTANCNFSM4HI2GG4Q>
.
|
Yeah this is very unfortunate... |
If you are interested in helping debugging this issue, you could provide remote access to your container or a copy of the container's appdata. Since I cannot reproduce on my side, there are a couple of things I can investigate using your setup. |
Hi, since part of what I'm backing up is actually sensitive data, I'd
prefer not to grant remote access to the container. Where can I find the
appdata for the container? If I see that there's no sensitive data there, I
have no problem with sharing that :)
…On Fri, 10 May 2019 at 03:20, Jocelyn Le Sage ***@***.***> wrote:
If you are interested in helping debugging this issue, you could provide
remote access to your container or a copy of the container's appdata. Since
I cannot reproduce on my side, there are a couple of things I can
investigate using your setup.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALGAUXMYVKNA54JPS5J7CDPUTLW3ANCNFSM4HI2GG4Q>
.
|
Closing this issue. Please re-open if needed. |
First of all, thanks for the awesome container :)
Now for the bad part, after upgrading to v2.6.3, my container went into a boot loop, with the following error on the
service.log.0
file:Followed by the XML contents.
If I downgrade to v2.6.3, the same error occurs, but if I downgrade to v2.6.2, everything works.
Any idea why?
Thanks
The text was updated successfully, but these errors were encountered: