Error to Agent 3.0 - Linux

[jcerrato1]

Error: Failed to execute agent management command startBackup. Error: Another backup job is running.

1) I have uninstalled the above agent.
2) rebooted that server .
3) installed the agent again,
4) The backup will run without issues for a couple times and then give the above error. This started happening when I upgraded from version 2 to 3 agent.

[PTide]

Hi,

What mode is that? Is it standalone or managed by VBR/Agent mode? Are you positive that there are no other jobs attempting to start at the same time? Please also provide logs (either open a support case, or provide a link to a downloadable archive)

Thanks!

[mwag]

Did you find a solution? We are encountering the same problem with Agent 3.

[BenO]

We also see this same issue after updating to Agent 3.0 on RHEL 7

Confirmed there are NO veeam processes running before kicking off the job and get 'Another Job is Running' error.

At that point, there IS a veeamjobman and veamagent process running, but they are the ones from the job thats just failed.

Code: Select all

root     117603 111127  0 02:36 ?        00:00:00 veeamjobman Service --session {2eccbc59-8659-4d93-8e1a-12af361ba186} --socket /var/tmp/veeam/socket/veeam.sock --log /var/log/veeam/Backup/Agent Backup Job 1 - dre-<hostname>/Session_20190122_023609_{2eccbc59-8659-4d93-8e1a-12af361ba186}/Job.log
root     117665 111127  0 02:36 ?        00:00:08 veeamagent --log /var/log/veeam/Backup/Agent Backup Job 1 _B dre_B<hostname>/Session__20190122__023609___F2eccbc59_B8659_B4d93_B8e1a_B12af361ba186_G/Agent.Source.log --mgmtConnKey AQAAAAAAAAAhAAAAVkFMIG1hbmFnZW1lbnQgY2hhbm5lbCBlbmNyeXB0aW9uAQAAAAEAAAAAAAAAGOGkPfux1AECAAAASgAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAQAAAAD46aEA42nF/nltLUNYoUe0QBkF0OrBW475HahsxCNEkM7B1/8zDLUQPxS0w/OoGpEAAAABkLErh+h9DJdmxJPiVd8AA=

At this point, restarting veeamservice clears these processes and the job may then work (or may fail with the same error)

[PTide]

Hi,

Michael, BenO,

Although our team already has ideas about the issue, I would like to encourage you to open a support cases and provide our support team with logs as it is almost impossible to say anything regarding the problem without seeing the logs. Please also post your case ID.


Thanks you!

[BenO]

I've raised this as case 03375684

Ben

[MoritzB]

Any Updates on this Topic?

we are having the same issues when importing an Config on Debian 8.11

[PTide]

we are having the same issues when importing an Config on Debian 8.11

Hi,

Please open a case with support team and post your case ID. They will collect logs, investigate the issue, and provide you with information about further course of action.

Thanks!

[edingc]

Case #03414007 created with same issue.

[PTide]

UPDATE: The fix is available via support team

[ilas]

What was the solution? I'm running into roughly the same problem
Thanks