Required Server Maintenance Workflow
This page is for implementation, operations, and technical support teams handling production server issues. Do not force-restart production servers directly from a cloud console. Confirm the impact scope before restarting projects, services, or databases.
Common Failures and Maintenance Direction
| Category | Issue | First Maintenance Direction |
|---|---|---|
| Login | Server cannot connect on the login page | Restart 'DuliRoute' |
| Login | Login operation reports '4000' | Restart 'DuliRoute' |
| Offline | Client keeps disconnected after login | Restart 'DuliFront' |
| Offline | Client repeatedly reconnects | Restart 'DuliFront' |
| Feature project | Admin console unavailable | Restart 'DuliBackend' |
| Feature project | Approval or project management unavailable | Restart 'DuliMgmt' |
| Feature project | Email unavailable | Restart 'DuliMail' |
| Feature project | Cloud Drive unavailable | Restart 'DuliWpp' |
| Feature service | Cannot send or receive messages | Restart 'DuliRoute', then 'DuliFront' |
| Feature service | Cannot send files or images are broken | Check disk space, then restart 'Gofastdfs' |
| Authorization | License expired or invalid | Check License status in the admin console |
Rule Out Client Issues First
For a single-function issue, restart the client first to exclude client cache, connection state, or local environment problems. If many users are affected, move to server-side maintenance.
Restart Order for Login and Offline Issues
- Restart 'DuliAuth'.
- Restart 'DuliRoute'.
- Restart 'DuliFront'.
If the issue remains, restart the core projects in this order:
- 'DuliAuth'
- 'DuliBackend'
- 'DuliRoute'
- 'DuliFront'
- 'DuliAuth' again
After Abnormal Data Server Shutdown or Reboot
- Start the firewall.
bash
systemctl start iptables- Start 'Redis'.
- Start 'Hadoop', 'Hbase', and 'Zookeeper'.
- Start 'Mysql'.
- Check project servers after data services are healthy.
Restart Notes
- Do not restart production services repeatedly without checking logs.
- Confirm whether users are actively using the system before operating.
- Prioritize service-specific restart over full server restart.
- Search logs for 'OutOfMemoryError' when services restart unexpectedly.