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
Docker Container Station Crashplan Small Business QNAP TS-451+ Issues #174
Comments
Just as I posted this, I think I may have figured it out. For folks that are using an antivirus on your NAS (Clam AV in my case) It appears that it may mess with the backup service. Not sure if there is anything that can be done via this project but I will leave open just-in-case. If the rest of my backup completes without issue, I will post here as well. |
This is to be the same issue as #173. Do you have any update about your findings? |
I do, however nothing succeeded. I bumped memory to 6gb and I could get CrashPlan to run for up to an hour or two but then would fall back into waiting for connection. I read the other ticket you linked and I am also using a custom key. I originally tried to take over an existing backup and that didn’t work at all. Then I tried doing a fresh backup and that was the one I could only get working for a couple hours before it went back into the waiting loop |
Is the "waiting loop" you are talking about the same issue as originally reported (i.e. crashplan engine not able to start)? |
Yes. Going to try v2.6.2 as the other person suggested to see if I can get it working. |
Couldn't even login using v.2.6.2. Resetting up via latest version and will post screenshots, logs, and configs in a bit. |
Backup failed at 8.40 about an hour after it started. In total, I got like 2.5 GB up. The thing failed so hard it locked up my NAS. I think it may be an issue with QNAPs implementation of Docker. Images and logs attached in the zip file. |
It seems that you are now getting a different issue. Can you try to chat with the CrashPlan's support team and provide your |
I ended up moving away from my Qnap device. Unraid works perfectly with this container. Assuming it has to do with Qnap's use of Docker. |
Hello folks, I have been banging on this one for almost a day now. I have gotten to the point that all I see is this message in the console in Container Station (Docker) for my QNAP TS-451+
[CrashPlanEngine] starting...
In the ui.log I am seeing
Retrying communication with service connect ECONNREFUSED 127.0.0.1:4244
Error from the service.log.0
Here's my config I have been using
Log Files
Removed
The text was updated successfully, but these errors were encountered: