After installing Koha Library System, performing thorough verification checks is essential to ensure your system is properly configured and production-ready. This guide covers critical validation steps that should be completed before going live.

Why Post-Installation Verification Matters

Proper verification ensures:

  • System Stability - All dependencies are correctly installed
  • Security - Default settings are properly configured
  • Performance - System is optimized from day one
  • Data Integrity - Database connections are working correctly
  • Production Readiness - No critical errors or warnings

Taking time to verify your installation prevents issues that could disrupt library operations later.

Accessing the About Page

The Koha “About” page is your primary diagnostic tool.

Step 1: Log Into Koha

  1. Navigate to your Koha staff interface URL
  2. Use the credentials you retrieved during setup
  3. Log in with username koha_library and your instance password

Step 2: Navigate to About

  1. Click on More in the top navigation
  2. Select About Koha
  3. Review all sections carefully

Critical Sections to Review

1. Server Information

This section provides details about your server environment:

  • Operating System: Should show Ubuntu 20.04 LTS or later
  • Perl Version: Typically 5.30+ for modern Koha
  • Database: MariaDB or MySQL version information
  • Koha Version: Current installed version
  • Apache Version: Web server details

What to Check:

  • ✓ All versions meet minimum requirements
  • ✓ No red warning messages
  • ✓ Database connection is active

2. Perl Modules

Lists all Perl modules required for Koha functionality.

Important Notes:

  • Some modules may show as “missing” immediately after login
  • Wait 2-3 minutes and refresh the page
  • Most initial warnings resolve automatically
  • All required modules should show green checkmarks

If Modules Are Missing:

# SSH into your instance
ssh ubuntu@your-instance-ip

# Update Perl modules
sudo apt-get update
sudo apt-get install libmodule-name-perl

# Restart Apache
sudo systemctl restart apache2

3. System Preferences

Displays configuration status and potential issues.

Common Warnings:

SessionStorage Not Set

Issue: “SessionStorage preference not set”

Fix:

  1. Go to Administration → System Preferences
  2. Search for “SessionStorage”
  3. Set to mysql for persistence
  4. Save changes

Version Update Available

Issue: “Koha version X.XX is available”

Action: Review release notes before updating. For AWS instances, we handle updates during maintenance windows.

Missing Email Configuration

Issue: “Email server not configured”

Fix:

  1. Go to Administration → System Preferences
  2. Navigate to Patrons → Messaging
  3. Configure SMTP settings:
    • KohaAdminEmailAddress: your-library@example.com
    • SMTP Server: Your email server (or AWS SES)
    • SMTP Port: Typically 587 for TLS
    • SMTP Username/Password: If required

4. Database Size and Performance

Check database statistics:

What to Review:

  • Number of bibliographic records
  • Number of items
  • Number of patrons
  • Database size on disk

Expected Values for New Installation:

  • Records: 0-100 (test data)
  • Items: 0-500
  • Patrons: 1-10
  • Database size: < 50 MB

5. System Maintenance Jobs

Verify background jobs (cron jobs) are running:

# Check cron jobs
sudo crontab -l -u www-data

# Verify jobs are executing
sudo tail -f /var/log/koha/library/cronjobs.log

Essential Cron Jobs:

  • Overdue notices
  • Fines accrual
  • Database optimization
  • Search index updates
  • Session cleanup

Performance Checks

Test Page Load Times

  1. Navigate through different modules
  2. Page loads should be < 3 seconds
  3. Search results should appear < 2 seconds

If Slow:

  • Check server resources (CPU, RAM)
  • Review Apache/MySQL logs
  • Consider enabling caching (see our Performance Guide)

Test Search Functionality

  1. Go to staff search
  2. Perform a test search
  3. Verify results display correctly
  4. Test faceted search (refine by author, date, etc.)

Test OPAC

  1. Open OPAC in a new browser tab
  2. Verify public catalog loads
  3. Test search from patron perspective
  4. Check responsive design on mobile

Security Checks

1. Verify SSL/TLS

Your AWS instance should use HTTPS:

# Test SSL certificate
curl -I https://your-domain.com

# Should return 200 OK with SSL certificate info

2. Check Firewall Rules

Verify only necessary ports are open:

# In AWS Console, check Security Group
# Required ports:
# - 80 (HTTP) - Redirects to HTTPS
# - 443 (HTTPS) - Main access
# - 22 (SSH) - Admin access (restrict to your IP)

3. Review Admin Permissions

  1. Go to Patrons → Staff users
  2. Verify only authorized users have superlibrarian permission
  3. Remove default/test accounts

Common Issues and Solutions

Issue: “Warnings on About Page”

Diagnosis: Review specific warning message

Solutions:

  • Update system preferences as indicated
  • Install missing Perl modules
  • Configure email settings
  • Update Koha version if critical

Issue: “Slow Performance”

Diagnosis: Check server resources

Solutions:

Issue: “Cannot Access OPAC”

Diagnosis: DNS or Apache configuration

Solutions:

  1. Check DNS settings pointing to instance
  2. Verify Apache virtual hosts
  3. Review Apache error logs: 
    sudo tail -f /var/log/apache2/error.log

Issue: “Email Notifications Not Sending”

Diagnosis: SMTP configuration

Solutions:

  1. Verify SMTP credentials
  2. Test email from command line: 
    echo "Test" | mail -s "Test Email" your-email@example.com
  3. Check email server logs
  4. Consider using Amazon SES for AWS instances

Post-Check Configuration

After verifying everything works:

1. Import Sample Data (Optional)

For testing purposes:

  1. Go to Tools → Import
  2. Upload sample MARC records
  3. Test cataloging workflow

2. Configure Circulation Rules

  1. Administration → Circulation and fines rules
  2. Set up patron categories
  3. Define item types
  4. Configure loan periods and fines

3. Customize OPAC

  1. Administration → System Preferences → OPAC
  2. Upload library logo
  3. Customize colors and styling
  4. Set library information

4. Set Up Automated Backups

Verify backups are configured:

# Check backup cron job
sudo crontab -l

# Verify backup location
ls -lh /var/backups/koha/

Learn more: How to Backup Your Koha Database

Maintenance Schedule

Establish regular check routines:

Daily

  • ✓ Monitor error logs
  • ✓ Check system availability
  • ✓ Review overnight job results

Weekly

  • ✓ Review About page for warnings
  • ✓ Check database size growth
  • ✓ Verify backups are running

Monthly

  • ✓ Update system packages
  • ✓ Review security patches
  • ✓ Performance optimization review

Quarterly

  • ✓ Koha version update review
  • ✓ Server resource assessment
  • ✓ Disaster recovery test

Next Steps

With your system verified and ready:

  1. Staff Training - Train your team on Koha
  2. Data Migration - Import your existing catalog
  3. Patron Import - Load patron records
  4. Go Live - Announce to your community

Need Help?

If you encounter issues during post-installation checks:

Pro Tip: Bookmark the About page and check it regularly. It’s your first line of defense for identifying system issues before they impact users.