Summary: Troubleshoot GBase Database(GBase 8s) startup failures by checking port usage, identifying conflicting processes, and verifying consistent port configuration.
When oninit fails to start a GBase Database(GBase 8s) instance, a port conflict is one possible cause worth checking early. Here's how to investigate it systematically.
1. Check Whether the Port Is in Use
If your configured database port is 9088, run:
ss -tlnp | grep 9088
# Alternative:
netstat -tlnp | grep 9088
If a process is listening on this port, identify it before taking action. The output may include the process name and PID, depending on your privileges and system tools.
Note: No output doesn't rule out every port-related problem. Confirm the actual port configured for your instance.
2. Identify the Process Before Stopping It
If the port belongs to an old GBase Database instance, verify that it is safe to shut down before running:
onmode -ky
This command shuts down the current instance associated with your environment. Make sure you're targeting the correct instance, especially on servers hosting multiple database instances.
Don't terminate an unrelated service simply because it uses the same port.
3. Verify Port Availability and Retry
After safely stopping the old instance, check again:
ss -tlnp | grep 9088
If the port is no longer occupied, retry startup using the appropriate procedure for your environment.
oninit -ivy
Use oninit -ivy only when initialization or reinitialization is intended and appropriate. It is not a universal fix for every startup failure.
4. Check Port Configuration Consistency
If another service legitimately uses the port, review the database configuration before changing anything.
For GBase Database(GBase 8s), check the relevant port settings in onconfig and the connection information in sqlhosts. Make sure the server's listening configuration and client connection configuration agree.
5. Check Permissions and Startup Logs
Run diagnostic commands with sufficient privileges to identify the process holding the port. If no conflict exists, inspect the database startup output and relevant online log for the actual error.
Other causes may include incorrect environment variables, shared-memory issues, permissions, or configuration errors.
Final Takeaway
When GBase Database oninit won't start, checking port usage is a quick first step—not a guaranteed diagnosis. Identify the cause, verify the configuration, and choose the recovery procedure that matches the error.
What's the most common cause of oninit startup failures in your environment?
Top comments (0)