13

Sometimes, you may encounter backup failures while using RunCloud’s backup feature, which can be frustrating. One of the common errors that users face is a backup failing with a message that says:

Full backup snapshot has been failed. Error: process timeout

This error usually indicates that the backup process took longer than expected and eventually caused a timeout. It can happen due to a variety of reasons, including server issues or firewall misconfiguration. Here’s how you can troubleshoot and fix the issue step by step:

Step 1: Check the Backup Logs

Whenever a backup fails, the first thing you should do is check the backup logs to understand what went wrong. These logs will give you insights into what caused the backup process to fail.

If the error log shows the message Error: process timeout, it’s an indication that the backup was unable to complete within the allocated time limit. While this error doesn’t point to a specific cause, it suggests that something may be hindering the backup process from finishing in a timely manner.

Step 2: Initiate an On-Demand Backup

To test the backup process, you can try initiating an on-demand backup by clicking the “Backup Now” option at the top right corner of the backup window. This allows you to test if the backup fails consistently or if it’s a one-time issue.

If this new backup also fails, it’s a sign that there might be an underlying problem with the backup configuration or server.

Step 3: Review Activity Logs in the Panel

If the backup continues to fail, a more detailed investigation is required. Log into your RunCloud dashboard, navigate to the Activity Logs section (found at the bottom left corner), and review the logs for any error messages.

You might come across the following error message in the activity logs:

RunCloud Agent “server-summary”. Unable to communicate with Server Server name (server IP): Connection timed out after 15000 milliseconds.

The Server name and server IP will be replaced with your specific server details.

Step 4: Diagnose the “Connection Timed Out” Error

This error typically occurs when the server cannot communicate with the RunCloud agent. This could be due to one of the following reasons:

1. Server Downtime: The server might be down, causing communication issues with the RunCloud agent.
2. Firewall Blockage: The external firewall provided by your server provider could be blocking the necessary ports that the RunCloud agent uses to communicate with your server.

Step 5: Verify Server Availability

To rule out the possibility of server downtime, you can check if the server is responding by using the ping command. If the server is down or unreachable, you’ll notice packet loss when pinging.

Step 6: Check Server Ports

The issue might also be related to port access. RunCloud requires specific ports to be open for proper communication. You can use the nmap command to check if ports such as 22, 34210, 80, and 443 are open and accessible.

nmap -p 22,34210,80,443 <server_ip>

If the server is not responding to the ping or if certain ports are closed, it’s crucial to verify the status of the server with your provider. Confirm that the necessary ports (22, 34210, 80, and 443) are open on the server provider’s external firewall.

Conclusion

If you encounter the “process timeout” error during a backup in RunCloud, it’s essential to perform a detailed check of the backup logs and activity logs. Most of the time, these errors occur due to connectivity issues between your server and the RunCloud agent, often caused by server downtime or firewall restrictions. By following the steps outlined above, you can identify and resolve the underlying issue, ensuring that your backups run smoothly.

Are you facing any Backup Issue in Runcloud ? Our team is available 24/7 to assist you.