Changes between Version 12 and Version 13 of Troubleshooting


Ignore:
Timestamp:
04/21/08 22:53:58 (6 years ago)
Author:
chris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Troubleshooting

    v12 v13  
    111111If this really doesn't help, then using the DEBUG builds of the system will give you much more information - a more descriptive exception message and the file and line number where the error occurred. 
    112112 
    113 '''DO NOT DO THIS''' for the store server, `bbstored`, as the debug version uses a different store file layout and it will NOT be compatible with your existing store. 
     113'''DO NOT DO THIS''' for `bbstored` or `bbstoreaccounts`, as the debug versions use a different store file layout and they will NOT be compatible with your existing store, and may well corrupt it. 
    114114 
    115 For example, if you are having problems with bbstoreaccounts, build the debug version with the following commands: 
     115For example, if you are having problems with bbackupquery, build the debug version with the following commands: 
    116116 
    117117{{{ 
    118118cd boxbackup-0.xx 
    119 cd bin/bbstoreaccounts 
     119cd bin/bbackupquery 
    120120make 
    121121}}} 
     
    123123(within the module directories, make defaults to building the debug version. At the top level, it defaults to release.) 
    124124 
    125 This will build an executable in debug/bin/bbstoreaccounts which you can then use instead of the release version. It will give far more useful error messages. 
     125This will build an executable in debug/bin/bbackupquery which you can then use instead of the release version. It will give far more useful error messages. 
    126126 
    127127When you get an error message, use the file and line number to locate where the error occurs in the code. There will be comments around that line to explain why the exception happened. 
    128128 
    129 If you are using a debug version of a daemon, these extended messages are found in the log files. 
     129If you are using a debug version of a daemon, these extended messages are found in the log files. You can also try running the daemon with the -DV options for debugging. 
    130130 
    131131== If All Else Fails ==