Difference between revisions of "StableBit CloudDrive Log Collection"

From Covecube - Wiki
 
(2 intermediate revisions by the same user not shown)
Line 16: Line 16:
 
# After you see the error, open the "Troubleshooting" section again and click on "Enable Disk tracing..." to disable it.
 
# After you see the error, open the "Troubleshooting" section again and click on "Enable Disk tracing..." to disable it.
 
# Open 'C:\ProgramData\StableBit CloudDrive' in Windows Explorer.
 
# Open 'C:\ProgramData\StableBit CloudDrive' in Windows Explorer.
 +
#* '''Note:''' This is '''''ProgramData''''', not '''''Program Files'''''.
 
#* '''Note:''' You will need to type this in, or enable "Show Hidden Files" to see this folder.
 
#* '''Note:''' You will need to type this in, or enable "Show Hidden Files" to see this folder.
 
# ZIP up the 'Service' Sub folder.
 
# ZIP up the 'Service' Sub folder.
Line 32: Line 33:
 
'''If known, note the exact time that the error occurred in the description below.'''
 
'''If known, note the exact time that the error occurred in the description below.'''
  
<wikiscript src="https://app.box.com/embed/upload.js?token=o4y89c1h28652r78t5p1f7hcry60if8r&folder_id=3109445897&w=385&h=385&i=&d=1&t=Submit%20to%20Technical%20Support&r=1" type="text/javascript">If you are using a Script Blocker, please disable to see the upload form.</wikiscript>
+
[https://www.dropbox.com/request/lrCAeFa2EH9VSJqP3QLM Click here to submit files using Dropbox (you don't need to an account with Dropbox)]
 +
 
  
 
''Logs are only used to fix bugs in StableBit CloudDrive and for no other purpose.''
 
''Logs are only used to fix bugs in StableBit CloudDrive and for no other purpose.''

Latest revision as of 18:24, 22 June 2016

StableBit CloudDrive features advanced kernel logging that can record every I/O operation performed on the pool. In addition, the StableBit CloudDrive service performs high level logging of its operation.

All log files are written under C:\ProgramData\StableBit CloudDrive\Service\Logs on the sever.

Be aware that if you try to read the log files yourself, you may see many warning messages. These by themselves do not indicate a problem. The Win32 API expects many functions to fail. For example, many applications will check whether a file exists or not by trying to open it, so it is perfectly normal for that to error out.

Collect a log

If you experience a problem with copying a file or reading data from the pool:

  1. Access the server using this: StableBit DrivePool Q7200705.
  2. Open up StableBit CloudDrive.
  3. Click on the "Gear" icon in the top, right corner of the StableBit CloudDrive UI.
  4. Open the "Troubleshooting" section and select "Enable Disk Tracing", and accept any prompts.
  5. Reproduce your error by copying / opening a file.
  6. After you see the error, open the "Troubleshooting" section again and click on "Enable Disk tracing..." to disable it.
  7. Open 'C:\ProgramData\StableBit CloudDrive' in Windows Explorer.
    • Note: This is ProgramData, not Program Files.
    • Note: You will need to type this in, or enable "Show Hidden Files" to see this folder.
  8. ZIP up the 'Service' Sub folder.
    File:CloudDrive zip service folder.png
  9. Upload the resulting zip file using the form below with a short description explaining the problem.
  10. You can optionally open a support contact thread at http://stablebit.com/contact (don't attach the logs to the contact thread as they can be very large).

Upload the log

You should not attach log files to a contact message at http://stablebit.com/contact because the files can be very large.

Upload Server.zip below.

Describe how you encountered the error.

If known, note the exact time that the error occurred in the description below.

Click here to submit files using Dropbox (you don't need to an account with Dropbox)


Logs are only used to fix bugs in StableBit CloudDrive and for no other purpose.

If do not seen the Box upload widget above, please temporarily disable any script blockers you are using.

Thank you

Thank you for taking the time to submit a detailed log file of your problem. The log files help us fix bugs quicker.