Skip to main content
Solved

Duplicate/hung process on Linux Media Agent


Forum|alt.badge.img+1

Hi,

 

We ran into a problem where the Linux Media Agent processes hung and showed duplicate processes.

We tried to stop them using “Commvault stop” and “systemctl stop commvault,” but with no luck.

We ended up rebooting the server, which solved the problem.

 

Commvault version: 11.32.42
Media Agent OS: Red Hat 8.9

 

What can cause this problem, and how can we resolve it without restarting the server?

Best answer by Rajiv

Hello @Mike_M Ideally all the processes should be stopped after waiting for some time after running the commvault stop command. Sometimes it can take more than 10-15 minutes depending on the work being done by the processes. You can also check if there are any jobs running against this MA before stopping the services directly. It's not recommended to kill the processes forcefully on the MA since it can lead to corruption in the DB. 

How frequently you are facing this issue? Can you note down the time when it occurs and check the /var/log/messages for any information for the same time? 

Also, what’s the hardware specifications for this MA? You can also check if RAM and CPU utilizations are reaching 100%., if they are, you should consider increasing the resources. You can also try to segregate the schedules as well to avoid this behavior.  

Best,

Rajiv Singal

View original
Did this answer your question?

2 replies

Forum|alt.badge.img+5
  • Vaulter
  • 50 replies
  • July 18, 2024

Just to clarify, in your first screen grabs - what are you defining as duplicate processes? Please explain your observations? So we can understand from your view point.


Rajiv
Vaulter
Forum|alt.badge.img+12
  • Vaulter
  • 323 replies
  • Answer
  • July 16, 2024

Hello @Mike_M Ideally all the processes should be stopped after waiting for some time after running the commvault stop command. Sometimes it can take more than 10-15 minutes depending on the work being done by the processes. You can also check if there are any jobs running against this MA before stopping the services directly. It's not recommended to kill the processes forcefully on the MA since it can lead to corruption in the DB. 

How frequently you are facing this issue? Can you note down the time when it occurs and check the /var/log/messages for any information for the same time? 

Also, what’s the hardware specifications for this MA? You can also check if RAM and CPU utilizations are reaching 100%., if they are, you should consider increasing the resources. You can also try to segregate the schedules as well to avoid this behavior.  

Best,

Rajiv Singal


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings