(turns out I missed this step during initial setup) In one of my logs I noticed that the engine was shutting down after attempting to connect to :4243 and failing to do so. So I was able to fix the problem where CP would start crashing after I configured it using the GUI. But the problem doesn't appear to affect reads, which is what I expect the CP service would be doing at the time it's failing, it doesn't occur frequently, and I didn't experience a problem with CIFS mounts on the CrashPlan VM (I'm currently using NFS mounts). ![]() Accessing shares via CIFS intermittently fails with spurious permission denied errors, and this is causing weird problems for my Windows 10 clients. If it does, I suggest opening a ticket with CrashPlan support.Īnother possibility, though unlikely, is that this SMB bug is causing problems: viewtopic.php?f=189&t=122544. Anyone have any suggestions?įirst, check that the CP service has sufficient memory. I have not found anything telling in the logs. I even try to start the service as sudo via the CLI, and it starts, but within a minute shuts down again. I have tried rc2.d, rc5.d and /init.d/rc5.d as run levels, all with the same results. Removal and reinstallation have ben the only way I found to get it up and running again, and that only persists until I log out of the desktop or restart. It will say it's running immediately after start, but shortly after that it will stop. ![]() Once I do that I can no longer get the desktop application to connect to the CP service, nor will CP stay running after startup. I'm able to get to the point where I adopt a backup and everything runs fine until I exit the desktop environment or reboot. ![]() Sszyszka wrote:Thanks to these instructions I was able to mostly get up and running, but I'm running into a weird problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |