This page describes the procedures for starting, stopping, and initial setup of the Fess server.
Important
Before starting Fess, you must start OpenSearch. If OpenSearch is not running, Fess will not function correctly.
Startup Methods
The startup procedure varies depending on the installation method.
TAR.GZ Version
Start OpenSearch
To start in the background:
Start Fess
To start in the background:
Note
Startup may take several minutes. You can check the startup status in the log file (logs/fess.log).
ZIP Version (Windows)
Start OpenSearch
Open the OpenSearch installation directory
Double-click
opensearch.batin thebinfolder
Or from Command Prompt:
Start Fess
Open the Fess installation directory
Double-click
fess.batin thebinfolder
Or from Command Prompt:
RPM/DEB Version (chkconfig)
Start OpenSearch:
Start Fess:
Check startup status:
RPM/DEB Version (systemd)
Start OpenSearch:
Start Fess:
Check startup status:
Enable automatic startup:
Docker Version
Start using Docker Compose:
Check startup status:
Check logs:
Verify Startup
Verify that Fess has started successfully.
Health Check
Access the following URL using a browser or curl command:
If started successfully, the Fess search screen will be displayed.
Check from command line:
If HTTP/1.1 200 OK is returned, it has started successfully.
Check Logs
Check the startup logs to ensure there are no errors.
TAR.GZ/ZIP version:
RPM/DEB version:
Or use journalctl:
Docker version:
Tip
When started successfully, a message like the following will be displayed in the logs:
Access via Browser
Access the following URLs to verify the web interface.
Search Screen
The Fess search screen will be displayed. In the initial state, no search results will be displayed because no crawl configuration has been performed.
Admin Screen
URL: http://localhost:8080/admin
Default administrator account:
Username:
adminPassword:
admin
Warning
Important Security Notice
You must change the default password. Especially in production environments, it is strongly recommended to change the password immediately after the first login.
Initial Setup
After logging into the admin screen, perform the following initial configuration.
Step 1: Change Administrator Password
Log in to the admin screen (http://localhost:8080/admin)
Click “System” → “User” from the left menu
Click the
adminuserEnter a new password in the “Password” field
Click the “Confirm” button
Click the “Update” button
Important
Passwords should meet the following criteria:
8 characters or more
Combination of uppercase letters, lowercase letters, numbers, and symbols
Not easily guessed
Step 2: Create Crawl Configuration
Create a configuration to crawl target sites or file systems.
Click “Crawler” → “Web” from the left menu
Click the “New” button
Enter required information:
Name: Name of the crawl configuration (e.g., Company Website)
URL: Target URL for crawling (e.g., https://www.example.com/)
Max Access Count: Maximum number of pages to crawl
Interval: Crawl interval (milliseconds)
Click the “Create” button
Step 3: Execute Crawl
Click “System” → “Scheduler” from the left menu
Click the “Start Now” button for the “Default Crawler” job
Wait for the crawl to complete (progress can be checked on the dashboard)
Step 4: Verify Search
Access the search screen (http://localhost:8080/)
Enter a search keyword
Verify that search results are displayed
Note
Crawling may take time. For large-scale sites, it may take from several hours to several days.
Other Recommended Settings
For production environments, consider the following settings.
Configure Mail Server
Configure the mail server to receive failure notifications and reports via email.
Click “System” → “General” from the left menu
Click the “Mail” tab
Enter SMTP server information
Click the “Update” button
Configure Time Zone
Click “System” → “General” from the left menu
Set “Time Zone” to an appropriate value (e.g., Asia/Tokyo)
Click the “Update” button
Adjust Log Level
In production environments, you can adjust the log level to reduce disk usage.
Edit the configuration file (app/WEB-INF/classes/log4j2.xml).
For details, refer to the administrator guide.
Shutdown Methods
TAR.GZ/ZIP Version
Stop Fess
Kill the process:
Or, stop from the console with Ctrl+C (if running in the foreground).
Stop OpenSearch:
RPM/DEB Version (chkconfig)
Stop Fess:
Stop OpenSearch:
RPM/DEB Version (systemd)
Stop Fess:
Stop OpenSearch:
Docker Version
Stop containers:
Stop and remove containers:
Warning
To also delete volumes with the down command, add the -v option. In this case, all data will be deleted, so use with caution.
Restart Methods
TAR.GZ/ZIP Version
Stop and then start.
RPM/DEB Version
chkconfig:
systemd:
Docker Version
Troubleshooting
Won’t Start
Verify OpenSearch is running
If OpenSearch is not running, start OpenSearch first.
Check for port conflicts
If port 8080 is already in use, change the port number in the configuration file.
Check logs
Identify the problem from error messages.
Verify Java version
Verify that Java 21 or later is installed.
For detailed troubleshooting, refer to Troubleshooting.
Next Steps
After Fess has started successfully, refer to the following documentation to begin operation:
Administrator Guide: Details on crawl configuration, search settings, and system settings
Security Configuration - Security configuration for production environments
Troubleshooting - Common problems and solutions
Upgrade Procedure - Version upgrade procedures
Uninstallation Procedure - Uninstall procedures