Unfortunately, the error messages are not particularly helpful at the moment. This page lists some of the common errors, and the most likely causes of them.
When an error occurs, you will see a message like 'Exception: RaidFile/OSFileError (2/8)' either on the screen or in your log files. (it is recommended you set up another log file as recommended in the server setup instructions.)
This error may not be particularly helpful, although some do have extra information about probable causes. To get further information, check the ExceptionCodes.txt file in the root of the distribution. This file is generated by the ./configure script, so you will need to have run that first.
Some common causes of exceptions are listed below.
Please email me with any other codes you get, and I will let you know what they mean, and add notes here.
This is found either when running bbstoreaccounts or in the bbstored logs.
Problem: The directories you specified in the raidfile.conf are not writable by the _bbstored user.
Resolution: Change permissions appropriately.
This usually occurs when the configuration files can't be opened.
Problem: You created your configurations in non-standard locations, and the programs cannot find them.
Resolution: Explicitly specify configuration file locations to daemons and programs. For example
/usr/local/bin/bbstored /some/other/dir/bbstored.config /usr/local/bin/bbackupquery -c /some/other/dir/bbackupd.config
(daemons specify the name as the first argument, utility programs with the -c option.
Problem: bbstored can't find the raidfile.conf file specified in bbstored.conf.
Resolution: Edit bbstored.conf to point to the correct location of this additional configuration file.
The server can't listen for connections on the IP address specified when you configured it.
Problem: This probably means you've specified the wrong hostname to bbstored-config -- maybe your server is behind a NAT firewall?
Resolution: Edit bbstored.conf and correct the ListenAddresses line. You should replace the server address with the IP address of your machine.
These errors all relate to connections failing -- you may see them during operation if there are network failures or other problems between the client and server. The backup system will recover from them automatically.
If 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.
For example, if you are having problems with bbstoreaccounts, build the debug version with
cd boxbackup-0.0 cd bin/bbstoreaccounts make
(within the module directories, make defaults to building the debug version. At the top level, it defaults to release.)
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.
When 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.
If you are using a debug version of a daemon, these extended messages are found in the log files.
Please get in touch if you need any help.
© Ben Summers, 2003, 2004