acurcione

Members
 View Profile  See their activity

  • Posts

    272

  • Joined

  • Last visited

 Content Type 

Posts posted by acurcione

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    26 minutes ago, Djoss said:

    The amount of memory needed directly depends on the amount of data you have to backup, something that probably increases with time.  CrashPlan suggests to allocate about 1GB per TB of backup data.

    Well that’s going to be a problem. I have a total of 37TB currently backed up. It doesn’t go up often any more, but when it does is many GB at a time. 
     

    it’s currently just doing a scan and my memory usage has already doubled from before. I never had this thing stopping like this before and the size hasn’t changed. This is new since the update, but I never did see all those restarts in the logs cause I had no reason to go looking.

     

    If you’re right then even the 6Gb I allocated isn’t going to be enough and I obviously don’t have enough memory to do what’s recommended. Guess I’ll see how this goes. 

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    I can see in the history when it just stops, both in the UI and in the log files. I’m not sure where else to look for errors though. The UI error log is full of errors, but it seems to working so I have no idea if that has anything to do with it. 
     

    here it is just in case:

     

    [936:1113/083714.032167:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.849564:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.849796:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.869040:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083714.869298:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083714.869422:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083714.869537:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [2243:1113/083714.884187:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory
    [2243:1113/083714.898575:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
    [936:1113/083714.907892:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.908125:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.908298:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
    [936:1113/083714.988668:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083715.006942:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [2448:1113/083715.069487:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory
    [2448:1113/083715.073034:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
    [2484:1113/083715.102722:ERROR:egl_util.cc(44)] Failed to load GLES library: /usr/local/crashplan/electron/libGLESv2.so: /usr/local/crashplan/electron/libGLESv2.so: cannot open shared object file: No such file or directory
    [2484:1113/083715.106734:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
    [936:1113/083715.221764:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083715.244763:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083715.850714:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083716.619686:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: libnssckbi.so: cannot open shared object file: No such file or directory
    [936:1113/083716.620196:ERROR:cert_verify_proc_builtin.cc(701)] CertVerifyProcBuiltin for 127.0.0.1 failed:
    ----- Certificate i=0 (C=US,ST=Minnesota,L=Minneapolis,O=CrashPlan,OU=CrashPlan Service,CN=Default) -----
    ERROR: No matching issuer found


    [936:1113/083716.683206:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083716.844730:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083716.902131:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083717.106647:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083717.210573:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    [936:1113/083717.281361:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
    Warning: vkCreateInstance: Found no drivers!
    Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
        at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
        at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
        at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
        at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
        at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

    Warning: Couldn't load Vulkan. Searched /usr/local/crashplan/electron/libvk_swiftshader.so, /usr/local/crashplan/electron/libvk_swiftshader.so, libvk_swiftshader.so.
        at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:299)
        at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:310)
        at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
        at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

    Warning: Failed to load libEGL.so
        at DiscoverPhysicalDevices (../../third_party/dawn/src/dawn/native/opengl/BackendGL.cpp:61)

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    Thanks! Things are back to normal and I was able to update. Now CrashPlan Pro keeps crashing after some time and I can’t figure out why. I see nothing in the system logs, but when I hopped into the appdata folder it looks like I had issues I wasn’t aware of. The damn thing appears to just exit and then start up again just about an hour apart. Now it just stops. 
     

    Any ideas on where to look to fix this? Honestly thought this thing was running smoothly cause I never saw any errors. 

    IMG_0034.jpeg

    Speedtest.net for unRAID 6.1+

    in Plugin Support

    Posted

    Anyone else having trouble with the server list? I’ve been running mine daily with no issues for a while, but when I went to do a manual test recently it threw back nothing. So I popped into settings where I had manually selected a nearby Spectrum server and the list that’s coming up now has very few servers and none anywhere near my state (Florida). If I go to the Speedtest website it auto selects the nearby server so I don’t know what’s going on. 
     

    to make sure it was still at least working I changed it to Auto and it selected something in Nebraska or something. It worked though and didn’t give any errors. 

    • Like 2

    Parity check cause Plex network issue?

    in General Support

    Posted

    8 hours ago, itimpi said:

    You might want to look into using the Parity Check Tuning plugin so that the check is split into increments that only run outside prime time to minimise the impact on end-users.

    Things are back to working normally so that was definitely the culprit. Installed that plugin and configured it. Thanks for the tip!

    Parity check cause Plex network issue?

    in General Support

    Posted

    4 hours ago, itimpi said:

    You might want to look into using the Parity Check Tuning plugin so that the check is split into increments that only run outside prime time to minimise the impact on end-users.

    Didn’t know there was such a thing. I’ll install today after testing to make sure I can stream properly again. Thanks. 

    Parity check cause Plex network issue?

    in General Support

    Posted

    Considering how long I’ve had Plex server in a docker with mostly no issues at all, I’m afraid to ask a seemingly stupid question. Can running a parity check and trying to stream a movie at 81Mbps or so cause the client to balk due to slow connection? And all direct playing so no load on CPU? And  with 8 cores with u dear 10% utilization? I know damn well my network is fine and Plex should be fine as we watch something almost every night and lately 4K rips. Tonight I had to fallback to a 1080p version at about 30Mbps stream. 
     

    I’ll be honest, I don’t know if I’ve ever tried streaming during a parity check so this might be normal. My parity check takes quite a while for me. Sitting at 21Tb on the array. 
     

    So should I be worried about this and looking for what, I don’t know? 
     

    server version is 6.8.3

    (Solved) Kernel Panic after upgrade to 6.8 (stable)

    in General Support

    Posted

    I just got hit by this. I got a warning about a vulnerability and ran the update. Down goes server.

     

    A) Why is this happening?

    B) Tried manually updating since the Mac USB creator tool fails on Catalina. Again, why?

    C) I don't have any spare USB drives lying around so what type am I supposed to buy now? Current one was the recommended version/brand from way back when.

    D) Is it possible that this is caused by a BIOS configuration issue? Of course it was booting before this update so I don't know.

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    4 minutes ago, acurcione said:

    Saw there was an update this morning so I updated and I've waited for CP to do it's scanning thing, but wanted to verify settings in the my.services.xml file and... there is no my.services.xml file in the conf directory now! Where the heck did it go??

    I pulled a copy from my automated backup on the array and restarted CP. Hope like hell it still reads the file!

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    On 2/11/2020 at 12:13 PM, xman111 said:

    i think the one guy on reddit only had like 5TB i think and they were cutting him off.

    I’m at 13TB uploaded for my unRAID server and another couple TB for my Mac. I still have 7TB to go on the server. Luckily I found a way to speed up the backups or it would have taken years to get this far. Even still it certainly isn’t terribly efficient. 
     

    I do wish there were more options in backup services that can run native Docker though. 

    [Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)

    in Docker Containers

    Posted

    I don't think this is possible, since this file is not expected to be manually edited


    Yeah. I get that. I needed to backup my media files which amount to 18Tb. I tried it before and was going to take years so I gave up only to come back to the idea after part of my server caught fire. :(

    Anyway, after researching the slowness I found a way to speed things up by disabling deduplication in the my.services.xml file. It isn’t recommended for normal things, but these files rarely if ever change. And I have some huge files from ripping discs without compression.

    So with a couple edits I’ll be able to upload everything in 3 months vs years. Not a bad trade off.

    Is it possible to have the items editable in the docker config so even after an update or restart the edits are mad automatically? If so I can supply the items needing editing.



    Sent from my iPad using Tapatalk Pro

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    1 minute ago, Squid said:

    There is no fundamental reason why it doesn't work.  That being said, there was one known issue with 6.7.x and Safari where 2 way communication wouldn't work.

     

    This is supposed to be fixed in 6.8  All of my testing for the plugins is done on 6.8, and running 6.8 with Mohave (Safari 13.0.3 (14608.3.10.10.1)) work fine.

     

     

    Thanks. Easy enough to use Firefox for now. I'm still on Mojave as well. I'm not updating till at least the first point release of Catalina. :)

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    11 minutes ago, Squid said:

    What browser?  *Apparently* there was another user who had an issue with the latest version of FCP when using Safari.  

     

    Also, unless you're on the latest version(s) of FCP, if the window takes longer than 120 seconds to disappear, it never will.  Does any sort of status line show up in the scanning window?

    You're a genius. It was Safari and it never went away. Switched over to Firefox and it ran no problem and found no problems. Going to run an extended scan just in case. And I'm on the latest version as far as ai can tell - 2019.11.13.

    [Plugin] CA Fix Common Problems

    in Plugin Support

    Posted

    I had to rebuild my unRAID server with completely new hardware and can't seem to run Fix Common Problems now. I mean it launches and says it's scanning, but the window never goes away. Everything else appears like it's working as it should and I don't see any errors in the syslog. I had to restore my appdata and docker.img, but that shouldn't have anything to do with this right?