Summary
If your Yellowfin service is failing to start, or starts and then shuts down unexpectedly, there are a number of things you can check before reaching out to Support. This article walks you through some initial diagnostic steps and explains what information to gather if the issue requires further investigation.
Initial Checks
Check the Yellowfin log files
The log files are the most useful starting point for diagnosing a start-up failure. You can find them at:
Yellowfin\appserver\logs
Look for any ERROR or FATAL entries around the time the failure occurred. Common causes include port conflicts, JVM issues, database connectivity problems, and insufficient memory.
Check for port conflicts
Yellowfin uses port 8080 by default. If another application is already using this port, Yellowfin will fail to start. You can check for port conflicts using the following commands:
On Windows:
netstat -ano | findstr :8080
On Linux or macOS:
lsof -i :8080
Check available memory
Yellowfin requires sufficient memory to start. If the server is running low on available RAM, the JVM may fail to allocate the required heap space. Check your server's available memory and compare it against the recommended specifications for your deployment size.
Windows service: check for Error Code 1
If you are running Yellowfin as a Windows service and see Error Code 1 on startup, this typically indicates a JVM architecture mismatch. See our article on resolving this here: Windows Service Error Code 1.
If the Issue Persists
If you are unable to resolve the issue after the above checks, please gather the following information before contacting Support, as it will help us diagnose the problem faster:
- When did the issue start? For example, after a new install, server reboot, or upgrade.
- How is Yellowfin being started?
- startup.bat
- startup.sh
- macOS startup
- Windows Service
- Your Yellowfin log files from Yellowfin\appserver\logs
If you have any further questions on this article, contact Support with a new ticket or send us an email.