Official Documentation...

[ Table of Contents ]

Non-Fatal Error Messages

The following error messages listed below are NON-FATAL and should not concern you in the slightest. It is quite possible, and my personal wish, that these non-fatal errors will be suppressed in future releases of BNBT.

... As Seen From The Tracker Console Window

1. client warning - (zlib) deflate error (0) on "/files/...", compact = 0, in = xxxx, sending raw

BNBT 7.7x employs file compression to allow the tracker to operate more smoothly. Because image files, such as GIFs and JPEGs are so small, they do not require compression, and therefore cause an error message to be displayed in your console, whenever an image is sent to a user's web browser. The reason the error occurs is because the image file goes through the compression library and comes out larger than when it went in.

To supress these errors, you can store all of the image files used by your tracker on a separate server, and reference the full URL to these images in your tracker's configuration and static documents. Using this method, your tracker will not be responsible for serving the image files and you will not see these error messages.

Keep in mind though, that these error messages are non-fatal.

2. client error - receive error (error 10054)

The above error message is caused by the way that keepalives are handled in most web browsers. Your users do not receive this error message.

PLEASE NOTE: It is not uncommon for this error message to be rendered in your console display repeatedly every few seconds. There is no cause for alarm. Hopefully, this non-fatal error message will be suppressed in future releases of BNBT, as it has caused many tracker admins to worry needlessly.

... As Seen From The BitTorrent Client

1. ON TODO LIST!
2. ON TODO LIST!
3. ON TODO LIST!
4. ON TODO LIST!