• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

BUG: Acronis module - another atismodbackupmng process is running

J

jacko@

Guest
Hello,

There is a bug with the Aconis module with Plesk 9.2.1 for Linux (Ubuntu 8.04).

Scheduled jobs come back with:

> Error: another atismodbackupmng process is running!
> TrueImage backup task #2

And yes, the same problem happens with the following work around:
http://kb.odin.com/en/6248

A ticket was opened with Parallels support regarding this and it took over a month to get resolved, so, I'm posting this to help some other poor soul who may have to deal with the software, or, support team. Also, I wouldn't want someone else to get charged for a workaround from their support team.

The issue had been caused by incorrect way Acronis True Image Module determines if another task is already running.

Support applied the following hack:
"As for now I have applied following solution in order to remedy the problem -- now scheduled tasks are properly executed:

--- /opt/psa/admin/sbin/modules/atism/atismodbackupmng.orig 2009-07-22 06:57:24.000000000 +0000
+++ /opt/psa/admin/sbin/modules/atism/atismodbackupmng 2009-07-22 07:06:54.000000000 +0000
@@ -415 +415 @@
- if ($cmd =~ /atismodbackupmng\s+--exec-task/ || $cmd =~ /atismodbackupmng\s+--backup-now/) {
+ if ($cmd !~ /^\/bin\/sh\s+-c/ && ($cmd =~ /atismodbackupmng\s+--exec-task/ || $cmd =~ /atismodbackupmng\s+--backup-now/)) {
"

jacko
 
What's happening with this bug? It's STILL present in Plesk 9.2.3.
 
Right, bug still under developer's investigation. I hope that fix will be implemented to the next Plesk update.
 
Right, bug still under developer's investigation. I hope that fix will be implemented to the next Plesk update.

So, we are 4 months on and no fix? (5 months including the month we waited for support). Unfortunately we sell this to customers and every time we have to install it we spend hours dealing with this rubbish.

I applied the "fix" / "patch" that was previously supplied, however, this doesn't fix the problem in 9.2.3.

Any chance of an updated fix?

Thanks.
Jacko
 
Back
Top