Sakai has a policy of containment and signaling of issues. The application signals via logging and an error report form in which the user can add comments and give relevant feedback.
Early adopters work closely with the community to iron out the residual defects.
Log4j is a Java framework for consistent logging. You can modify the structure of the log file and where the log file is sent through one configuration file.
This chapter mentions a number of common error messages.
Nabble and its search engine over the Sakai distribution lists is a viable source of reference for immediate issues. The Sakai bug database is also a good source for researching problems.
Coming in the next chapter are numerous international case studies showing Sakai at its best.