docs.facundoitest.space

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Diagnosing a Stuck Backup Job ======

**Problem:** Sometimes, a backup job on your server can become stuck, and you may find it challenging to stop or kill the process.

**Symptoms:** You might encounter this issue when attempting to stop a backup job in the back office, or when checking the vzdump process in the console.

===== Diagnosis: =====

1. **Web UI:** If you try to stop the backup job in the Web UI, but nothing happens, it's an early indication of the problem.

2. **Console Check:** To investigate further, check the ''vzdump'' process using the command:

<code bash>
ps awxf | grep vzdump
</code>

You will see the process ID (PID) of the backup job, which appears as something like this:

<code bash>
2444287 ?        Ds     0:00 task UPID:server_name:00254BFF:06D36C31:63BB7524:vzdump::root@pam:
</code>

Note that the process state is "Ds," indicating an uninterruptible sleep (waiting for IO). This state cannot be interrupted by signals, making it difficult to stop.

===== Solution: =====


1. **vzdump -stop:** Ideally, you can try to stop the stuck backup job using:

<code bash>
vzdump -stop
</code>

However, this may not always work.

2. **Kill the Process:** You can attempt to kill the process using the command:

<code bash>
kill -9 <process id>
</code>

Replace  ''<process id>'' with the actual PID of the vzdump process. Please note that it might take some time (approximately 2 minutes) for the backup to terminate.

3. **Process States:** Understand that the process state "Ds" means the process is in an uninterruptible sleep, waiting for IO. It cannot be easily stopped by signals. In contrast, "Ss" state (interruptible sleep) can be interrupted by signals.

For more details on process states, refer to the "PROCESS STATE CODES" in the `man ps` command.

<WRAP center round important 60%>
**Final Note:** If the backup job remains stuck, with the process in an uninterruptible sleep state, it may indicate an IO-related issue, possibly with the hard drive. In such cases, you might need to consider rebooting the system as a last resort.
</WRAP>


Diagnosing and resolving a stuck backup job can be challenging, but these steps provide a starting point for understanding and addressing the issue.

https://forum.proxmox.com/threads/backup-job-is-stuck-and-i-cannot-stop-it-or-even-kill-it.120835/