Error Cron Panel Plesk

Buenas tardes.

Tengo un error en el cron que me envia este mensaje.

/usr/local/psa/admin/sbin/mailqueuemng -Sfailure

Can't exec "pidof": No such file or directory at
/usr/local/psa/admin/sbin/mailqueuemng line 670 (#1)
(W exec) A system(), exec(), or piped open call could not execute the
named program for the indicated reason. Typical reasons include: the
permissions were wrong on the file, the file wasn't found in
$ENV{PATH}, the executable in question was compiled for another
architecture, or the #! line in a script points to an interpreter that
can't be run for similar reasons. (Or maybe your system doesn't support
#! at all.)

Use of uninitialized value $qmpid in scalar chomp at
/usr/local/psa/admin/sbin/mailqueuemng line 671 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.

To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it cannot
do this, so it also tells you what operation you used the undefined value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in your
program. For example, "that $foo" is usually optimized into "that "
. $foo, and the warning will refer to the concatenation (.) operator,
even though there is no . in your program.

Use of uninitialized value $qmpid in pattern match (m//) at
/usr/local/psa/admin/sbin/mailqueuemng line 672 (#1) Qmail isn't running... no need to stop it.
Looking for messages with Subject: failure No messages matching Subject "failure" found in the queue!

Can't exec "pidof": No such file or directory at
/usr/local/psa/admin/sbin/mailqueuemng line 670 (#2)
(W exec) A system(), exec(), or piped open call could not execute the
named program for the indicated reason. Typical reasons include: the
permissions were wrong on the file, the file wasn't found in
$ENV{PATH}, the executable in question was compiled for another
architecture, or the #! line in a script points to an interpreter that
can't be run for similar reasons. (Or maybe your system doesn't support
#! at all.)

Qmail wasn't running when qmHandle was started, so it won't be restarted.


Que problema puede ser?

Muchas gracias.

 

Tu problema se llama plesk!! XD Perdona por la ironia, yo tuve ese problema hace poco, y no conseguí solucionarlo, al final conseguí que el cliente se pasase a cPanel.

Saludos y suerte!!

 

Que versión de Plesk y con que S.O.

 

si tienes la respuesta, te pongo una calle con tu nombre!! XD